11-03-2011 01:07 PM
we want to change our price from free to paid! Do people, who already downloaded the app (BlackBerry Smartphone App) have to pay the price?
- If yes - Is there a way to let them upgrade for free?
Solved! Go to Solution.
11-03-2011 03:26 PM
11-04-2011 12:34 PM
11-04-2011 12:37 PM
I don't know if this is fixed in the latest App World version, but (valid for App World 2.0) if you change the price from free to paid, users who have download the app as free won't be able to get any app upgrades untill they buy the app.
11-05-2011 02:40 AM - edited 11-05-2011 02:40 AM
Does anyone know if it's fixed in App World 3.0?
11-10-2011 03:52 AM
The users who have downloaded the app for free need to pay the X amount if they want to get the upgrade of the application.
But if you are just changing the price and not uploading the binary files, then only new users will be charged and already existing users can use the app for free as they are doing it now.
If you are upgrading the app with new features and uploaded the new binary file and changed the price, existing users will have to pay to download the updated version.
Note: This may attract negative reviews as most of the users except it to be free all the time!
11-10-2011 11:18 AM
OK. Let's say the app costs 1,99$.
For a special period the vendor lowers the price to 0,99$ and customers are purchasing it.
Later the price jumps back to 1,99$.
When the new upgrade arrives, as a customer I never paid for full price. Of course, upgrade price is set to 0$.
Am I wrong?
11-10-2011 12:52 PM
Yes, you are right.
But in this case it is a change from free to paid (no matter the price), and App World (at least previous versions) couldn't handle this. For example you have downloaded the app as free, later the vendor changes it to paid. You cannot download the app again (for example when changing phones) and when the app gets updates, you will receive notification for the update but won't be able to download the update.
During the community insider event Alex Kinsela promised to fix this bug, but I have no idea if it is fixed. And of course I don't want to risk an app to test it