I have an application that is being developed for a long time. It is going to release 5, with at least 10 updates during its lifetime.
The current release of the app is very different from the original first one. I have improved it more and more but all this time I am giving updates for free. Now I am considering creating another application and keep the old one alive.
The idea is this.
CURRENT APPLICATION - I keep the current app live and eventually create maintenance updates if some bug show but don't improve it more. The current version has more than 100 functions. This app is on the TOP 50 on its category, but it is floating wildly. One day it is #28, the following day it is #150... (I simply don't know why).
NEW APP - I create a new app out of the old one. This new app would be essentially the old one with a new interface and with the legacy part removed (the old app has a legacy part in the code, specially with the file import routines, in order to be able to read files created with several releases of the app).
So, my question is: what do you guys think? Will this be ok? How would you do?
I have an application that is being developed for a long time. It is going to release 5, with at least 10 updates during its lifetime.
The current release of the app is very different from the original first one. I have improved it more and more but all this time I am giving updates for free. Now I am considering creating another application and keep the old one alive.
The idea is this.
CURRENT APPLICATION - I keep the current app live and eventually create maintenance updates if some bug show but don't improve it more. The current version has more than 100 functions. This app is on the TOP 50 on its category, but it is floating wildly. One day it is #28, the following day it is #150... (I simply don't know why).
NEW APP - I create a new app out of the old one. This new app would be essentially the old one with a new interface and with the legacy part removed (the old app has a legacy part in the code, specially with the file import routines, in order to be able to read files created with several releases of the app).
So, my question is: what do you guys think? Will this be ok? How would you do?
I think it's ok.
I am thinking of the same thing for one of my app. It would be nice to provide users with free new features for years on a $.99 app, but sometimes, it just doesn't work so well.
Do you still think of having the old app in the app store? Would it mention the new app in the description as being the current one?
Two scenarios I can think of:
- Old app becomes Lite version, free with iAd, and link to upgrade to Pro version. That strategy worked out well for me.
- Two price points, one for old app, one for new; similar to what Apple does when selling a new iPhone, previous one still on sale for a lower price. Problem is you could split your sales between two versions, that could have a negative impact on rankings.
I think it's ok.
I am thinking of the same thing for one of my app. It would be nice to provide users with free new features for years on a $.99 app, but sometimes, it just doesn't work so well.
Do you still think of having the old app in the app store? Would it mention the new app in the description as being the current one?
Two scenarios I can think of:
- Old app becomes Lite version, free with iAd, and link to upgrade to Pro version. That strategy worked out well for me.
- Two price points, one for old app, one for new; similar to what Apple does when selling a new iPhone, previous one still on sale for a lower price. Problem is you could split your sales between two versions, that could have a negative impact on rankings.
I have a bad experience with lite versions. People have the app and very few buy the app. I cannot also transform the current one (old) in a lite version, because it has too many functions and I would not like to cripple who bought it.
My idea is to create a new app, a new name and stuff and see if it climbs the ranks. I think the new version is good and can make it to the TOP something.
Lowering the price of the current one can be a good stuff to do...
If I could go back I would NEVER release Tangled 2, it was a mistake. Even though I pretty much rewrote the whole thing, it never quite caught on like the original (still to this day the original is greatly out selling the sequel)
__________________ My Games: My Blog 13" Macbook Air 1.7Ghz Core i5, 4GB DDR3, Intel HD Graphics 3000 iPhone 4S - PSPGo - 3DS - Wii - PS3 - 360
I have a bad experience with lite versions. People have the app and very few buy the app. I cannot also transform the current one (old) in a lite version, because it has too many functions and I would not like to cripple who bought it.
My idea is to create a new app, a new name and stuff and see if it climbs the ranks. I think the new version is good and can make it to the TOP something.
Lowering the price of the current one can be a good stuff to do...
Yeah, I guess it is hard to generalize, what works with an app doesn't necessarily works with another.
Actually, let me rephrase what I said about what worked for me with the lite version:
- I created a new app, 'Lite', that was identical to the full featured app, just added ads. So all users of that app have never had anything but the lite.
- Simultaneously, I updated the original app with the new features, so that the original buyers keep getting upgrades and are not penalized.
So at the end of the day, I have both versions running and nobody upset from not getting upgrades.
Whether you get good conversions form free to paid is really dependent on the app, but I have been selling more paid apps since the free is out, so it works for me.
Yeah, I guess it is hard to generalize, what works with an app doesn't necessarily works with another.
Actually, let me rephrase what I said about what worked for me with the lite version:
- I created a new app, 'Lite', that was identical to the full featured app, just added ads. So all users of that app have never had anything but the lite.
- Simultaneously, I updated the original app with the new features, so that the original buyers keep getting upgrades and are not penalized.
So at the end of the day, I have both versions running and nobody upset from not getting upgrades.
Whether you get good conversions form free to paid is really dependent on the app, but I have been selling more paid apps since the free is out, so it works for me.
fork on update?
Linear Mode
