Flutter requirements
This page is for the builder who compiles Veldriq Field. Technicians do not install Flutter. This SKU is source: you produce the APK, AAB, or iOS archive. It does not include Laravel.
This documentation does not promise Google Play or App Store review outcomes. It does not include a Flutter SDK install tutorial — use flutter.dev.
Why this toolchain
Section titled “Why this toolchain”pubspec.yaml requires Dart SDK ^3.12.2. Flutter 3.44.x stable ships that Dart. Older Flutter that still reports Dart 3.11 will fail flutter pub get.
Toolchain
Section titled “Toolchain”| Tool | Expected | Why |
|---|---|---|
| Flutter | 3.44+ stable (flutter --version) |
Matches Dart 3.12.2+ required by sdk: ^3.12.2 |
| Dart | 3.12.2+ (ships with that Flutter) | Same toolchain — do not install Dart separately |
| JDK | 17 | Android compileOptions and Kotlin JVM target are 17 |
| Android Gradle Plugin | 9.0.1 (in this tree) | Do not upgrade AGP as a first-run step |
| Gradle | 9.1.0 (wrapper) | Shipped wrapper; let Flutter invoke it |
| Android SDK | SDK + cmdline-tools + build-tools | compileSdk 37; targetSdk follows Flutter (currently 36); minSdk follows Flutter (product target 24) |
| Xcode | 15+ on macOS | iOS only. Deployment target 15.0. Not required for Android-only buyers |
| Backend | Licensed Veldriq 1.x with Field APIs | /api/v1/mobile/* and /api/v1/field/sync/* on your origin |
Confirm
Section titled “Confirm”flutter doctor -vflutter --versionflutter --version must show Flutter 3.44+ and Dart 3.12.2 or newer. flutter doctor must show these as [✓] before a store upload: Flutter (stable), Android toolchain, Android Studio or another IDE (SDK still required), a connected device or emulator for flutter run. On macOS, if you ship iOS: Xcode.
If it fails: fix every Android (and, if you ship iOS, Xcode) line marked [!]. You can ignore Chrome / web. You can ignore CocoaPods for Android. This tree does not ship a Podfile; do not run pod install by hand as a first-run step.
What you do not need on the Field machine
Section titled “What you do not need on the Field machine”- Composer, PHP, MySQL, Redis, or Bun — those belong to the Veldriq web install.
- Firebase files.
google-services.json/GoogleService-Info.plistare not required to compile, launch, or sign in. - Vendor keystores or Apple certificates. You supply your own.
dart run build_runnerfor a V1 reskin. Drift.g.dartfiles are already committed.- A purchase-code field in this app. Licenses are activated on the web product.
Accounts to have ready (web product)
Section titled “Accounts to have ready (web product)”Platform Admin → Settings → License & Products (/admin/settings/license):
- A running Veldriq origin you control, HTTPS for production
- Field purchase code activated: status Active, Revalidation due, or Grace — a web Veldriq code that is Active does not license Field
- A staff user with an Active technician profile plus permission
field.workspace.view - Your own Android
applicationIdand (if shipping iOS) Apple Developer team + bundle id
There is no per-technician, per-device, or seat quota. One Field purchase covers one production deployment.
Related: Installation · API base URL.