My app is a one page mobile app, and I use custom states to show and hide groups to simulate page navigation. So there is no navigation in reality. That’s why the native “go to previous” action of bubble doesn’t work for this kind of apps.
How did this work out for you? Also, why are you under the impression that custom states are the play as opposed to URL parameters? I’ve read arguments in both directions, and I have chosen URL parameters given the benefits with navigation. I only use custom states for my Login screen, and with a few popups for posting and whatnot.
I also heard that URL parameters are more suitable for navigation on one page apps and I’ve used them to build my app. But when i wanted to turn the app to a native app, bubble listed me several errors related to the use of URL parameters (which is normal because a native app has no URL). So the only possibility left is to use the custom states.
To build navigation history, I added a Data Type in my database with the list of custom states. Every time I navigate, I add a line with the current custom states to my data type, and every time I use return button, I set the states of the last line to navigate and then delete that line.