As we all know, data sources have mouth-watering potential. Reading data sources seems stable with acceptable performance (if approached correctly). At the time of this writing, the CUD of CRUD (Create, Update, Delete) of data sources, as well as binding to viewers, leaves something to be desired…
While we wait for the bleeeding-edge of Thunkability to stabilize, I would like to pose the following question:
What can be done with data sources and Data Viewers that cannot be done with JSON and Cloned Components?
Admittedly, using JSON and cloned components requires a LOT more blocks. But I am asking with a purpose. If experienced Thunkers can list specific capabilities of Data Sources and Data Viewers which are NOT possible with JSON and clones, I would like to build functions that can address those issues while the great team a Thunkable perfects their components. I think this will also help the Thukable staff better understand Thunker needs and goals.
Again, I’m not looking for a gripe list, but rather a list of features we need to make Thunkable development faster, easier, and more enjoyable for everyone!