For example, a Ruby on Rails app would use a router to recognise URLs and dispatch them to a controller’s action - in my case the correct resulting page. How does a backendless app with a UI builder FE achieve that?
I don’t mind the ugly url on preview ( I think). Just when I finally get to production I want the clean easy read and easy to share url like http://www.mybackendlessapp.com/blog/blogPost.
Like I said, it’s the sharing of the clean url and then being able to process the clean url when received by the app. If the app can’t maintain the clean version once loaded, that’s okay but not preferred.
Maybe a better question to ask is : What is the life cycle of a request to a backendless app ?
How does the app receive a request?
Can I read that request and interpret the URL (that the user put in the browser or clicked a link from) to then process and redirect to open the appropriate page ?
Can this be done before the app decides it’s a 404 ?