If you want to do logging and avoid a server, try this
http://talkingandroid.com/2009/11/04/droiddrop-remote-logging-for-android/
It uses drop.io api to fulfill server piece.

On to the post:

> 1. negative comments from rival devs (check the major apps comments boards
for some very troll like comments)

I think if this was pervasive a complaint might work.  But there are a lot
of haters out there

> 2. comments from users who haven't taken the time to learn how to use the
app or contact you for help

Make it really easy to contact you for help.  Put an email link in your app.
Create a how-to video and link to it on Youtube.
Say in your desceription: Please Contact me if you have an issue.
Create a first time user experience that takes the user through a demo.
After that?  Ignore the truly igorant.


> 3. comments from users who have a handset where your app crashes but this
handset only makes up for 2% of installed userbase

Or who have a custom ROM on a phone?
You still have to determine if there is a real issue that affects others.
Maybe this group sees it more.

> 4. comments from users who have an old version of your app where the bug
they experience has already been fixed

Google has a recommendation for this somewhere.  Check the current version
of the app, have a server somewhere with the latest version,
Detect and compare.  I haven't done this.  But PackageManager looks like the
key
http://developer.android.com/intl/zh-CN/guide/publishing/versioning.html

I've thought it would be valuable to have a discussion forum library that
could be embedded into apps for better customer service.
Any thoughts?

Carmen
-- 
Carmen
http://www.twitter.com/CarmenDelessio
http://www.talkingandroid.com
http://www.facebook.com/BFFPhoto
http://www.twitter.com/DroidDrop

On Mon, Feb 1, 2010 at 4:47 PM, matt smith <[email protected]>wrote:

> thanks for the tips but i already have a log collector for my app -
> this is not the issue - even if the problem on certain handsets can be
> identified, there is still no way of preventing comments coming in
> which imply the app works on zero handsets - and then there's still
> the three other types of harmful comments which i believe make it very
> difficult for devs even with decent apps :
>
> 1. negative comments from rival devs (check the major apps comments
> boards for some very troll like comments)
> 2. comments from users who haven't taken the time to learn how to use
> the app or contact you for help
> 3. comments from users who have a handset where your app crashes but
> this handset only makes up for 2% of installed userbase
> 4. comments from users who have an old version of your app where the
> bug they experience has already been fixed
>
> Put another way, when a solid app doesn't have many competitors, e.g.
> PicSay, it tends to get almost exclusively 5* reviews. Compare to apps
> of similar quality but which have heavy competition, these seem to get
> much more mixed reviews.
>
> --
> 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]<android-discuss%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-discuss?hl=en.
>
>

-- 
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.

Reply via email to