So, I have made an app and it's getting it's fair share of action on the Play Store. It is free and currently contains no adverts.

I am nearing completion of integration with Flurry Ads. I am also planning on putting in custom event tracking into the next release.

My question is, is it a bad thing to post updates for something like this and containing no update to user experience. i.e. Will users get pissed off and complain via review that the update is for ads?

Or should I hold back on the update and try and implement a new feature for the user.

Do you have any new features in the pipeline, or is the application as feature-full as you would want it to be? (i.e. would you just be thinking up a new feature just to release it alongside the ads, or are there actual additions you want to make in the future?)
–
JonW♦Jan 13 '13 at 11:51

It's pretty much finished. But there is one feature i'd like to ad in the future but i'm still investigating it's implementation.
–
conorJan 13 '13 at 12:21

1

Unless your users really, really want to see ads, yes, it's a terrible thing to do from a UX POV.
–
DA01Jan 13 '13 at 22:07

4 Answers
4

Who can honestly say that whenever they update an app that they notice all the changes or expect to notice them?

Apps update all the time where people have no idea what changed in them, so updating so that you can have better analytic tools in the app is a good enough reason. Just don'l lie about what the update contains. Don't call it "bug fixes" if it isn't.

Are you sure they'll feel cheated? Plenty of apps update with just 'bug fixes' or other such minor updates. Are you saying that users don't like updates like that either?
–
JonW♦Jan 13 '13 at 12:16

2

Well, I personally think they might feel cheated if the only thing they notice is a poxy ad bar.
–
conorJan 13 '13 at 12:22

1

@JonW If I am using an app regularly and after update instead of updates I find advertisements I will probably feel cheated or mislead. But I don't mean to take a hard stand on this, just suggesting not to take a chance.
–
ripu1581Jan 13 '13 at 12:25

Not that I recommend using dark-patterns, but one thing I suppose is rather common place in these kinds of situations is to add a "overly generalizing" point to the changelog. Something like

- general improvments to the application

The idea being that even if users find that there is no noticeable change other than the ad implementation, they still might think there was value added to their experience based on the changelog statement implying improvements.

Again, I would think twice before going this route, but it is a solution. In my view it is still better than announcing that an update has an exclusively negative impact on user experience, i.e. ads - and most likely it is not a straight-out lie as such, if you even improved the code in any way, which I am sure is something you do along the way of new implementations.