@ts1 Interesting timing on your post. I just added a new plugin (JSON Machine Pro) for working with lots of page states.
2 Likes
Love it! Been waiting for this since you teased it on the forum. Will check it out soon. Thanks for the update.
This is a great thread and so many "golden nugget"s. Wish I had come across this a bit earlier 
Thank you @romanmg and all others for the very informative dsicussion. One thing to add - if building a web app for a country/region where internet connection is choppy and/or mobile data is expensive, a SPA structure/design would be a better option IMHO. It will minimize the risk of page-to-page load time delay as well as save precious mobile data. This is true for many of the East/Southeast Asian countries, especially if you building an app for masses who live in rural areas. At least that has been my experience so far. Would really love to hearing anyone who may have a different POV/experience!
Hi there. I purchased the JSON Machine Pro plugin this week. That said, I’m having some real trouble understanding how the plugin functions based on the existing demo and documentation. I’m trying to pass a JSON text into a reusable element, parse that JSON using your plugin and then reference the values in various fields. Sounds straightforward, but for the life of me, I can’t figure out how to do it. Any chance you’d be willing to help? Feeling like I must be a little dense.
Hi @ts11 I’ve read your different posts and would be really interested in this methodology document you’re talking about 
Hey.
Very interesting thread.
I am currently building a bubble app from scratch for a side project.
And I chose the SPA path.
I am wondering if after 2 years, if there are some new methodologies ? Best practises ?
On my side each « page » of my spa is a RE. But several RE use same requests. So it’s not optimized. I read somewhere that is complicate to work with RE like I did, because it’s difficult to pass data through several RE. Specially if there are sub level.
Thx
1 Like