Is support connected to App logic design ?

The soul of an Application is the logic. Thet heart is placed by the implementation of an App. Both make a solution to solve one or more problems.

To fight real problems you need strong logic design and strong implementation. The logic controls the lifetime of the solution. I am sure you have found many apps having poor logic but great high-tech implementation. Of course any of those Apps can’t do the job or can’t finish it.

Here is the point where support comes in. Support has to cover the gap between poor logic and final solution. Anyone can understand now, that the amount (cost) of the support reflects the damage of the poor logic plus some implementation faults (if any). The implementation faults can easily be corrected and reduce the damage. But the logic part is fundamental for the App and can't be easily fixed. Most of the cases need redesign.

Another situation is when the logic contains the support part. Many companies charge for the support or sometimes their final product is the support. That is a usual case for the open source products. Here the support cost is not damage but works as income. For those cases the logic has to be poor (problem solve logic) and the implementation rich.

These products are the most profitable. The success key for those Apps is to declare that can solve a real life problem. They contain a low cost logic - implementation and their price is free. Those apps work well with low amount of data. But what happens when your data growing? The answer is support.

Finally the support is the remainder part of an App or sometimes the real product. In any way is tight connected to logic.