How pankaj1662005/wolrd10 works
Project type and purpose
• Its purpose is to present multiple UI “screens” (authentication flow, profile settings, home/time/mindmap/transcription screens) with theming support and asset-driven data (JSON in assets).
File structure
• Top-level modules:
• android/ → Android platform embedding (MainActivity.kt, Gradle build files, google-services.json)
• windows/ → Windows runner (CMake, native code)
• lib/ → Dart code (application logic & presentation)
– 0 theme/ → Theme definitions & provider
– 1auth/ → Authentication service + login/signup/verification screens
– profile_screens/ → Profile settings & competition submodule
– screens/ → Core feature screens (home, profile, time/mindmap/transcription/summary)
– main.dart → Application entry point & route setup
• assets/ → Local JSON files for offline data (Bluetooth.json, Champion.json)
• pubspec.yaml → Declares dependencies, assets & Flutter configuration
README for additional insights
• The README is the default Flutter scaffold; no custom architecture notes. All structural insights come from the file tree.