How himamshus06/offline_sos_bridge works
This is a Flutter application named offline_bridge. The tree includes a first-aid mobile model asset, but the README is empty and the Dart entry point was not excerpted, so the app’s user workflow and model integration cannot be established. The graph therefore shows the known application entry point and platform-host startup structure without asserting how app features use the model. Native startup and window relationships are supported by the provided excerpts; plugin registrants are shown as platform components, not wired to unsampled app behavior.
Main entry points: flutter_window.h Flutter window · main.cpp Windows startup · main.cc Linux startup · win32_window.cpp Win32 window
Components 11
Flutter app
- App entry point
lib/main.dart
Model asset
- First-aid model
ml/mobile_assets/first_aid_mobile_model.json
Platform hosts
- Windows startup
windows/runner/main.cpp - Flutter window
windows/runner/flutter_window.h - Win32 window
windows/runner/win32_window.cpp - Windows plugins
windows/flutter/generated_plugin_registrant.cc - Linux startup
linux/runner/main.cc - GTK application
linux/runner/my_application.h - Linux plugins
linux/flutter/generated_plugin_registrant.cc - macOS plugins
macos/Flutter/GeneratedPluginRegistrant.swift - iOS application
ios/Runner/AppDelegate.swift
Connections 3
- Windows startup → Flutter window: creates
windows/runner/main.cpp - Flutter window → Win32 window: inherits
windows/runner/flutter_window.h - Linux startup → GTK application: creates
linux/runner/main.cc