Hi, I’m a little confused, Weweb says their apps are all SPA’s, but I have a PWA and everytime I go to a new page it reloads everything on that page, and to be honest its kind of slow. I’m loading one collection from Xano, no filtering or sorting on the front or back, and only displaying 7 records, and I have to wait to watch it load every time.
Now, i’m not waiting seconds for it to happen, but its not anywhere near as snappy as I think it should be based on what I’ve built in the past in Bubble.
Basically it doesn’t seem to matter what I’m loading, even a simple API call to Xano seems to be taking long enough to load that I can watch the page being built to load and it has a pretty bad user experience.
For Reference:
Xano - Launch paid plan
WeWeb - Starter Paid Plan
Performance is the same on multiple phones in multiple countries
Thats exactly how I was going to build it but I was told by Weweb that it wouldnt matter because it packages everything as an SPA. I like WeWeb the best of all the nocode tools, and I’ve used many. WeWeb seems to be quick as a web app, but as an PWA it seems to be much slower, and its not device specific as multiple people are showing the same lag.
On weweb, all sections that are not instances of a “multipage section” are loaded each time the page is changed.
To take advantage of SPA, you need to use multipage sections as much as possible. Typically, the menu bar should be one. It will then only be loaded the first time the app is loaded.
Hey @mark can you share a screen recording maybe of your experience? And/or can you share a URL for looking at it? I’m really curious what network traffic is going on in PWA mode that is slowing you down.
PWAs have a lot of promise but they fight against the browser’s natural inclination to run home to get you data. The devil is often in the details! So if you can share either vid, link or (best) both, maybe I or others could give you more insight?