I'd be adding features for the paid version, not removing any (unless programatically impossible to mix them).
I'm finding the users pretty fickle actually, at least 10% actually download the thing not knowing what it does and give it a one star when they don't read the installation instructions (it's an input method). Anyway, I had intended it to be free, but people are asking for features that will cost me to implement (more than it already does in time), so I'll do the work, but they can help defer the cost. Because it's an input method, it's pretty hard to add special buttons! Most of what I want to add can be done as a separate content provider, so I'm thinking that's the way to go. I think Google really has to fix the market though! - Brill Pappin On Dec 2, 3:42 pm, Brill Pappin <br...@pappin.ca> wrote: > I've got a situation a lot of us do, where I have released a free > version and now need to make a Paid version of the same app. > > As those who have tried will know, you can't change an app from Free > to Paid (a silly feature of the Market). > > So, what I'm planning to do is release a "Plus" version that has more > features. > > What are others doing to help direct users to their paid versions from > their Free versions? > I'n my case its an input method, so I have to be careful about how I > tell the user about the paid version with more features. > > Comments? > > - Brill Pappin -- 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
