I will say that what I initially expected to be the biggest issue -- Connecting a database to Retool -- Turned out to be the easiest part of this entire experience. I even found and reported a little bug!
One issue I ran into a lot was UX Inconsistency between documentation and the end-user experience. To a lesser extent, instructions were often only written for a certain flavor of SQL -- and it would be foolish to expect documentation based upon the myriad of ways we can connect our data -- but when it came to 1:1 following a guide, it wasn't unusual to run into slight difference in menus that made it frustrating.
Customer Support is very busy but also very kind and willing to walk me through some changes; Changes we're still working on.
Saving a DB change is turning out to be a herculean task; Unfortunately, not enough people use Retool to get help, (Although there is a community forum!), because we're all confused. Again, to its credit, I can add users through Retool very easily, and was delighted, hopeful that this would be a quick way to build an app.
I wonder why it wasn't possible to make it a GUI option; a checkbox that says "Save changes to connected database?". There is both a SQL and a GUI Option, the latter of which is touted as the option that's less prone to error, but I ran into a handful of errors trying to do the option, so it's not simple at the end of the day.
If you have more experience building front-facing tools, using APIs, you may find it easier than someone like me, who comes from using back-end cloud services, but still knows enough to teach themselves most things.
