You missed the core of what I was saying: not vibe code a whole thing end to end (I agree, not sustainable), embrace the idea of having devs build the storage, parsers, schema, and security and let everyone vibe code the rest.
Like, let’s use a simple photos example: a photo file has metadata standards already embedded, but doesn’t store it’s edit history, event, or who’s in it. Immich already does a lot that’s great here with parsers and ML and if they changed focus to the data storage layer they could essentially boil down to a table for edit history, a table for events, a table for people, etc, the ability to store in SQLite or sidecars, and an API layer for people to hand to their AI.
Not only would it reduce the dev load, but then we could have an ever-expanding sphere of personal data ownership as Futo adds schemas/tables for video, audio, documents, and maybe everything else most people need to build their own UIs for specific uses or even “god view” UIs.
I am really not following. If “anyone” can write a GUI, how does moving it away from the devs reduce load? Either it’s a lot of work for devs and then even more so for “anyone” or it’s easy for everyone.
For simplicity of explaining, I’m going to group web software parts in to “hard” and “easy” with AI assistance
hard:
- Overall security
- User permissions in multi-user deployments
- Input sanitization
- RDBMS schema design
- Parsing
- Bit-rot protection (here because it’s rarely on the radar of the general user)
easy:
- DB queries against a known schema
- Working in a front end HTML/CSS/JS stack
- Making UI components
- Moving those components around
To your question about why moving front end away from devs would reduce load: a person making a UI they want is a different category of work than creating a UI that everyone wants. Even if it’s easy, it’s distracting to be thinking about everyone’s use-cases and refining the details.
Like, let’s use a simple photos example: a photo file has metadata standards already embedded, but doesn’t store it’s edit history, event, or who’s in it. Immich already does a lot that’s great here with parsers and ML and if they changed focus to the data storage layer they could essentially boil down to a table for edit history, a table for events, a table for people, etc, the ability to store in SQLite or sidecars, and an API layer for people to hand to their AI.
Not only would it reduce the dev load, but then we could have an ever-expanding sphere of personal data ownership as Futo adds schemas/tables for video, audio, documents, and maybe everything else most people need to build their own UIs for specific uses or even “god view” UIs.