The core vision here is something I can absolutely get on board with, but the execution fundamentally seems to misunderstand why "home-cooked software" doesn't exist.
The target audience problem is immediately apparent: they're building a product for people who can write JavaScript event handlers but somehow can't 'npx create-react-app'. This demographic is approximately twenty-seven people.
More critically, they've confused the problem space, in my opinion. The barrier to personal software isn't the lack of drag-and-drop of JavaScript environments. It's that software, unlike a meal or a home-made sweater, comes with an implicit support contract that lasts forever. When I cook dinner for friends, I'm not on the hook when they're hungry again next Tuesday. When my grandma knits a home-made sweater, she's not expected to keep supporting it in case I want to add a hood.
When the attendance counter has a race condition and the venue goes over capacity, guess who's getting the angry call when the fire marshal shows up for an inspection?
The "redistributing the means of software production" rhetoric rings particularly hollow from what appears to be a proprietary SaaS in the making. You don't democratize software by creating another walled garden. And their claim about "owning your data" while simultaneously offering real-time sync is either technically naive or deliberately misleading. How is the attendee counter example's counter state shared between users, if the data lives in local storage? I don't see how you can have both without server infrastructure that they control.
The actual nearest thing to their vision already exists and has millions of users: Spreadsheets. Non-technical people build complex, business-critical "applications" in spreadsheets every day. No JS required, local-first, and everyone already knows how to use it. But "we made a worse Excel" doesn't sound as revolutionary, I suppose.
The real unsolved problem isn't making it easier to create small apps - I build small tools for myself all the time. It's making them sustainable without creating permanent maintenance burdens. And that is not something you can solve with a new framework or SaaS - it's at it's core, a social issue.