Hey eveyone,
Backendless is using a ui page path logic like example.com?page=page1. Most websites I see are using a logic like example.com/page1.
This could be achieved by creating a single container for each subpage and publish them all to a tool like firebase hosting in the according subdirectories. However as this is not the intended behaviour, I’m wondering if there are any negative side effects or if there’s a better solution to achieve this goal.
I’m aware that splitting an app in mutliple containers renders App Data useless. Although variables can be passed using the native sessionStorage.
Best,
Anton