Known Limitations

These are the constraints we hear about most often. Many of them are temporary and being actively worked on — check the Updates page for the latest.

Platform support

• Apps build for iOS, Android, and the web from a single React Native + Expo codebase. Desktop‑native targets (macOS, Windows, Linux) are not supported.
• The Builder UI itself is supported in modern Chromium browsers and Firefox. Safari and embedded webviews may work but are not officially supported.

Importing existing projects

• You can import apps from Draftbit Classic (v1) and start new apps based on React Native / Expo.
• Importing an arbitrary GitHub repo is not supported — projects need to start in Draftbit. See the Common Questions page for the latest on this.

Code editor

• The Code Editor supports JavaScript, TypeScript, JSX, JSON, and Markdown. Other languages (PHP, Python, C#, native iOS/Android source, etc.) aren’t recognized for autocomplete or linting.
• Manual code edits are gated to paid plans. The Free plan can browse and view code but not save edits.

AI agents and models

• The default agents are Claude Code (Anthropic) and Codex (OpenAI). Google Gemini is on the roadmap.
• Available models depend on your plan. Premium models like Opus 4.7 require a Pro plan or higher; the Free plan defaults to a smaller model.
• If you connect your own provider keys, model availability follows what your account allows on that provider — Draftbit doesn’t impose a separate model gate.
• When you use your own API key or subscription, your provider’s usage limits, rate limits, model availability, and authentication rules still apply.

Credits and billing

• Daily and subscription credits do not roll over once they expire. Subscription credits have a 30‑day grace period after the end of the billing cycle in which they were issued. See Credits for full rules.
• Bonus and grant credits don’t expire but are spent last.

Publishing

• One-click iOS and Android publishing requires complete credentials in the Publishing configuration. Without them you can still export your code and publish manually.
• Custom domains for web publishing are supported, but the registrar must allow CNAME or A records pointing to Draftbit. Some registrars restrict this on entry-level plans.
• Native iOS and Android previews need a new native preview build when you add, remove, or change packages that include native code.
• Apple and Google still control app review, policy decisions, account requirements, tester setup, and public release timing.

Build Config

• Sensitive values in Build Config are intended for build-time configuration and server-side tooling. They are not exposed to compiled app runtime code.
• Use plain text EXPO_PUBLIC_ variables only for values that are safe to include in the app bundle.

Integrations

• The MCP and REST API connectors only run while a chat thread is active. They are not a substitute for backend services your published app can talk to directly — for that, configure your app to call the same endpoints over the network.
• A handful of MCP integrations are still labeled Coming Soon on the Integrations page (Firebase, Figma at the time of writing). These will move to GA when their connectors stabilize.
• MCP, REST, GraphQL, Supabase, Canva, and publishing integrations can fail when the upstream service is down, credentials expire, required permissions are missing, or the external API changes.

Imported Draftbit Classic apps

Imported apps can include legacy variables, REST services, theme structures, or signing assumptions from the original project. Draftbit exposes tools for managing these pieces, but complex apps may need manual cleanup before previewing or publishing reliably.

Collaboration

• Real-time collaboration shows live presence avatars in the top bar, but multi-user editing of the same screen at the same time can produce conflicts. We try to surface them clearly when they happen — when in doubt, save your changes first and reload.

Reporting a limitation we should fix

If you hit something that feels like a missing feature rather than a bug, the fastest path is the in‑app support chat (Get Help in the top bar) or the Roadmap, where you can upvote items so we know what to prioritize.