.... but why is the entire 'listener' concept not completely 'abstracted' from the low code builder user? As far as they are concerned, you have a URL change, then ENTER is pressed (or URL is processed from a link), then Page load on that page executes? Why not just make it even easier for the BILDR user?
Great question, we think a lot of Bildr is setup as end user control - and there are times these are necessary. The listener concept here is fundamentally different, we're not clicking enter or navigating to a new page all together. If you were to type in a new URL and hit enter, you're loading a new page. We're using the browser's URL as an update to allow for forward and back browser capabilites without having to navigate away from the single page experience, and reload the page. Eliminating the setup of the listener action would mean our page can't listen to the back/to buttons, meaning it won't update if the user hits back or forward. Would love to see a company that you like that does this well or if you have any other ideas on how to do that! I think the right way I'd look at this is abstracting it out of an action on page load and tying it to the URL Route settings as a single page app w/ clarity of how that should operate.
Is there a way to import a figma design into bildr?
.... but why is the entire 'listener' concept not completely 'abstracted' from the low code builder user? As far as they are concerned, you have a URL change, then ENTER is pressed (or URL is processed from a link), then Page load on that page executes? Why not just make it even easier for the BILDR user?
Great question, we think a lot of Bildr is setup as end user control - and there are times these are necessary.
The listener concept here is fundamentally different, we're not clicking enter or navigating to a new page all together. If you were to type in a new URL and hit enter, you're loading a new page.
We're using the browser's URL as an update to allow for forward and back browser capabilites without having to navigate away from the single page experience, and reload the page. Eliminating the setup of the listener action would mean our page can't listen to the back/to buttons, meaning it won't update if the user hits back or forward.
Would love to see a company that you like that does this well or if you have any other ideas on how to do that!
I think the right way I'd look at this is abstracting it out of an action on page load and tying it to the URL Route settings as a single page app w/ clarity of how that should operate.