On Wed, Sep 1, 2010 at 7:14 AM, Tauno Talimaa <[email protected]> wrote: > Indeed but imagine a case where you have two options (after spending quite > a lot of resources on a project already): > a) Don't release your software at all. > b) Release your app and use hidden constants( that do work on current > devices) but risk with the fact that your application will break in the > future and you have to fix it again. > Which one would you choose?
The right answer is: c) Do your homework first and don't write apps that can't be implemented -- the carrier limitation you describe is a well-known problem Of the two choices you outline, if your end distribution channel is a pre-load on a device through a specific carrier, go with b). Or, if this app is being done on a consulting basis, and the customer gives the go-ahead, go with b). Otherwise, go with a), because the future costs (in terms of time, reputation, etc.) have a good chance of exceeding your revenues. I am all for lobbying to have this promoted to be in the SDK, because it's a seriously useful feature, for a variety of reasons (though I could see requiring a permission for it). If there's no issue in b.android.com about putting this in the SDK, you may wish to add one. However, the business decision for going forward with distribution has to be made on future costs and revenues -- it does not matter one bit how much time you have put in to date. If the costs are controllable (i.e., distribution is limited to certain devices), or if the costs are incurred by somebody else (i.e., consulting client), and the revenues are known, it may make sense to run the risk. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Development Wiki: http://wiki.andmob.org -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
