How espanholaaraucariasur-dev/gestor-territorios works
The repository appears to be a Flutter application, but its Dart application sources are absent from the supplied tree, so its user-facing workflow and domain capabilities cannot be established. The available evidence mainly describes platform launch scaffolding, plus Android/web messaging entrypoints and a Firebase Functions package. The graph shows only relationships visible in the excerpts; the messaging and backend internals are not detailed enough to connect confidently.
Main entry points: main.cpp Windows launcher · flutter_window.h Flutter host window · main.cc Linux launcher · AppDelegate.swift iOS app delegate
Components 11
Desktop shells
- Windows launcher
windows/runner/main.cpp - Flutter host window
windows/runner/flutter_window.h - Win32 window
windows/runner/win32_window.h - Linux launcher
linux/runner/main.cc - GTK application
linux/runner/my_application.h
Mobile integration
- iOS app delegate
ios/Runner/AppDelegate.swift - Android messaging service
android/app/src/main/kotlin/com/congregacion/araucaria_sur/MyFirebaseMessagingService.kt
Backend and messaging
- Web messaging worker
web/firebase-messaging-sw.js - Firebase Functions
functions/index.js
Other components
- App user
- Google Maps services
Connections 6
- App user → Windows launcher: launches
- Windows launcher → Flutter host window: creates
windows/runner/main.cpp - Flutter host window → Win32 window: inherits from
windows/runner/flutter_window.h - App user → Linux launcher: launches
- Linux launcher → GTK application: creates and runs
linux/runner/main.cc - iOS app delegate → Google Maps services: provides API key
ios/Runner/AppDelegate.swift