@james.crennan been kind of following these threads lately and I have a curious question…I’m not published natively and only using PWA. Does app size affect that as well? And how can I find out the size of my app?
1 Like
Hi James
Thank you for your much valued input. Your hands-on approach is truly appreciated by me & probably the entire Adalo Community. I have some concerns & I will list these here:
-
I am currently also building a coded app through a development team. It is almost completed and the APK is about 80MB. I therefore don’t understand the 10MB app functioning limit.
-
I am quite sure there are many Adalo apps in the 40-50MB range. This number is gathered from my routine reading of posts in the Forum. Once again the 10MB limit comes as a surprise to me.
-
I have been getting successful builds in iOS and Android over the last 5 to 6 months. This spate of constantly failing builds was only occurring in the recent week since there was a series of Adalo failures (I am sure there have been posts describing the ill-effects on makers in the past 7 days). The consecutive successful builds were done with the app in the 50MB to 80MB range. The build records will show that. I never had time-out then, why am I having it now?
I do understand that a “light” app would function better in all environments & devices and I will takes Support’s guidance on how to make it lighter. I am sure I could get it down to about 40MB but the 10MB limit is a hard target to reach unless I rip out many features that make this app unique. Please note that I am building a production app that would have discerning users with expectations. I always thought that Adalo can be used to build an app that can be marketable because it is unique. If I had known the 10MB limit, I might have been more careful on my choice of design & flow right from the start. Maybe a useful tool would be to display the app size so that makers will be constantly aware of the app size & not be in a fix after a year or more of development.
@eduscvs – okay! We’ve done some deep diving and uncovered that your timeouts were indeed our fault. You are right–even though your apps are quite large, you shouldn’t have been encountering a server timeout. The culprit was a change we made on our end to improve data continuity (and thereby speed). An unintended consequence saw an escalation of requests and responses between a few apps and our servers, resulting in the servers ending the connection. @eduscvs - my aplogies!
This has now been resolved.
We’re dedicating a number of our engineering team to creating a host of testing services to bulk up our staging servers so we can more adequately test out our changes. This will mean our AI rollout will be a tad slower, but we have to get the foundations right first.
Regarding the 10MB guidance - this is a north star. We cannot stress enough that a smaller app will give you fewer problems, and we’re doing a lot on our side to help out–for instance, removing excess fonts alone that are not used (symbols such as windings etc) saves 800kb alone. We also have our new ‘Adalo X-Ray’ deployed to our staging servers for testing. X-Ray is our CTO’s AI baby, and will auto-index your databases and provide a performance audit. It will indicate what exists in your app that will be slowing it down. What is exciting is this will be the basis for our prompt engineering, so when Adalo apps are created for you, they will be created to not only look good (AI is pretty good at this out of the box) but it will do so in a highly performant manner (this is much harder to achieve).
3 Likes
Hi James
Thanks for the update! If the “timeout” issue did not happen, I will still be in the dark about app size. So in a strange way, I am glad this happened. I am doing a screen audit and working towards the 40-50 MB limit. My internal tests on google play show 39MB.
Looking forward to the tools that will help makers get the heads-up on good building practices.
Thanks once again
Jay
2 Likes
Hi James, are there any updates for June?
See here! June 2025 update!
1 Like