Yeah I’ve discussed this with Ashley from Adalo, but haven’t found a straightforward solution.
There are just too many possible states of subscription, upgrade, downgrade, cancellation etc. to be covered entirely by building something within Adalo as a user vs. Adalo offering it as a fully functional module. In my case I think building something is a little more risky in case some use-case is left out as not built.
Best solution I could think of - You need to separate the gating from the Adalo App itself. Gating happens at Site A, and App is hosted at Site B.
You should have all your gating externally (because you can’t pass login information from another service into Adalo), say Webflow checks for a Unique Account ID, use Memberspace for gating a webpage which redirects to Adalo sign-in links (eg buttons to login to your app), and then users are able to access your Adalo App by logging in with their email & password.
- Within Webflow, you would have to constantly update Adalo App Link
- Within Adalo, you would have to make copies of your app every week or so, and paste the new link into webflow, and delete ‘old’ apps
This is done so that your users don’t bypass the gating mechanism in webflow by bookmarking your Adalo app domain (where previer.adalo… or your custom domain), and just access the app directly via the bookmark.
Creating copies of new apps and deleting would ensure even saved bookmarks would stop working after a while, and only paid members would have access to the latest ‘builds’ or links of your app.
Ideally you should not have a custom domain, and use only adalo’s previewer… sub-domain, to avoid the bookmarking of sub-domain for permanent access without paying subscription.
Worst case scenario is a non-paying customer is able to access your previer.adalo.com app for a duration until you delete it and replace with the latest version of your app. So it depends entirely on your build/update frequency.
To summarize - www.myapp.com (in webflow) -> Entering Unique ID leads to accessing app.myapp.com -> on this page is the a button, which links to most updated & only active version of your app, hosted on previewer.adalo.com…, which you keep replacing by making new copies of your app very frequently.
This would still involve a user going to your www.myapp.com domain, entering a unique userID, then one more click, then entering email & password, then one more click to access app, which is terrible UX.
Its ugly & got too many moving parts, even I have not implemented it. But its the most reliable solution I could think of thus far.