On the "Don't update if it ain't broke" anguish, You could add a "subscribe to receive beta before everyone else" alert box the first time your user launch your app. The alert box sends then on a subscription form on the internet and you gather models and emails.
Then when you're about to release an update, you send them the beta in an email with a qrcode to the apk on your server. That's a lot of work though, maybe just go the Microsoft way : "Our beta-testers ? Our users why ?" :D Maybe just use the alertbox to ask people to report bugs, and add a "report bug menu". You collect both the bug and the type of the phone and send it to you by email. Anyway, the worst that can happen to an app is to get stuck to v1.00 :D Good luck. Yahel On 5 mar, 05:52, "Maps.Huge.Info (Maps API Guru)" <[email protected]> wrote: > I certainly can feel your pain. Radar Now! (125,000 users), which is > in your same category, just down the line a few slots, has made me > very nervous about updating. The last update I released, about a month > ago, seems very stable and has generated very few complaints. I'm in > the "if it ain't broke, don't fix it" mode now, which kind of stinks > as it could use some new features. When I get my new N1/Droid, I'll > work on an update but not until then. > > -John Coryat -- 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
