On Mon, Jul 12, 2010 at 11:58 AM, Maps.Huge.Info (Maps API Guru) < [email protected]> wrote:
> The app was installed by approximately 200 users from all over the US, no > issues reported. That seems to me that it's stable. > That's good to hear. However, we don't all have beta groups and multiple devices to test with. I suspect that the vast majority of devs only find out about issues after releasing to Market and getting a flood of complaints (in the comments of course). Really, what can you lose? > A lot of time, and a good chunk of your ratings if things go wrong. Why risk it for a 200K app? > If it becomes a problem, simply take it out. > And get even more complaints for taking a feature away after adding it. Although this brings up an interesting point. What happens if you enable this, have people use it, then take it out? What happens to the ones that have installed to the SD when they update? > Seems like a winner to me, but then again, I've been labeled an optimist. > Nothing wrong with that - I'm fairly optimistic myself. But I'm also practical. I don't see the point in adding in a new entry to "the list of things that could go wrong", regardless of how "simple" it may be, simply because it's the cool new thing in Android when it won't add much value (for me at least). To each his own, right? ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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.
