The Adalo Editor is a big piece of software and relies heavily on computer specs and internet connection to run effectively. A slower computer will struggle to open and edit larger apps so optimizing the app setup is key to a performant builder.
To keep your app speedy, make sure to be careful with the number of components on any given screen. Too many components can make screen loading slow for your users and bog down a screen when making changes in the builder. Try dividing up the screen into a flow of screens for your users. More screens is better for user performance and experience than one screen with lots of components.
Avoid nesting components too deeply in parent and child components - nested parents that are over 4 components deep will most likely experience lower loading speeds and unexpected results. Furthermore, deeply nested components make it much more difficult to manage the layout settings of those components. Consider breaking up the screen into multiple screens or reworking your database to display the data you need to display.
Running lottie animations in the builder can drastically slow down your build experience. Consider turning off the Lottie previews.
Since text and images are generated responsively in the builder, having large bodies of text, background images, or other uploaded images can slow down the builder. Consider storing lots of text and images in the database and pulling via MagicText if possible rather than showing them as static.
Large static Images in the App Design can slow down the builder. Consider lowering the quality of apps if using many images in the design.
Very large apps can sometimes experience slowness if screen connections are turned on. Consider turning this off if your builder experience is slow.
For more detailed guidance, we encourage you to explore these resources:
By combining these best practices with ongoing improvements from Adalo, you can ensure your app performs efficiently and provides a seamless experience for your users. Be sure to start thinking about your app performance in terms of a score and asking yourself whether each new feature will move that needle up or down.
Last updated
Was this helpful?
Was this helpful?
