The pro-code no-code app builder for Web, iOS, and Android
Chicago
Joined April 2018
- Tweets1.3K
- Following12
- Followers5.9K
- Likes6.3K
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?
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?
ALT Daily code backups: Draftbit's Backups panel lists scheduled and manual backups with date, version, size and a Download button
ALT Back up now, any time: the Back up now menu offers Saved version or Unsaved changes
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?
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?
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?
ALT See every state of a screen: the Component Tree forcing a condition so the preview shows an empty 'No tasks yet' state.
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.
ALT Edit content without code: text fields in Draftbit showing variables like task.description and task.status as chips.
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.
ALT Build right on the canvas: a component being dragged onto a Draftbit app preview.
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.
ALT Ship any version you've saved. The Draftbit Publishing page's Versions tab lists saved versions with published badges (iOS 1.4.0, Android 1.4.0, Web), and a Publish this version menu offering Web, iOS and Android.