> What does everyone else think? I just am willing to accept missing > features if I know all the phones will be able to get them later on > down the road, and I don't have to tell people they have to have an > Android phone with software version 1.1.56 build 6 or better to run my > app.
Ummmmm... I think there are four different models here: 1. Upgrades are impossible, other than by buying a new handset 2. Upgrades are possible but painful to install (e.g., traditional WinMo) 3. Upgrades are easy (e.g., iPhone upgrade-in-place via iTunes) 4. Upgrades are forced down your throat (which might cover iPhone too -- I'm not sure how their upgrade model works, exactly) Bear in mind that, except in model #4, you *still* need to say users "have to have an Android phone with software version 1.1.56 build 6 or better". After all, just because an upgrade is available doesn't mean the upgrade has been applied...unless it's forced down your throat. That's no different than "you need Windows XP Service Pack 2 to run this program". My personal "sweet spot" is model #3, but that's just me. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.2 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
