On Wed, Nov 3, 2010 at 1:34 PM, Lance Nanek <[email protected]> wrote:

> I have an updated version of a puzzle game I do the programming for in
> private beta right now. It adds support for multiplayer challenges. I can't
> imagine putting a change like that in this new field.
>

Why not? It's a new feature and is what changed, right?


> People might search for multiplayer wanting a multiplayer game and my app
> wouldn't show up.
>

If it's a major feature you want to highlight and think people will search
for, that's what the main app description is for.


> I suppose I can put bug fixes in the new field.
>

You can put whatever you add / changed / removed since the last version -
including new features that you also list in the description.


>  Making it non-searchable is not encouraging me to use it correctly.
>

I disagree. The point of a change log is to inform your CURRENT users what
you've added when they get the little update notification. Current users
aren't searching for your app - they have it already. Making it searchable
will just lead to developers using the space to add more features and
keywords, not actual changes. Making it non-searchable removes that
incentive and encourages it to be used for it's intended purpose.

That said, though it's a nice change, I think it would have been better to
simply double the description field and let developers use it as they see
fit, which would make your change log, if you felt like adding one,
searchable. Oh well. At least they're continuing to improve things.

-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices

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

Reply via email to