docs
/
Appmint Mobile

Build and development workflow

Use the project toolchain, target the intended backend and run the native mobile app.

Use the Flutter version pinned in .fvmrc and the SDK constraints in pubspec.yaml. The project pin is Flutter 3.47.7; the package requires Dart 3.13 or later below 4.0 and Flutter 3.47 or later.

Prepare the toolchain

Select the project's Flutter installation, then resolve dependencies:

flutter --version
flutter pub get
flutter devices

Use the selected executable consistently for dependency resolution, analysis, builds and launch. An older system Flutter installation can have a Dart version below the project's requirement.

Connect to the intended environment

Pass explicit endpoints when working against a local server:

flutter run -d <device-id> \
  --dart-define=APPENGINE_URL=http://<development-host>:3300 \
  --dart-define=STUDIO_URL=http://<development-host>:3100

A physical phone uses a reachable development-host address. On an Android emulator, the host machine is available through the emulator's host alias. On a browser or simulator, choose the address appropriate to that runtime. Keep backend and Studio endpoints in the same intended environment.

Native launch

Use the exact device identifier when multiple phones, tablets or simulators are available. For iOS, open ios/Runner.xcworkspace to manage signing, the development team, provisioning and the entitlements required by enabled native features. Unlock and trust the physical device when prompted by the operating system.

For Android, prepare the SDK, grant device-debugging authorization and use the project's Gradle configuration. Hardware discovery also requires the runtime permissions for the platform version.

Verification commands

flutter analyze
flutter test
flutter build apk --debug
flutter build ios --debug

Use the relevant module checks while developing a change, then exercise the resulting workflow in the app. Native camera, Bluetooth, NFC and terminal features require the appropriate native platform and hardware. Browser previews are useful for layout and ordinary record workflows.

Workflow verification

Follow setup through the operator action and the resulting business record. Cover payments already made before reopening checkout, receipt delivery separate from payment, repeated product scans, saved-device reconnection, and event entry/exit and benefit rules. Keep environment-specific credentials and private customer records out of documentation and source-controlled artifacts.

See Environment, Architecture and Release.