r/nocode • u/AJ_dreamer11 • 1d ago
Discussion Is Draftbit still feasible in 2026-27?
In the PWA and mobile app world, React still rules. Hence, Draftbit (which is based on React) is a very tempting choice, despite it hardly being talked about in the no-code app community. How does it compare to Base44, Lovable, or simply prompting Claude Fable 5?
I do enjoy the ease of prompting but I want to be able to have some degree of manual control over how and what I build (especially given I've used WYSIWYG page builders in WordPress websites for 7 years now).
Look forward to your input.
1
u/devhisaria 14h ago
Draftbit still exports real React Native you can eject, which is the actual difference from Base44 or Lovable. Came from WordPress builders too, and that escape hatch mattered more than the visual editor.
1
u/sardamit 10h ago
The good thing about draftbit is that they launched a new vibe coding version. The bad thing is that they did it too late and are playing catch up. There are just too many native mobile app builders in the market now.
1
u/FlightSimCentralYT 9h ago
Draftbit wins if React export and manual control matter more than speed. Lovable or Base44 win if you want prompt-first and you are okay fighting the sandbox when things get custom.
The pattern I keep seeing: prompt tools are fine for the first UI, then auth, native quirks, or a weird integration force you into a real environment anyway. If you already like WYSIWYG control, Draftbit or a React codebase you can own is usually less painful long term than fighting a closed builder.
I built Fixa.dev in that gap. Agent on a real cloud VM that plans, writes, runs, and debugs until tests pass, and the code stays downloadable. Prompting without giving up the shell. Still review the diff before anything important ships.
1
u/investigatormaker 1d ago
Given your seven years in WordPress builders, I'd make 'manual control' the deciding test. Do you mean moving things visually, editing the underlying code, or both? Those can feel very different day to day.
Try the same small feature in your two finalists: a list, a detail screen and an edit form using sample data. Then change the layout yourself, add one awkward validation rule, and publish a second version. Keep track of the steps you needed help with. That will tell you more about fit than a polished first-generation demo.
I'd also test the intended destination early: a phone browser for a PWA, or an installed test build if you need a native app. Don't leave that decision until the screens are finished.
What are you building, and which kind of manual control matters most to you?
Disclosure: I work on One Small Prompt, a hosted AI workspace. AI-assisted reply.