> > Problem is, half the time we don't know. Users post 1* Market comments > saying "Force closes on Droid" or "Doesn't work on Samsung Moment", > and unless you have that specific handset to test on, you're SOL. You > "sanity check" on an emulator instance of the same resolution and OS > version, and nothing is obviously broken, so where do you go? > > The increasing array of hardware devices (with different OS versions, > screen sizes, and crappy vendor-specific UIs) simply exacerbates the > structural problems with the Market, where it's far too easy for users > to downrate apps, and with no meaningful way for the developer to > respond. Put another way, the current Market punishes devs for ANY > "flaw" in their app, real or perceived, and the diversity of the > device ecosystem is bound to generate such "flaws". > > I recognize that nobody (including Google) can force OS upgrades to > existing devices. That responsibility lies with manufacturers and > carriers, and all too often, they shirk it in favor of selling the > next handset of the week. Perhaps Google could apply some pressure, > perhaps not. At the least, please ensure that "Google Experience" > devices have sufficient RAM to enable future upgrades; I'm still > bitter about the G1's memory limit, which makes me feel like I'm being > punished for being an early adopter. > > What Google CAN do is improve the flippin' Market. It's routinely > mentioned as one of the weakest links in the Android chain; the > upgrade with 1.6 was a step in the right direction, but many more are > needed, benefiting both users and developers. Addressing some of the > many Market issues on b.android.com would stop so-called > "fragmentation" issues from being magnified the way they now are. >
While I agree with you 100% about the market being underwhelming for both the user and developer, there is something you can do about the feedback comments left on your app. First, download and install your app to a device from the market. Then, when you see a comment that needs responding to, add a comment. Your comment will appear directly above the last one made. If later on you see another comment you need to respond to, simply update your comment. It will move to the top of the stack again. I preface my comments with: "Developer Comment:" There's no guarantee that the poster will ever read that response, they usually are done by the time they leave a negative comment with the words "uninstall" but future downloaders will read your response and know that 1) you read the feedback, 2) you respond to it and 3) you're proactive in support. Here's one I got recently on my "Radar Now!" app: Richard and Victoria 01-19-2010 * I live in Imperial Beach CA and its right by the US/Mexico border so the app kept reading my location in Mexico. I uninstalled immediately. Please fix. Obviously, I have no control over how the cell towers compute this person's location so there is nothing I can do to "fix" his problem other than tell him to move. My response was as follows: maps.huge.info 01-19-2010 ***** Developer comment: Your location is computed using the cell towers in your area, the only way to improve: disable that service and use gps. At least this shows I read the comments, have an understanding of the problem and can respond to the user in an intelligent and thoughtful way. Richard and Victoria will never read this as that user has already moved on, but other readers will see my feedback. -John Coryat "Radar Now!" "What Zip Code?"
-- 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
