When is Expo Go enough to try an idea?
Use Expo Go to explore a screen or a capability already included in it. For a camera or other phone feature that requires a native library or configuration outside Expo Go, make a development build for your app.
A development build is your own test app with the native parts your project needs. Test the actual permission behavior there before you decide the feature is ready.
What does Expo build for you and what can you keep?
Expo Application Services, or EAS, can build installable files in the cloud. The Free plan lists 15 Android and 15 iOS builds in its monthly allowance. Check the current allowance and queue before counting on a build for release day.
Keep the project source and build settings in your own repository. Expo documents local EAS builds as another option. You supply the platform build tools and check the limitations of local mode. An installable file is useful for testing or distribution, while the project is what you edit to make another version.
Does uploading a build publish it to the store?
A build produces an app file. EAS Submit can upload the file to the store system. Set up the matching developer account, signing and store information, then check the store’s review and release steps.
On iOS, the uploaded build becomes available in TestFlight after processing. Public App Store release still needs the App Store Connect submission steps.
How could you rehearse camera access before creating a build?
Draw two paths through a fictional plant journal. Use no account, camera, upload or build service.
- Show access grantedThe camera opens after the user chooses Add a photo. Draw a picture of a paper leaf as the sample.
- Show access declinedThe app keeps the draft and offers a way to finish the note without a photo.