Hello everyone! I know there are existing topics about this, but I’m just curious if there’s an update or any latest fix to work around this. There’s a certain flow in my app where I don’t want users to go back, such as after payment, after placing an order, or after logging out.
One option is to add a true/false property to the user that changes with certain actions and you can condition the visibility of the components you don’t want them to see with that property, or add an action to the screens you don’t want them to go back to conditioned by that property. If “User has already paid” = True, when the users tries to go back to a certain screen it immediately sends them back to the correct screen.
To prevent users from going back in Adalo, use screen redirects after key actions (payment, order, logout), hide navigation bars, or implement session based logic to restrict access. For web apps, JavaScript can disable the back button. Let me know if you need details!
So the best move here will depend on the specific use case. There are a few workarounds though.
One move I’ve used is to link to a screen that then redirects you to another screen instantly. For example, let’s say a user makes a payment and I don’t want it to get registered twice, so I want to prevent them from going back into the payment module.
Screen 1: Payment. Button to complete payment, links to redirect screen.
Screen 2: Redirect: Contains an action whenever the user visits the page which redirects them to a verification screen.
Users won’t even notice screen 2. If they try to go back on screen 3, they’ll just get sent right back to screen 3.
Another move is just to add another action to move them along. For example, my log out buttons have a 2nd action which immediately sends you back to a log in page, there’s no going back.
I used it my self and it works well, but I noticed that once the user access a screen where the component exists, the back event will be disabled on all screens after.\