Best practices when building

Hey all, I was curious to hear from people on some best practices they use or have discovered while creating in Adalo. Anything from design, database structure, pushing data around, etc.

One thing I enjoy doing is keeping a blank screen for designing my elements and page sections, and also keeping reusable elements there such as custom icons, buttons and font sizing and weight guides for different elements to keep consistency. Sort of like a mini library within the editor!

How about everyone else?

3 Likes

I usually focus on the DB structire first, because it makes it more clear what I put on the screens.
so 1) database 2) screens 3) relationships between DB

1 Like

We work through the user experience and the actions we want them to take and where those actions take place and then work backward from there. We used to start with the database, and there are some basic points that you can start with, but the workflows often highlight data elements you might have overlooked.

1 Like

I’ve also found you should really put off from linking all your screens up to eachother and turning UI into custom lists for as long as possible while building and planning out your UI/UX. I don’t have the worst computer (i7-7700 / 16GB RAM / GTX 1060 6GB) but when the editor is filled with a bunch of screens and elements, and then the screens are all linked together, it slows down the editor greatly.

To the point where I need to wait 1-2s seconds before an element is selected, which adds up when you’re trying to select an element to edit which is in a group, and that group is inside a list.

Edit: I’ve seen that you should have as little tabs open as possible which helps, which I usually do. Just the editor, a tab viewing the published URL, a tab for the forums and a tab for LoFi Girl.

Try different browsers, it could be brave, edge, firefox or others, I almost have all. :grinning:

And for those that want to build MVP, try to solve the critical factors first before seduced to any other features.

In your experience, which browser runs the editor the best? I’m just using Chrome.

edge beta and brave.

1 Like

I use Edge on my Surface Book and really like it. After a quick search confirming that Edge runs better than Chrome and your recommendation, I think I’m going to bite the bullet and switch to it on my desktop.

Thanks for bringing light to that. :grin:

1 Like

You should use Firefox when you have multiple screens 60+ say. The performance is about 5x to 10x better due to the ability of its hardware acceleration.

I was banging my head against the wall for a long time with edge, brave, opera chrome and more. I have a 16gb GPU and 64gb Ram, none of the named browsers can access this level of power, so to an extent PC performance becomes irrelevant.

I wrote a post quite a long time ago:

OH. MY. GOSH. Just loaded up my project in Firefox and I can confirm it’s by far the best browser to use.

I’ve only got about 25 screens including basic login and a couple of static screens, but they’re sized at 1920x1080, maybe that’s why I’ve been struggling on the other browsers?

I went from hardly being able to pan the work area around in the editor and waiting seconds for things to be selected/lag with typed and deleted characters etc. To now everything smooth and fast as if it was a new project with default screens.

Thank you to the moon and back mate!

1 Like

I try firefox too, it seems faster, but I don’t like that I have to zoom actual size every time I zoom in.

This counting screens just trigger me, so even I didn’t realize that edge beta can handle 161 screens, and this is after split.

One thing I don’t like edge beta is in fullscreen mode, the tooltip don’t show up, so I usually don’t use fullscreen, but if I need to use fullscreen, I use brave.

Just stating my experience. :grinning:

“Zoom actual size every time I zoom in”. What do you mean by that, I don’t understand?

It has been a while since I used firefox, now testing again, no need to zoom actual size anymore.

Before, after zooming in with trackpad, the left panel becomes zoomed too, so I have to click zoom actual size to make it into normal size.

Well, this is for better and be grateful. :grinning:

1 Like

Glad it helped. As Yonki has stated there are a couple of drawbacks:

  1. The scroll bar is present when scrolling up and down your previewer phone screen/iPad screen. I copy the preview link and use Chrome/edge etc for viewing my projects. But all Dev is done in Firefox

  2. Scrolling in by pinching the laptop track pad does cause the whole frame to sometimes zoom in, rather than zoom into the intended screen. This isn’t the case though when you use a mouse, so use a mouse instead of trackpad.

  3. You may notice typing long pieces of text into magic text areas, Firefox doesn’t work so well. I type long pieces of text out else where, and copy paste into the magic text areas.

Otherwise, Firefox is literally a no brainer. I tried every browser going, but you will find most browsers will work v poorly for large projects. When Firefox works instantly.

I’ve ran into your 1st and 3rd problems, but I work on desktop for now so 2nd isn’t an issue. The 3rd issue is very annoying. I think I’ll stick to chrome until performance drops off to unbearable then move to Firefox.

1 Like

Good idea, I have a few Apps with 100ish screens, and Chrome, Brave and Edge etc just are not even a feasible option. You will see that when your project grows to similar size :slight_smile:

Adopt an iterative approach when developing an app. Develop (and test!) small bits if functionality at a time. Don’t do it all as a ‘big bang’ and try to get all the features in at once. I extend this to getting early test builds out in Android and IOS.

I have a ‘testbed’ application where I can try out stuff without disrupting my main application.

Get a 3rd party (a friend, relative, colleague) to test your app as you develop it. They often provide good feedback on how intuitive and easy to use your app is, and will use your app in ways that you hadn’t anticipated or designed for.

Adopt a methodical approach to testing. Document your test cases somewhere so that you have a list of things you need to test and retest after changes. Unfortunately, Adalo doesn’t have a way to run tests automatically so this can be tedious and time consuming.

Take regular backups of your app and database.

1 Like