How alewwh1104/proyecto_ppm works
Project Nature and Purpose
• This project is an Android application focused on managing wishlists. It allows users to create, edit, and manage personalized wishlists.
• It employs the MVVM architectural pattern, modern UI with Jetpack Compose, API consumption via Retrofit, and user/data management using Firebase.
Key Components
a. Presentation Layer (UI):
• The UI resides under app/src/main/java with dedicated packages for different screens:
– Account views (SignIn_Screen, SignUp_Screen, Home_Screen, UserAccount_Screen)
– Catalog screens (Category_Screen, Products_Screen, AddItem_Screen, etc.)
– Guest views (Guest_Screen, AboutWish_Screen, ViewGuestList_Screen)
– WishLists views (MainLists_Screen, AddList_Screen, EventCard, ListCard, ItemCard)
• Navigation is implemented in the navigation package (AppNavigation, NavigationState) to manage transitions between these screens.
b. Domain/Logic Layer (ViewModels & Business Logic):
• MVVM is the primary pattern. ViewModel classes such as CategoryViewModel link UI components to underlying data and logic.
c. Data Layer:
• Networking: The networking package contains classes like WishAPI and WishWebService that manage REST API calls using Retrofit.
• Data Responses: The networking/response package defines response data models (e.g., WishResponse, Constants).
• Repositories: The ui/catalogs/repository package (CategoryRepository) acts as a data manager that abstracts away data source details (API calls, Firebase reads/writes).
d. External Services:
• Firebase: Utilized for user registration and managing lists/products. Though not directly visible in the file tree, Firebase integration is a key dependency.
• Retrofit: Used for consuming REST APIs to fetch product or category data.
Architectural Patterns and Design Principles
• MVVM is clearly adopted for separation of concerns between UI (Views), ViewModel (logic and UI state management), and data sources (repository/API).
• The project leverages modern declarative UI practices with Jetpack Compose.
• A modular design is apparent in the file structure (separated directories for UI components, navigation, networking, and theming).