How ahmedzein-dev/al-taher-jewellery works
Project Type & Purpose
• This is a multi‐platform Flutter application (mobile: Android/iOS; desktop: Linux/MacOS; web) named “altaher_jewellery.”
• It follows a modular “clean architecture” approach, with features like home, categories, blogs, currency exchange, search, favorites, contact us, about us, and a welcome/splash flow.
• State management is done with BLoC/Cubit. Data comes from remote sources (REST/Firebase), local cache, and core services (e.g., asset, theme managers).
File Structure Analysis
• Top‐level platform folders: android/, ios/, linux/, macos/, web/ – these contain platform build & plugin configuration.
• lib/ – the entire Flutter app code, organized into feature modules (home, categories, etc.) and a core folder.
• Each feature follows a “Data → Domain → Presentation” pattern:
– data/data_sources & models & repositories_impl
– domain/entities, repositories, use_cases
– presentation/blocs, screens, widgets
• lib/core/ – cross‐feature assets: constants, enums, error handling, network config, shared widgets, use_cases, managers, utils.
• pubspec.yaml – Flutter dependencies.
• android/, ios/, web/, linux/, macos/ – platform hosts Flutter engine and native configuration.
Key README Insights
• No extra architectural notes, so we infer patterns from file layout and naming.
Essential Elements
• Component labels (e.g., “CurrencyFirebaseService”).
• Notes on protocol types (REST/Firebase).