smf_flutter_core 0.5.0

The module that creates the Flutter app every SMF app starts from, with its Android and iOS projects, main(), start-up and root widget.

example/README.md

The Flutter app that every SMF app starts from

Every app that the SMF CLI generates has the app entry role, and flutter_core provides it. While it is the only module that does, you don't choose it. Without -m, an app has this module alone:

dart pub global activate smf_flutter_cli
smf create my_app --no-input

smf create adds it by itself as the only module that provides the app entry role, and says why:

Adding flutter_core: the only provider of the app entry role, which every app needs.

The module writes the Android and iOS projects that flutter create writes, pubspec.yaml, analysis_options.yaml, the README of the app and this code:

lib/app.dart
lib/bootstrap.dart
lib/core/app/fallback_start_screen.dart
lib/main.dart
test/core/app/fallback_start_screen_test.dart

The template of the app entry role adds two more files, whichever module provides the role: lib/core/app/status_bar_icons.dart, the widget that asks the system for the icons of the status bar that suit the theme, and its widget test, test/core/app/status_bar_icons_test.dart.

An app with this module alone starts on the fallback start screen. For my_app it shows a cell with the symbol Ma and the number 5, both made from the name of the app. Below the cell are My App, a hint that the app has no start screen yet, and the path of the file of the screen, which a tap copies. Add a feature whose route can start the app, such as home, and the app starts there instead. It then has no fallback start screen and no test of it.

main() runs bootstrap() before the first frame. Other modules put their start-up code into bootstrap(), such as the start of Firebase, and their wrappers around the root widget, such as the ProviderScope of Riverpod:

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await bootstrap();
  runApp(const App());
}

The documentation has more on the flutter_core module and on the files of a generated app.