Draftbit

You have an app idea and want to know what it actually takes to go from a prompt to something people can download. This is how that goes in Draftbit, following one yoga studio's booking app from the first prompt to the App Store and Google Play. We sped it up, so a real build takes longer, but the steps are the real ones.

How an agency ships client apps with Draftbit: Jimmy's team at Nova Digital used to buy a code script for each client project, then adapt it, and it was sometimes broken or outdated. Now: → New apps from a prompt, or from a template in the library, then customized → React Native apps with a Supabase backend → Draftbit's agent and Supabase, both driven by prompts "What else could we ask for? Nothing." — Jimmy, Nova Digital CEO (translated from French) Building apps for clients? What's your stack?

Release notes: draftbit.com/whats-new/conne…

Draftbit now keeps daily backups of your app's code. What you get: → A scheduled backup every day your saved version changes → "Back up now" any time: pick your saved version, or your unsaved changes → Each backup lists its date, type (Scheduled / Manual, Saved / Unsaved), version and size → Download any of them as a zip; restore by importing it as a new app Your code stays yours. What's your backup routine?

Release notes: draftbit.com/whats-new/conne…

Using the Stripe MCP in Draftbit? Two days left. From October 31, Stripe's MCP only accepts OAuth or Stripe Agent keys, so a connection that uses a regular API key will stop working. The fix takes a minute: open your Stripe connection in Draftbit and choose "Sign in with OAuth", or paste an Agent key. RevenueCat connections can use OAuth now too. Have you switched yet?

Full walkthrough (Part 2 of the e-commerce tutorial, from 3:36): youtube.com/watch?v=42KgkHHz…

Email verification + onboarding for a Supabase-backed app, in one prompt in Draftbit: → Prompt: when a new user signs up, verify their email, then run onboarding → The agent gates routing: a signed-in user with an unconfirmed email waits on a confirm screen → Signing in with an unconfirmed account routes to that screen with a resend button, not a dead-end error → "Confirm email" is on in the Supabase auth settings, inside Draftbit's Project Integrations One tip from the agent: Supabase's built-in mailer only sends a few emails per hour. Add your own SMTP provider before real signups. How do you handle onboarding in your apps?

Release notes: draftbit.com/whats-new/conne…

Draftbit backs up your app's code every day, whenever you've made changes since the last backup. → Need a copy right now? "Back up now" saves your saved version or your unsaved changes → Download any backup as a zip → To restore, import it as a new app Do you keep your own copies of your code?

Agreed. Your code should never be out of bounds. 🎾 The code stays yours.

Great tip, thank you! 🙏

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.

100%. Serious projects deserve full ownership. Your code, your repo, your rules. 💪

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?