How mrihsann/sales-tracking works
Project type and purpose
• This is a native Android mobile application named “Sales Tracking.”
• It follows a “Clean Architecture” (or layered) approach with MVVM and Jetpack Compose for UI.
• Its purpose is to let sales teams track orders, products, and performance metrics offline via Room database.
File structure
• Top-level files: gradle scripts, settings, wrapper, README.
• app/src/main/java/com/ihsanarslan/salestracking contains these key packages:
• data – Entities, Room DAOs, STDatabase (local persistence)
• domain – DTOs, repository interfaces & implementations, and use-case classes grouped by feature (order / product)
• presentation – MVVM ViewModels + Composable Screens (Home, OrderList, ProductList, Analysis) and their UI components
• navigation – NavigationGraph & Router for Compose navigation
• di – AppModule.kt for dependency injection
• ui/theme & util – theming, Resource wrapper, app entry (StApplication.kt), MainActivity.kt
README for additional insights
• Confirms a small/medium business focus and that it’s designed for offline-first, local data tracking.
Elements
• Clear labels: “Composable Screens,” “ViewModels,” “UseCases,” “Repositories,” “Room DAOs,” “STDatabase”
• Green for domain/use-case
• Orange for data/DAO/DB
• Gray for Android framework