Which Draftbit build can you try on your phone?
The built-in native preview uses a simulator. Draftbit’s Pro and higher Testing Builds include an Android file you can install on a device and an iOS file for the simulator. For an installed iPhone test through Draftbit’s store upload path, use the build in App Store Connect with TestFlight.
A preview can show how a screen looks. An installed copy lets you check how it behaves after leaving and reopening the app.
What is included when you pay for publishing?
The current plan matrix starts code export, GitHub export and iOS and Android publishing at Standard. Pro and higher add native simulators and downloadable testing builds. Check your account’s plan, especially if you started on earlier pricing.
Developer accounts and connected services have their own requirements. A successful upload is one step before testing or public release.
Which parts can you move out of Draftbit?
You can export editable app code. Draftbit’s ordinary GitHub export sends files one way and replaces the contents of the selected branch, or only the selected folder if you configure one. Draftbit also offers a separate workflow for copying in a supported project or working in a connected repository.
Keep a separate branch or copy for changes you make outside Draftbit. Review where records, files and sign-in live before moving. A connected or Draftbit-provisioned backend is a separate dependency.
What would you check on the first test build?
Sketch a fictional checklist and one item called “Pack cups.” Use no account, code or connection.
- Choose one expected resultMark the item done, then draw the app after reopening. The item should still be marked.
- Choose the right test pathLabel an Android file as device or emulator and an iOS simulator file as simulator only. Mark the separate path an iPhone tester would need.
- Leave a boundary before real testingOnly plan a real run after you can verify separate test records and that outgoing services are disabled or test-only.