- Jan 20, 2014
- 32
- 0
- 0
Hi,
I come from the iPhone side when it's about mobile development.
There (some years ago) it was typical to provide two apps "Super XX free" and "Super XX" - or "Super XX" and "Super XX pro".
Anyhow - one app was free and you could update to the paid version.
Nowadays it's (if I'm not wrong) there are other models.
From my point of view I have two possibilities.
Provide a paid app with trial.
Or provide a free app with IAP.
In both cases paying will result in "more functionallity" or "no adds" or something like this.
To be a bit more specific.
a.) I don't like adds - and from what I hear they don't bring much revenue
b.) My app has three potential customers (users).
b1.) The ones doing little
b2.) The ones doing a bit more
b3.) The reals pros (doing a lot)
So for b1 I provide a "light" version and for the others a "pro" version.
b2 can still work with "light" - but it isn't so feature rich (in some place a bit more complicated) to use it for b2-needs
b3 definitely knows that he needs pro - he can check with light but will switch (if he likes the app) for sure
To be a bit more precise with the "two apps" I want to explain my expectations.
Users of the free version should build a base - and make the app popular.
The paid version shell bring money.
And a last word (why I don't even think about two different apps).
The app collects data (users enter data) which is important for users.
So when they want to upgrade they shall keep all their things.
Or in other words - go on using the same app with enhance functionallity.
I published my app as paid with trial.
Asking a number of colleagues what they think about it and the response was (mostly) they wouldn't take a closer look since it costs money.
So I'm thinking about the IAP solution. Although it looks a bit more complicated (just had a short look on the workflow) but the "first impression" of a free app seems much better.
Has someone experiences with the two models?
What works better?
I come from the iPhone side when it's about mobile development.
There (some years ago) it was typical to provide two apps "Super XX free" and "Super XX" - or "Super XX" and "Super XX pro".
Anyhow - one app was free and you could update to the paid version.
Nowadays it's (if I'm not wrong) there are other models.
From my point of view I have two possibilities.
Provide a paid app with trial.
Or provide a free app with IAP.
In both cases paying will result in "more functionallity" or "no adds" or something like this.
To be a bit more specific.
a.) I don't like adds - and from what I hear they don't bring much revenue
b.) My app has three potential customers (users).
b1.) The ones doing little
b2.) The ones doing a bit more
b3.) The reals pros (doing a lot)
So for b1 I provide a "light" version and for the others a "pro" version.
b2 can still work with "light" - but it isn't so feature rich (in some place a bit more complicated) to use it for b2-needs
b3 definitely knows that he needs pro - he can check with light but will switch (if he likes the app) for sure
To be a bit more precise with the "two apps" I want to explain my expectations.
Users of the free version should build a base - and make the app popular.
The paid version shell bring money.
And a last word (why I don't even think about two different apps).
The app collects data (users enter data) which is important for users.
So when they want to upgrade they shall keep all their things.
Or in other words - go on using the same app with enhance functionallity.
I published my app as paid with trial.
Asking a number of colleagues what they think about it and the response was (mostly) they wouldn't take a closer look since it costs money.
So I'm thinking about the IAP solution. Although it looks a bit more complicated (just had a short look on the workflow) but the "first impression" of a free app seems much better.
Has someone experiences with the two models?
What works better?