How mpadillae/misw4203-202415-vinilos works
Main Components
a. Client Layer (UI):
• Activities and Fragments (from ui/albums, ui/artists, ui/collectors)
• Adapters (for RecyclerViews)
• XML Layouts
b. Presentation Layer:
• AlbumListViewModel
• ArtistListViewModel
• CollectorListViewModel
c. Domain Layer:
• AlbumRepository
• BandRepository
• CollectorRepository
• MusicianRepository
d. Data Layer:
• Create two parallel containers:
1. "Network Services" containing:
• RetrofitApiClient
• Various service interfaces (AlbumService, BandService, etc.)
2. "Models" containing:
• Data classes (Album, Band, Collector, etc.)
Component Relationships
• UI Layer → ViewModel Layer (user actions)
• ViewModel Layer → Repository Layer (data requests)
• Repository Layer → Network Services (API calls)
• Network Services ↔ External API
• Models should be shown as being used across all layers
Technical Stack Indicators
Technology labels:
• Kotlin
• Retrofit
• MVVM
• AndroidX
• LiveData
• Glide
• Material Design
[UI Layer (Activities/Fragments/XML)]
• ↓
[ViewModels (MVVM Pattern)]
• ↓
[Repositories]
• ↓
[Network Services] ←→ [Data Models]
• ↓
[External API]
Where shared utilities and constants are used across the application.
This will provide a comprehensive view of the Vinilos application's architecture while maintaining clarity about how different components interact with each other.