A padel booking app with Supabase auth, court availability, bookings, and separate player and club-owner areas, built by someone who says they're "not an experienced developer."
"The AI agent has been particularly useful for turning ideas into working features… I can see and work with the underlying code rather than being completely locked into a no-code platform."
— RallyMW founder (verified review)
3/ Preview every state. Force either side of a condition from the Component Tree to check empty lists, signed-out views and errors. Preview only, never your code.
Which state do you forget to check most?
2/ Text with variables. Words stay text, variables render as chips (task.description, task.status). Click a chip to swap the value, or type { to insert one.
Three visual-editing details from Draftbit's latest update 🧵
1/ Drag onto the canvas. Pull a component straight onto the preview. The screen makes room as you move, so you see where it lands before you let go.
You can now connect an existing app from GitHub to Draftbit, and Draftbit works directly in your repo, not a copy.
→ Connect repo → Draftbit GitHub App (no token to renew) or a fine-grained access token
→ Pick branch + app folder; the picker lists every folder with a package.json, so monorepos work (e.g. apps/mobile)
→ Your files stay as they are: nothing to migrate, chat + code editing + preview right away
→ Saving commits to your branch. Teammate pushed? Sync pulls their commits first
Works on every plan.
New in Draftbit: publish any saved version of your app.
The Publishing page now has a Versions tab that lists every saved version.
→ Pick one, hit "Publish this version", and ship it to iOS, Android or Web
→ Versions you've already published show badges for platform, version number and result
→ App stores still need a higher version number, and Draftbit fills it in for you
→ Builds use your current environment variables, so a very old version may need updates before it builds
API, CMS and Supabase backends always publish their latest version.
Shipped something you want back? Re-ship the version that worked.
If your team's app takes payments through the Stripe MCP in Draftbit, there's one change to make before October 31.
From that date, Stripe's MCP will only accept OAuth or Stripe Agent keys. Connections that still use a standard API key will stop working.
The fix is small: open the Stripe connection in Draftbit and choose Sign in with OAuth, or paste an Agent key. RevenueCat connections can use OAuth now as well.
If you manage several client apps, it's worth checking each project's connection this week rather than finding out from a failed checkout.
How do you keep track of third-party credential changes across projects?
From one prompt to a 5-screen e-commerce app in Draftbit:
→ Pick the agent + model (Codex, Claude Code, …)
→ Prompt: Home, Product Detail, Cart, Checkout, Profile
→ Start from the Ecommerce template
→ Onboarding wires up a Supabase backend
→ Missing images/icons? One follow-up prompt fixes them
→ Save, then check the commit history
Full 9-min walkthrough 👇
Solo founder. No engineering team. A production-ready food delivery app.
Rajesh built ZingoEats with Draftbit. What made the difference for him:
→ API integrations handled inside the platform
→ Granular control over the design
→ Custom code + API documentation: "once I mastered those, my development speed doubled"
New Draftbit drop, as sung by our Release Cat. 🎤🐱
🔗 Connect repo: Draftbit works directly in your own GitHub repo — saving commits to the branch you choose
💾 Backups: your app's code, backed up daily when it changes (or hit "Back up now")
⏪ Publish any saved version again to Web, iOS or Android
👀 Skills: coming soon
🤖 Made with AI
A Hono API backend in Draftbit, start to finish:
→ New app → API Backend (Hono)
→ Database: managed Supabase, Cloudflare D1, or external Postgres
→ The builder reads your OpenAPI doc and turns the canvas into an API console
→ Pre-filled path, query, headers and body → Send → JSON response
→ Copy as cURL, plus request logs and generated API docs
Release notes: draftbit.com/whats-new/proje…
New in Draftbit: automatic app backups.
→ Draftbit checks your app once a day and backs it up only if the code changed, so no duplicate copies
→ Need a copy right now? "Back up now" works even mid-edit
→ Every backup is a downloadable zip of your source code, one per branch
→ Restore by importing the zip as a new app (your original stays untouched)
Your latest backup is always kept while your plan includes backups.
New in Draftbit: Connect repo.
Your GitHub repository stays the source of truth. Draftbit works right inside it:
→ Saving in the builder commits straight to the branch you choose
→ No migration, and Draftbit doesn't rewrite your project to fit its conventions
→ Monorepo? Point it at a folder like apps/mobile
→ Someone pushed to main outside Draftbit? Hit Sync and keep going
→ Connect with the Draftbit GitHub App, or a fine-grained token if you prefer
You still get chat, code edits and a live preview.
Import copies your code into Draftbit. Connect repo keeps it where it already lives.
Draftbit builds backends now, too. 🔌
Pick an API Backend (Hono), choose your database — managed Supabase, Cloudflare D1, or your own Postgres — and let the agent build it.
There's no UI to preview, so the builder swaps the canvas for an API console:
→ reads your OpenAPI doc and lists every endpoint
→ pre-fills path, query, header and body
→ sends the request with your dev key
→ Copy as cURL
→ request logs + generated API docs, right alongside
Claude Opus 5.5 and GPT-6 Sol are now live in Draftbit — the new defaults for Claude Code and Codex. 🚀
⚡ Opus 5.5: 40% cheaper to run and 30%+ faster than Opus 5 (savings vary by task)
🎯 GPT-6 Sol: about half the factual mistakes of GPT-5.6 Sol
💸 GPT-6 Luna: beats GPT-5.6 Sol for a tenth of the cost
Which one are you trying first?











