Building your App
You have a lot of freedom to choose how you approach building apps in Draftbit. You can describe what you want in chat, make direct visual edits, manage integrations and build configuration, or edit code yourself. Most teams use a mix of those workflows as the app matures.
AI Agent
Section titled “AI Agent”Working with Draftbit’s AI agent makes building apps easier by letting you describe changes in natural language. The agent can edit files, use connected integrations, inspect preview errors, and explain what changed. Learn more in the AI App Builder.
Visual Editor
Section titled “Visual Editor”Use the Visual Editor to work directly with screens, components, styles, and preview devices. You can select elements, inspect component structure, adjust styles, and give the agent targeted context from the canvas.
Project Assets
Section titled “Project Assets”Each project in Draftbit gets a shared asset area for media such as images, video, audio, fonts, and text files, which every app in the project can use. Learn more about managing Project Assets.
Packages and environment variables
Section titled “Packages and environment variables”Use Settings to manage environment variables, npm packages, and legacy variables for imported apps. This is also where package changes that affect native builds start.
Code Editor
Section titled “Code Editor”If you have experience coding or are inclined to learn, Draftbit provides code access directly in the Builder. Learn more about working with the Code Editor.
App Publishing
Section titled “App Publishing”Once you’ve built your app in Draftbit, you can share it as a public prototype, publish a PWA, build native previews, submit to the Apple App Store or Google Play Store, or export the code. Draftbit offers one-click publishing for managed builds and manual publishing for teams that want full control over deployment.