Replying to @madmanstudioio
Agreed. Your code should never be out of bounds. 🎾 The code stays yours.
Replying to @halalstocktok
Exactly! Especially when iOS, Android and Web drift apart. 🙌 And when you republish an older version, Draftbit bumps the version number the stores require, so rolling back doesn’t get blocked.
Replying to @IronRedSandHive
100%. Serious projects deserve full ownership. Your code, your repo, your rules. 💪
Replying to @LIFESTYLWEALTH
Love hearing this, thank you! 💜 Keep shipping, and tell us if there’s anything we can make better.
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)
Release notes: draftbit.com/whats-new/conne…
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.
Details in the release notes: draftbit.com/whats-new/conne…
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?





