You can use JSON to be API Objects. You can save API Objects as data fields on custom data types. You can save a JSON file and use an API call to point to it. You can hard code the JSON in the plugin element within the editor. You can use custom data types to convert into JSON and then do client side manipulation on them and then update in the DB as normal.
Basically, it gets away from only leveraging two of the data types built into native Bubble and instead makes use of all four, custom data types, options sets, api objects and plugin objects. It also allows for reducing WUs by massive amounts (95-99% reductions for fetching/creating/modifying data) and makes some things normally not possible in Bubble possible, like creating a Global Data Center that controls all CRUD operators, Structured Data and Meta Data.
It also makes it easier to work with various LLMs for creating data structures and the actual data. Allows you to work more easily with incoming API data and manipulate it. The biggest thing is the use of JSON.
Using JSON more in our apps gives a lot, and I mean a lot more flexibility in how you structure data, how you structure your app elements (especially reusables) and how you can interact with browser local/session storage and IndexDB, which when done right help improve the performance of the app and give me options on how we can improve loading times of data or just when we choose to load the data.
It also makes it easier to setup your own database backups, sending data sets to LLMs and more.
I started saving API Objects as data fields in 2021 when I was a Bootcamp instructor for Bubble, but never had any idea of how to make better use of them than that. Luckily, people drop nuggets of gold on the forum.