How farhanriaaz/secondopinionapp works
Project type and purpose
• This is a cross-platform Flutter application (mobile, web, desktop) named “second_opinion_app.”
• It serves as a client for a “second opinion” medical service, providing screens for authentication, browsing categories, uploading reports, making payments, chatting, etc.
File structure
• Top-level folders:
• android, ios, linux, macos, windows, web – platform-specific wrappers and build files
• lib – Dart code implementing the app’s architecture
• assets – static resources (fonts, images, localization JSONs)
• pubspec.yaml – dependency and asset declarations
• Within lib:
• constants – theme, asset paths, strings
• data – repository pattern with network (Dio/REST client) and local datasource layers
• di – dependency injection (get_it via service_locator, network_module, local_module)
• models – data transfer objects for authentication, categories, posts, profiles, reports, sliders
• stores – MobX state-management stores (one per feature, with generated code)
• ui – Flutter screens (login, registration, home, categories, second opinion workflow, reports, profile, support)
• utils – helper classes (device utils, Dio error handling, encryption, localization, routing)
• widgets – reusable UI components
• Key configurations:
• firebase_options.dart + google-services.json / GoogleService-Info.plist for Firebase integration
• flutter_native_splash.yaml for splash screen setup