Generator validation and limitations

A successful download is only the start. This record explains the difference between template checks, SDK checks, and testing your own application. The SDK results below come from the project’s recorded validation work; this page does not claim a fresh SDK run whenever its documentation changes.

What automated template checks cover

The project includes checks for configuration validation, dependency selection, generated paths, source templates, and ZIP contents. Browser tests download actual Flutter and Android archives and inspect their contents. A representative configuration matrix catches structural mismatches; it is not an exhaustive compilation of every possible option combination.

Recorded Flutter SDK checks

The recorded local environment used Flutter 3.33.0-1.0.pre.947 and Dart 3.9.0-333.0.dev, a development SDK. It is not a current-stable compatibility claim.

• Clean Architecture + BLoC + Dio + GetIt + GoRouter: package resolution, source analysis, and the generated repository test passed.
• GetX + GetX DI + GetX Routing: package resolution and source analysis passed.
• Clean Architecture + Riverpod + Dio + Riverpod DI + GoRouter: package resolution and source analysis passed.
• AutoRoute + Drift with optional features: package resolution, code generation, and source analysis passed.

Recorded Android SDK checks

Clean Architecture + Jetpack Compose + Hilt + Retrofit + Room was built with JDK 17, Android SDK 35, and Gradle 8.11.1. assembleDebug and testDebugUnitTest succeeded. Other configurations have template and archive coverage, but were not all compiled or tested on devices.

Current configured Android baseline

• Android Gradle Plugin: 8.9.2
• Kotlin: 2.1.20
• Gradle: 8.11.1
• Compile SDK default: 35

Versions shown here come from the same configuration as the templates. They describe the chosen baseline, not the newest available release. Review library requirements when changing the toolchain.

What you still need to verify

• Flutter native runners and package-specific platform setup; Android wrapper and SDK setup.
• Real API behavior, authentication, persistence, concurrency, and recovery from failures.
• Accessibility, device behavior, release signing, permissions, and your application’s security requirements.
• Any configuration different from the combinations listed above.

Follow the Flutter walkthrough or Android walkthrough. If your result differs, report the configuration and SDK versions.