@David That’s what I’d like to know.
I would like a clear definition of “App Action.”
@David That’s what I’d like to know.
I would like a clear definition of “App Action.”
Adalo, you can review
How will these actions be consumed?
I need to know if it’s viable, because I won’t be able to control the users.
I ran a test of the actions. For my app if one customer performed 50 actions a day:
Open home screen = 4 actions
Adding steps = 2 actions
Mood Tracker = 2 actions
Add a Note = 2 actions
Food button = 1 action
Food search = 1 action
Add meal = 2 actions
Back to home = 4 actions
-----------
x 3 = 54
This is just adding one meal to the their diary w/a note and a mood tracker. I multiple by 3 for 3 meals a day and this is the minimum because I have other features in my app that I am not even calculating.
I am a 1 person shop who does need the Collections API (I am happy they moved this to the Professional Level). So I would be on the Professional level w/30,000 actions per month. That is only 1000 actions PER DAY. Which would calculate to 20 customers per day to reach the limit.
WOW… that’s all I have to say!
This does push the users to the business plan in the long run if they want to grow the app to a level where there are many users. App Actions add up pretty quickly!!!
It’s a big jump in pricing between Professional to Team or Business. I just can’t afford it unfortunately. I love Adalo, probably one of the top 3 platforms that I have used in my career. Yes, it has some issues but I was confident they’d work everything out eventually. So I stuck with them.
I will now have to consider other options as the app actions approach just isn’t a workable solution for me. Not sure it will be for many unless that are on the Business plan.
FYI: You can test your actions via your settings, usage & billing.
another doubt that I did not find on the site (latest information)
using a system inside WebView will actions be counted?
@preptogether @Rios @Tsubasatwi @simm and others
For those asking what is an action - the very first pricing change blog post had a link to the help docs which clearly stated what constitutes an action.
This is the list below - screenshot from that page.
I should write that it is the list as of today, because it could change in the future.
@tjd_15, Thanks for posting this.
Bonkers springs to mind.
Changing an input value? Surely that is done on the device. Link to an external website??? Link to a screen!? Better let AWS know so that they can overclock the processors.
That list is petty but hey…fine if Adalo want to get ‘micro’ on the detail.
The macro perspective… Adalo aren’t including enough actions within the paid subscriptions and the overage rates are too expensive.
Or your customers are wrong, they will pay your rates and they won’t leave in droves to flutter.
Or you have a flood of potential customers ready to sign up and pay for silly things like underlining text. Maybe they will pay extra to use emojis too
Let’s put the shoe on the other foot.
Adalo refund me a month subscription for every genuine bug I log that remains unfixed for 4 weeks. Pay me a dollar for every minute I spend scanning through a list of 30 collections that are not in A-Z order.
We’ve been with you from the early days and waited patiently. This is not how to treat long standing customers / partners. If you don’t grandfather those of us who have built apps and businesses based on your previous structure then I have no doubt many will leave. By all means increase the price, but don’t move the goal posts.
@David we have a call next week. At this rate it will be an exercise in retention.
Ok, cool. So an action equates to just about everything.
Definitely don’t piss off any of your customers if they figure this out
Some points to consider:
If all these constitute actions, there are some features that won’t be reasonable to build with Adalo.
Take the Chat feature. Each new message probably represents a Create Message, Update Conversation and Trigger Notification action, at least.
Then we have some strategies that we’ve used and have been advised to use, to disguise some performance issues, like using Lotties when some complex set of actions is being done. That alone are 2 actions (turning the Lottie on and off).
Additionally, we’ve also been advised not to have many lists on the same screen, which means they’re in different screens that need to be linked to one another (more links, more actions).
Overall, many of the strategies that us makers had to implement to disguise Adalo’s limitations will now represent an increase in our plan’s price.
Is that fair?
Even after the revised plan, is still a joke for me. You can increase price and it’s fine, limit some features for lower plan is ok, I accept that too…
But I will never accept the action limit which is ridiculous, if you just want plain apps with bad design and 30 users maybe they are enough… But a well made application needs much much more than that.
if I have to develop an app knowing that I have to limit actions to a minimum to spend less, there is something wrong.
Just the underlying concept that is wrong
Just to say, a client that knows how Adalo pricing works, could potentially make the developer spend more just doing ghost actions for fun… Is that fair?
This!
A cap on app actions + charging for more seems to be a 100% monetization move by Adalo more than anything else (server load, etc). Until we hear more details as to why even have actions cap.
The math between app actions across all plans doesn’t make sense either.
Hey @David
Can you please go into more detail as to why/how you came up with these app action numbers for these plans?
How were app actions calculated to determine these averages for these plans?
Most importantly, why even lock us into app actions?
Awaiting your response. Thank you!
The problem that after 12 months what do you do with all the apps that you already have loaded from old clients and those that you are creating now? … you will surely go from 50 to 250dls without scale… maintaining the plan now is like a help but not a long-term solution … imagine now you make 5 apps you get 10dls a month each one in 1 year it will cost you 50dls each … the price is crazy and pray that the actions in the app are not exceeded but you can go from 250 to thousands of dollars. SO CRAZY!
Thanks!!!!
The manual was unconfirmed.
It was very helpful.
I started learning flutter flow today, because most of my clients would navigate from different pages just to explore the app.
Well I’m still with Adalo from now, in the future I would have to upgrade to avoid losing my clients
I was just about to subscribe to Adalo but this new plan is super horrendous. Adalo’s default actions are so basic that you have to use at least a couple of them to get anything done. And, the custom actions are actually not custom actions they are just API integrations. If I launched my first app using Adalo today, it would consume the action limit within a week or two. I don’t mind the app limit, but action limitation is a big no unless they update their actions to be much much more flexible. I hope they reconsider or I’ll be forced to create the app from scratch using another provider.
Thank you!!
Hi @David @Santiago and others following the thread
Exactly why I am pushing the notion of grandfathering existing builds and anchoring their performance on today’s infrastructure / performance.
This is fair from a user perspective:
We have built apps in good faith that the price of the monthly subscription and overage price for gigabytes of storage might well increase. Who would ever imagine such a pricing system, finitely measuring what an app does down to a button by button level. Go ahead, increase the monthly $50 to $65 per month, but don’t think you can add all sorts of counts and conditions and be applauded by your customers. Everything else should remain, nobody is asking for a lifetime of freeloading, ring fence, throttle, freeze the performance levels of today.
We have learned to use Adalo from scratch and worked a lot out for ourselves, OK it’s fairly straightforward, kudos to you guys, but it is not perfect, refined or finished by a long way. As a maker if you want to build something worthy of revenue then there is a tonne of bugs / nuances / unwritten limitations / hacks to overcome.
We have waited, waited, waited and endured, for long over promised performance updates. There is still much work to do from Adalo’s side. Now that Adalo have released Location and Performance upgrades they feel they can get away with a price hike and fill the hole in their business plan pricing structure. There is no way you would have tried this in a different order.
We report bugs to be told they are low priority and there is NO timeline for when it may be dealt with. So we wait, and build around the problem, with an excess of actions.
!! SOLUTION !! Fix the bugs, improve your components, run stricter controls on 3rd party components and maintenance of them, then we can strip out some of the actions.**
We report shortcomings in Adalo components - same answer, NO timeline. Date picker as an example. Also…Location input box is a “new” component but has issues. We routinely pick up very simple things that your devs have not implemented or tested for, only for them to be swept under the rug.
We turn to the forum for support, and help each other where Adalo has failed to solve their issues in a timely manner. In doing so we foster a community, largely without input from Adalo. This community serves to support a user base for Adalo and surely eases levels of churn. We do this for no reward other than perhaps the help that others can give us in the community.
If you are hell bent on pushing this new pricing scheme then it is clear that ALL of the above that WE have GIVEN YOU FOR FREE means nothing. Some will leave because of price alone, others will leave because your performance / price ratio is poor, some will leave because they feel spited, some will leave because they have lost faith in what Adalo promises v does. Who can build a business in an ecosystem with such uncertainty for future planning?
Keep your existing customers happy. By ring fencing existing apps or accounts you can keep your early and existing customers happy, we are your foundation and knowledge base, who are willing to tell the world about Adalo. Few of us disagree that $50 needs to increase, increase that if need be, inline with inflation and costs that have increased to you.
Ring fenced apps do not benefit from further Adalo upgrades, better components etc… Any customer that wants to benefit has to upgrade to your new pricing schedule, on an app by app basis.
BTW on your current Adalo pricing table, you claim.
Create advanced logic for filtering & visibility based on and/or rules.
That’s not true as of yet.
Final rant…
Adalo is deceptive, it seems so simple… start on a journey building an app, then you begin to feel the reigns holding you back, you can’t null a value (unless you set Date=None), you can’t load a date into the date picker. Just a couple of the nuances I refer to. With all these holes in your system you you can’t rely on the App Academy to bring on the next round of low tier signups, they will fall at the first hurdle not properly documented (there are lots), you need a contingent of happy users singing about Adalo on the forums, helping them over hurdles, building you up, working with support and devs, not grumbling and talking everything down.
You have enabled no coders to build something, you have also opened their eyes to other possibilities, Adalo can be a platform for building your app and webapp, never having to look elsewhere, it can also be a step up to slightly more complicated no/low code platforms. Adalo is not infallible, your users can leave, are leaving, and are not signing up (see above post). Other platforms are waiting to welcome them. I implore you to make this right and get everybody back on your side in a fair way to all.