3 ms·
Neat. One issue with the demo is that the initial impression makes the tool seem very sluggish, when in reality the sluggishness apparently comes from fetching
by zokier 9y ago
Neat. One issue with the demo is that the initial impression makes the tool seem very sluggish, when in reality the sluggishness apparently comes from fetching data dynamically over the network. While demoing that capability is nice, I would default to using local data.
One thing that I noticed while paying attention to the sluggishness was that customer information view showed the previous data until new data arrived when selecting another customer. I would consider that fairly bad thing, especially as there are no indicators that the data is not actually valid.
I think a natural extension to this system would be to add a form builder or something that adds the ability to modify/submit data. Combined with something like AWS Lambda (and other AWS services) you could build quite powerful "applications" with relative ease.
- dvdhsu 9y agoThanks for the feedback! - local data -- good point -- will switch that up so the demo goes faster in future - no loading indicators -- thanks! I think I've used the tool so much I've now gotten used to it, but this is definitely something we'll add in our next release - form building -- interesting. We were thinking about doing API queries to modify data, but that would require backend code. Were also thinking about just having a database local to retool -- so you can take notes on your customers, say.