How scuacm/acm_mobile works
Project type and purpose
• From the file tree and README, this is a cross-platform mobile (and web) application built with Flutter (“acm_mobile”). It targets Android, iOS, and Web, and integrates with Firebase (see firebase.json, firebase_options.dart, google-services.json, GoogleService-Info.plist). There is no custom server-side component in this repo—everything runs in the client.
File structure
• Top-level platform folders:
• android/ – Android Gradle project, native launch spots, app manifest, resources
• ios/ – Xcode project, Swift/Objective-C bridging, asset catalogs
• Flutter client code in lib/:
• lib/main.dart – app entry point
• lib/pages/ – screen widgets (home.dart, club_info.dart)
• lib/components/ – reusable Flutter widgets
• lib/firebase_options.dart – Firebase SDK configuration
• Assets folder holds images for in-app use.
• test/ and lib/test/ hold unit/widget tests.
• Configuration files at root: pubspec.yaml (dependencies), firebase.json (hosting/rules), devtools_options.yaml, analysis_options.yaml.
README
• Confirms it’s a “starting point for a Flutter application.” No custom server, suggests you rely on Flutter and Firebase.