>
>Of the many ways there are to make apps here are the two that I think are the most common.
>
>You begin an app. because you know there's a big market for it. No need to finish it. No need for it to be bug free. No need for it to do everything as advertised. The most important thing is to get it out the door and make money.
>
>Now it's better that the price is high enough for this strategy to work. Why? because if those (customers) that bought it complain about things not working or not there as advertised you'll be luckier making them wait for patches or improvements if they paid a good price. They'll probably think "Well I already paid a lot of money for what I have and already our data is in there. So we'll wait and see for a while to see what is going to happen with what we asked for. If they don't respond then we'll change to another app." Statistics show that only a minority will change the app. because of all the promises of the company making the app. And after that the longer the wait the less the probability of them changing the application.
>
>There will be patches released and improvements made but those won't be the priority. Priority is to sell a lot of that (unfinished) app so that potential competition won't really have the time to react.
>
>This is how some make money fast without really delivering a complete app.
>
>
>
>The other way is to work long and hard on making an app complete with keeping the bugs total as low as possible. In a word making an app. that even those making it would use it they had to <g>.
>
>
>The second way should always be the way to go but the first option always complicates things. So because of it the perfect timing has to be applied for the release of the app. Bugs are ok as long as these are not major ones. It's ok if everything is not finished as long as the things not finished are not really major features.
>
>Hmmm now it begins to look like a subset of the first way to make apps. Could it be that there's really one way to make apps? ;-)

Denis;

That could be the case? :)

Tom