The problem is that the "doesn't" and "can't" become a "gentleman's agreement" between devs and users.
I got a team of not tech-savvy people using an app that at any point they could accidentaly click edit, not knowing they would be:
A) triggering extra charges, and
B) potentially changing mission critical code, destroying part of, or even the whole app.
A 'user' that has access to the editing controls and unfettered access to the DB definitely looks more like a 'dev' than a 'user'.
I've spent a lot of brain juice in trying to scope an app properly and make it as fool proof as possible, but for that we're now stuck at a high cost Business plan for an app that doesn't really do much for the business.
I found out about Retool in Jan 2025 and went head in developing things. Pretty life changing being able to jump from VBA macros to deploy a full inventory control web app in 2 months of learning the Retool ecosystem, picking up JS on the way and building a full CRUD app.
We're in Australia so the billing hurts according to the exchange rate which now makes everything 60% more expensive (1 USD = 1.6 AUD). For such a small internal tool with just 4 users (1 admin, 3 'end'), being forced to the Business plan just to have some user scoping controls becomes...... questionable.