I would like to know how many new users (without account) have used my mobile app this month and i would like to know between the first times that they have used the mobile app, if the have came back many times later.Is it possible to know that or not ? How do ?
@LuckyTravel no “ready-made recipe” for you here, you can explore Mixpanel or AppsFlyer (there is an SDK integration by Cosmith.io). Maybe they can help.
The only alternative I can imagine is creating custom component - storing some unique ID (based on phone ID or random number) in the local storage at the 1st app launch, along with date; reporting this as a 1st login to your backend; then in each launch report this pair again. You can do smth like that based on Pragmaflow’s Adalo-local-storage code, but some effort will be required.
Long time ago I managed to store the id locally and identify same “anonymous” user at the next time, but that was long ago as I said
Mixpanel and AppsFlyer are free or i have to pay to use it?
“storing some unique ID (based on phone ID” → yes, i thought exactly like you But on Adalo, you think that it’s possible do to that? (like it’s no code)
@LuckyTravel you can check pricing on the respective websites. Both have free tiers.
I can’t say whether free tier is enough for your requirements or not.
In “vanilla” Adalo getting and storing unique ID reliably is not possible.
Technically, it is possible to store some values in local storage; this is what Pragmaflow’s component does. But you have to build and maintain it by yourself.
Also Adalo may store the values of the inputs in local storage and there was a workaround to put an input onto a separate screen, update its value and then retrieve it later on. The issue with this method is that nobody knows how Adalo treats local storage and when it removes values from it / cleans it up; so building something reliable does not seem to be possible.
I would create a feature request asking to have a proper local storage access in the builder itself. Ideally Adalo should include something like SQLite, but Key-Value storage is already good to have.
@LuckyTravel “maintain” means that you will have to create fixes for bugs and update component when underlying platform changes. E.g. Adalo can update version of React and you will have to check and update (if needed) your component to match this new version.
Pragmaflow is a company. I don’t know its value but I think it can’t be purchased anyway.
Some time ago they have developed multiple custom components for Adalo. The source code is available on the Github. You can download this source code and use it according to its license. As I remember modification is permitted but anyway this needs to be checked. Also you can check if you have any other legal obligations like royalties, etc. Download is free, usage terms is defined by the license.
I have absolutely no idea whether their component will work now or not. Moreover, I think that even Pragmaflow do not know that, as they are not maintaining Adalo components anymore.
How this component works with (or without) modifications - that’s solely your responsibility.
Basically, when you are developing the custom component, either starting from scratch or based on other codebase, nobody is responsible for its functionality except yourself.
I would recommend searching the forum if you’re interested in Pragmaflow’s components, there are a lot of discussions on this.
I will go to see the forum of Pragmaflow but if it don’t find what i need, what else solution i have? You suggested me to go to see with MixPanel and AppsFlyer because you think that maybe that they can have a solution for that, right?