Hi Blake
Did you ever find a recommended strategy for this ? I am facing the
very same issues, but don't like the option of the intermediate step ?
Regards
Don
On Feb 16, 4:21 pm, Blake B. bbuckle...@yahoo.com wrote:
I'm not worried about the code migration - that's only a half-hour
work
Ok, maybe I missed this along the way (or heard comments of this and
couldn't believe it to be true), but this statement seems clear in the
Setting the price of applications section:
If you have previously published an application for free, you cannot
change it to have a price.
This seems to
Developers could always add a couple of features and charge for the
feature added version.
Al.
Blake B. wrote:
Ok, maybe I missed this along the way (or heard comments of this and
couldn't believe it to be true), but this statement seems clear in the
Setting the price of applications
Your interpretation would make more sense, but that doesn't seem to be
the way it's being done.
I don't have the option on my current app to change from free. When I
unpublish it and attempt to Upload an application, I have the option
to set a price, but the publish site won't allow me to
You may need to refactor your code to change the package name to
something line com.blah.nonfree.App and rebuild your apk.
It would seem to offer the quickest solution.
Al.
Blake B. wrote:
Your interpretation would make more sense, but that doesn't seem to be
the way it's being done.
I
I'm not worried about the code migration - that's only a half-hour
work (max) with eclipse Subversion.
I'm concerned about the user experience in transitioning their data to
the new paid version. The user has data in user preferences and a
sqlLite database that they will expect to be able to
6 matches
Mail list logo
