A simple graphical DB client is often a perfectly fine UI. Everything depends on the details, of course.
If this saves a month of defining and building a bunch of admin preference screens, letting you focus your one developer on things that matter, that can mean everything for a small startup.
what??? a month??? for an internal preferences/flags UI? See, this is what I mean. You've already failed. You cannot execute.
Also now you're gonna make customer support folks edit the DB?
- With Django, this is generated for you. It's literally free.
- With DotNet Core, also can be generated.
- Pretty sure Spring MVC has something similar.
- With Rails - can also be generated, or built very quickly with Hotwire.
- With React, this takes a couple minutes. Just have a generic "flags" list you can toggle etc. There are like a million form generation libraries.
At the end of the day if it takes you a week to get a UI with a list of buttons and checkboxes out, you need to rethink the technologies and process you're using if you're trying to move fast. You should probably do away with the process, too, for this early of an organization.
Yeah probably. If it's just one guy then... maybe. Personally I found putting 5mins into a little UI with text inputs useful when a customer in another timezone reaches out at 11pm and I just have my phone - can get that five star review by just making the adjustment right then.
For Spring I find https://bootify.io does a great job of generating DB, models, CRUD frontend+backend. Not open source but the basic variant is free (and I mean really free to use, no registration, just use it) and the code generated is reasonable for further development.
If this saves a month of defining and building a bunch of admin preference screens, letting you focus your one developer on things that matter, that can mean everything for a small startup.