What do you need for an Android or iPhone test build?
Install Flutter and set up tooling for your first target platform. Flutter uses Dart for the app code. For local iPhone builds, you need macOS and Xcode. Android has its own SDK and device setup.
Start with one screen and one phone action. When you need a plugin for a phone feature, check its support on the platforms you intend to ship.
Which phone behavior needs a separate check?
Use a test device for the full experience around the app, including its permission prompt. Flutter’s integration test package can exercise app behavior on a target device, but it cannot operate native permission dialogs.
Use a project and test connections you control, with fictional information. Verify the device, account and storage before granting permissions or trying the action. If you cannot verify them, rehearse on paper.
Which files do you keep when you send the app to a store?
Keep the Flutter project, its Dart code and platform settings. Flutter is distributed under a BSD license. Build files such as an Android app bundle and an iOS archive or IPA are separate from your editable project.
The Android and iOS release guides document platform signing. Make sure the right people retain access to the store accounts and signing process needed for a later update.
What would you check before choosing a camera plugin?
Sketch a fictional plant journal and two permission outcomes. Use no device, project, install or store account.
- Draw the fallbackGive the reader a way to save the note with no photo.
- Make a device checklistList the phone models and the actions you would later verify, including deny permission and return to the draft.