Changelog

This release focuses on three things: latest stable Flutter, simpler routing with go_router, and a more agentic development setup.

Latest Stable Flutter

Flutter Kit now targets Flutter 3.41.2, with updated SDK constraints (Dart ^3.9.0, Flutter >=3.41.2) and refreshed generated platform files. This keeps new projects aligned with current stable behavior out of the box, and reduces setup drift between local development and CI.

go_router by Default

Our custom navigation worked and gave us tight control, but most new feature requests kept pulling toward plug-and-play expectations. To make extension simpler for more teams, we moved the routing foundation to go_router.

Route definitions now use GoRoute and RouteBase, while the context-free RouterService stays in place as a thin wrapper over go, push, replace, canPop, and pop. The result is a more familiar routing model with less custom surface area to maintain.

Agentic Development

Alongside the routing update, we tightened routing safety with a more robust 404 exception flow and redirect-loop protection, and aligned navigation tests with the go_router behavior.

We also reworked documentation and AI guidance around agentic workflows. Core conventions are centralized in agents.md, reusable playbooks live in .claude/skills, and the docs now include a generalized Agentic Development guide instead of editor-specific instructions.

AI tools are becoming essential for Flutter development, but getting consistent, high-quality results requires proper configuration. We’ve made significant improvements to help you get the most out of AI-powered development.

Refined Flutter Kit AI Rules

We’ve completely refined the Flutter Kit AI rules to have a deeper understanding of the MVVM architecture and production patterns. The rules now provide much more specific guidance on:

• Proper dependency injection patterns
• Navigation handling
• State management best practices
• Improved folder structure guidelines

When you ask AI to implement features, you should now get significantly more consistent results that follow the Flutter Kit’s standards.

Enhanced Documentation About AI

The Flutter Kit documentation now includes links and insights into Flutter’s new AI rules template. We also provide some context on why we’re not using their rules, but it might still be valuable to be aware of.

Resolved a routing conflict in BestRouterConfig where the initialRouteInformation would ignore deep-link URLs from the platform. The router now correctly prioritizes the platform’s URL for deep links, while falling back to the RouterService state for default (/) launches. This ensures both web deep-linking and pre-configured app start-up routes function as expected.

Before

1
class BestRouterConfig extends RouterConfig<Object> {
2
  BestRouterConfig({required RouterService routerService})
3
    : super(
4
        routerDelegate: AppRouterDelegate(routerService: routerService),
5
        routeInformationProvider: PlatformRouteInformationProvider(
6
          initialRouteInformation: RouteInformation(
7
            uri: Uri.parse(
8
              routerService.navigationStack.value.last.uri.toString(),
9
            ),
10
          ),
11
        ),
12
        backButtonDispatcher: RootBackButtonDispatcher(),
13
        routeInformationParser: AppRouteInformationParser(
14
          routes: routerService.supportedRoutes,
15
        ),
16
      );
17
}

After

1
class BestRouterConfig extends RouterConfig<Object> {
2
  BestRouterConfig({required RouterService routerService})
3
    : super(
4
        routerDelegate: AppRouterDelegate(routerService: routerService),
5
        routeInformationProvider: _createRouteInformationProvider(
6
          routerService,
7
        ),
8
        backButtonDispatcher: RootBackButtonDispatcher(),
9
        routeInformationParser: AppRouteInformationParser(
10
          routes: routerService.supportedRoutes,
11
        ),
12
      );
13

14
  static PlatformRouteInformationProvider _createRouteInformationProvider(
15
    RouterService routerService,
16
  ) {
17
    final String platformInitialRoute =
18
        PlatformDispatcher.instance.defaultRouteName;
19

20
    final String appInitialRoute = routerService.navigationStack.value.last.uri
21
        .toString();
22

23
    final String initialLocation =
24
        (platformInitialRoute == '/' && appInitialRoute != '/')
25
        ? appInitialRoute
26
        : platformInitialRoute;
27

28
    return PlatformRouteInformationProvider(
29
      initialRouteInformation: RouteInformation(
30
        uri: Uri.parse(initialLocation),
31
      ),
32
    );
33
  }
34
}

• New side bar look and organization to make it easier to find what you’re looking for
• Updated structure using the Diataxis Framework
• Guided Tour to give a more thorough overview of the important features
• Better and more explanations in most documents
• Cleaner and updated UI

This new structure is more consistent by using the <product> <action> syntax. To use the new command, update your CLI by running:

1
npm install -g @hungrimind/hungrimind-cli

The initialRouteInformation in best_router.dart now uses the RouterService path instead of a default value.

Translation Without Context

You can now access a static instance of your translation using the static Translate class.

Example:

1
print(Translate.current.appName);

New Internal Notification System

By using locator<NotifyService>, you now have access to a service to either show a toast or initiate haptic feedback (vibration).

Before migration:

1
toastService.showToast(
2
  'This is a toast message',
3
);

After migration:

1
notifyService.setToastEvent(
2
  ToastEventSuccess(message: Translate.current.errorGeneric),
3
);

Haptic Feedback

Using the new notification system, you can now initiate haptic feedback.

1
notifyService.setHapticFeedbackEvent(HapticFeedbackEvent.success);

Updated Dart Formatter

We updated the formatter to better respect trailing commas.

1
formatter:
2
  trailing_commas: preserve

This is the initial release of the Flutter Kit. It includes all the core features that we use in production, such as MVVM Architecture, Routing, and more.