How mohammedrabed/luqtaecommerce works
Project Type and Purpose
• This is a Kotlin-based Android mobile application (“Luqta”) implementing a second-hand, hyper-local e-commerce platform.
• It follows Clean Architecture and MVVM, uses Jetpack Compose for UI, Koin for DI, Retrofit/OkHttp for networking, DataStore + Keystore for secure storage.
File Structure
• Top-level module: app/ – Android application module with Gradle build files.
• app/src/main/java/com/example/luqtaecommerce/:
• data:
– local/ (DataStore, SessionManager, TokenManager, CryptoManager)
– remote/ (Retrofit API LuqtaApi, AuthInterceptor, SessionCookieJar)
– repository/ (interface + LuqtaRepositoryImpl)
• domain:
– model/ (entities for auth, product, cart, order, coupon, etc.)
– use_case/ (interactors organized by feature: auth, product, cart, order, payment, review, validation)
• presentation:
– auth/, main/ (home, categories, products, cart, orders, profile), splash/
– Each screen: Composable + corresponding ViewModel + UI state classes
• di: Koin modules (dataModule, networkModule, domainModule, viewModelModule, validationModule)
• ui: Shared Compose components and theme definitions
• navigation: NavGraph, destinations, bottom-nav items
• util: File utilities, retry logic
• Resources: Compose-driven layouts; XML only for manifest, navigation/config, drawables, theme values
• Build & config: Gradle scripts, ProGuard rules, network security config, wrapper scripts
Extract Key Architectural Patterns from README
• MVVM: UI (Compose) ←→ ViewModel (StateFlow)
• Clean Architecture: Presentation ↔ Domain (use cases & models) ↔ Data (repositories & data sources)
• Dependency Injection: Koin modules wire everything
• Network: Retrofit + OkHttp + Interceptors + CookieJar
• Secure storage: Android Keystore + AES via custom CryptoManager
Main Components & Their Relationships
A. Presentation Layer
• Composable screens & shared UI components
• ViewModels (injected via Koin)
→ call domain use cases, expose UI state
B. Domain Layer
• Use cases (business logic)
• Domain models/entities
→ orchestrate repository calls
C. Data Layer
• Repository implementations (LuqtaRepositoryImpl)
↔ Local data source (DataStore + Keystore)
↔ Remote data source (Retrofit API)
D. External Services
• HTTP API server (auth, products, cart, orders endpoints)
E. Infrastructure
• Koin DI container
• Android Framework (OS, Jetpack ViewModel, DataStore, Security)
Important Patterns & Tech
• Clearly label MVVM boundary between UI & ViewModel
• Clean Architecture boundaries (presentation ↔ domain ↔ data)
• DI container feeding ViewModels, use cases, repositories
• Secure storage path: TokenManager → Android Keystore + AES
• Network pipeline: OkHttpClient → AuthInterceptor → Retrofit → API