On Tuesday, July 16, 2013 5:52:52 PM UTC-7, TreKing wrote:
>
>
> That said ... so you're saying that any user that wants those new features 
> and already supported you by buying the original app has to pay again and 
> have a secondary app installed? That, sir, is a *dick move* (pardon my 
> French) and will likely earn your current app quite a backlash.
>
> That said, I, for one, wouldn't think of you as a bad person if you did 
decide to do it that way. Or the way that Trekking suggests. Or a different 
way of your choosing. 

It's a business decision. It has to be worthwhile for you. 

Just because people feel entitled to updates and great new features 
throughout eternity because they paid a few bucks two years ago doesn't 
mean that they are. That attitude is somewhat unique to the app world. Try 
going to a car dealership and tell them to install a dvd player and leather 
seats in the car you bought two years ago because it comes standard in this 
year's car. 

You just need to decide how you are positioning this. 

If you decide the app as it is today still has evergreen value, but that 
the new, enhanced app serves a more demanding market who are willing to pay 
more, that would be a reason to have a separate app.
You could decide that the new features are a valuable addon, that a number 
of people will want and be willing to pay more for. That would be a reason 
to have it as an inapp purchase. 
You could decide, in an act of self serving benevolence, to make the 
present app free to run up its usage, giving you a greater pool of people 
to sell the new shiny version to. 
You could, as Treking suggests, decide that your product is maturing, and 
what people have paid for the first two years was an "introductory" price, 
then raise the price as the new features come in.  

No path will be without its detractors. You may get hate mail for raising 
the price of an existing product, but if they aren't willing to pay the new 
price, that keeps their comments off the new version. 
There could be some backlash on the old version's ratings if the new 
version is available at a price., but the new version will benefit from 
having the most grateful and least whiny users, so its rating will likely 
benefit. 
Make your old version free, and some people could be mad that they paid for 
it before that. 
Some will object to paying an in app purchase fee for new features. 

But at the end of the day, do what makes you the most money that you can 
still feel good about. 

I'm not saying I've set a good example. I've given my users a lot for free 
over the last three years. But I have solid data to suggest that I'll be 
out of business if I do that for everything. That wouldn't serve users in 
the end much either. 

Nathan
 

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to