moai-lang-flutter

Riverpod provides a reactive, compile-safe state management system using providers and notifiers. Define providers for immutable state and notifiers for mutable logic, then access them from widgets via `ref.watch()` or `ref.read()`. Code generation (`riverpod_generator`) eliminates boilerplate and enables type-safe state updates across your Flutter app.

Yes. Dart 3.5 sealed classes enforce exhaustive pattern matching, and records let you destructure complex data cleanly. Use sealed classes to model domain types (e.g., network states: success, error, loading), then match on them in widgets for type-safe, maintainable UI logic without runtime errors.

go_router provides declarative, URL-based navigation that scales across mobile, desktop, and web. Define routes as a tree, use named routes for clarity, and leverage deep linking automatically. Combine with Riverpod for state-driven navigation decisions that survive app restarts and platform transitions.

Platform channels let Flutter communicate with native Objective-C/Swift (iOS) and Kotlin/Java (Android) code. Define a method channel in Dart, implement handlers on each native side, and invoke them from Flutter. This enables access to device-specific APIs, sensors, and libraries not available through Flutter packages.

Yes. `riverpod_generator` with `@riverpod` annotations generates providers automatically, catching errors at compile time and reducing manual boilerplate. It's optional but recommended for large apps; small projects can use manual providers without the generator setup.

Use `ProviderContainer` to isolate and mock Riverpod providers in unit tests. For routing, mock `GoRouter` or test routes via `GoRouterState`. Widget tests combine both: inject a `ProviderScope` with test providers and verify navigation outcomes. This isolates logic from UI, speeding up tests.