How jeikai/furnitureshop_appadmin works
Project type and purpose
• This is a multi-platform Flutter “admin” client for a furniture shop.
• It targets mobile (Android/iOS), desktop (Windows/Mac/Linux) and web.
• Its purpose is to let administrators log in, manage categories/products/discounts/guarantees/staff, view and respond to orders and chats, and receive notifications.
File structure
• Top‐level “android”, “ios”, “linux”, “macos”, “windows”, “web” directories = Flutter’s platform scaffolding.
• “lib” holds the Dart code, split into:
• data/ (dependency injection, auth, models, repositories, API servers, constants)
• screen/ (widgets/views + controller classes for each UI feature)
• main.dart (app entry point, bootstraps DI and routes)
• Presence of injector.dart → dependency‐injection (likely GetX or similar).
• auth_service.dart + google-services.json → Firebase authentication/push.
Readme insights
• Implies you must infer architecture from code.