Out of Webflow, Bubble, Webstudio, Toddle & Divhunt, which one do you currently hold in the highest regard? Do you see specific ones as overwhelmingly better for specific use cases vs others?
They all have their benefits for very different reasons. As do you and your clients. For price/low risk Webstudio stands out to me personally because if its flexibility and scalability but you need to put in that extra bit of work.
We believe that SPAs are the future, platforms like Facebook, RUclips, and Instagram are prime examples of this. While the main concern with SPAs is SEO, this can be effectively addressed with server-side rendering or, in our case, pre-rendering. So, when using Divhunt, you won’t face any SEO drawbacks. When a web crawler requests your site, we detect it and pre-render your website on the fly within a fraction of a second. This means the crawler receives the full HTML, including all content, images, text, and even lazy-loaded sections. Of course, there are downsides, just as there are with MPAs. For instance, some third-party libraries don’t handle SPAs very well, which can lead to broken functionality or require additional steps to make them work properly. Hopefully this will be sorted out in near future.
@divhunt good luck on that bet. All that work for marginal speed benefit when a “classic” website will work just fine. Lazy loading sections meant for a janky experience to users.
Do you think Divhunt has got what it takes?
I wonder how WebStudio and DivHunt compare between the 2 (if pricing was not a factor) for scalability
Webstudio is a different beast. I’ve got plenty of videos on Webstudio.
Out of Webflow, Bubble, Webstudio, Toddle & Divhunt, which one do you currently hold in the highest regard? Do you see specific ones as overwhelmingly better for specific use cases vs others?
They all have their benefits for very different reasons. As do you and your clients. For price/low risk Webstudio stands out to me personally because if its flexibility and scalability but you need to put in that extra bit of work.
@@webflowandcode Thanks for that, I appreciate the quick response too!
Such a shame of the SPA approach, because I really like a lot of their features.
Same!
Theres an option to deactivate spa
No. This just means the pages refresh. It’s still a JavaScript-powered website. You see me play with it in the stream.
We believe that SPAs are the future, platforms like Facebook, RUclips, and Instagram are prime examples of this. While the main concern with SPAs is SEO, this can be effectively addressed with server-side rendering or, in our case, pre-rendering. So, when using Divhunt, you won’t face any SEO drawbacks.
When a web crawler requests your site, we detect it and pre-render your website on the fly within a fraction of a second. This means the crawler receives the full HTML, including all content, images, text, and even lazy-loaded sections.
Of course, there are downsides, just as there are with MPAs. For instance, some third-party libraries don’t handle SPAs very well, which can lead to broken functionality or require additional steps to make them work properly. Hopefully this will be sorted out in near future.
@divhunt good luck on that bet. All that work for marginal speed benefit when a “classic” website will work just fine. Lazy loading sections meant for a janky experience to users.