When developing your mobile app/game, you know that you have to keep in mind several design aspects, specially engagement (retention), acquisition and monetization.
There is a very famous framework called ARM (Acquisition, Retention, Monetization) that says that you first need to focus on acquiring users, then engage them and only for last try to monetize them. After all, does not make sense to monetize an app/game that does not have a minimum number of DAU (daily active users).
I have a problem of the ARM. At same way that it correctly poses that does not make sense to monetize before you have a "steady" user base, I don't think that makes sense to acquire users if your app/game doesn't provide them with an good experience that would makes them return to it again. So, I prefer to act in a RAM framework (not it is not the memory :) RAM = Retention, Acquisition and Monetization).
I came across with a presentation made by Kontagent (a analytics provider) and they showed a framework that is similar to what I think should be the ideal framework to be pursued by a mobile app/games developer. Of course, if you mobile app is more like a service app, the retention would not be something as relevant to you as would be for a game developer. Here is their framework:
There is a very famous framework called ARM (Acquisition, Retention, Monetization) that says that you first need to focus on acquiring users, then engage them and only for last try to monetize them. After all, does not make sense to monetize an app/game that does not have a minimum number of DAU (daily active users).
I have a problem of the ARM. At same way that it correctly poses that does not make sense to monetize before you have a "steady" user base, I don't think that makes sense to acquire users if your app/game doesn't provide them with an good experience that would makes them return to it again. So, I prefer to act in a RAM framework (not it is not the memory :) RAM = Retention, Acquisition and Monetization).
I came across with a presentation made by Kontagent (a analytics provider) and they showed a framework that is similar to what I think should be the ideal framework to be pursued by a mobile app/games developer. Of course, if you mobile app is more like a service app, the retention would not be something as relevant to you as would be for a game developer. Here is their framework:
If you have some free time, you can watch their full presentation below.
On my next post I will talk about setting up AWS Push services so you can use it with your mobile app/game.
See you.
See you.