How project-travel-mate/travel-mate works
Main system components
a. Presentation Layer (Android UI)
b. Domain Layer (Presenters / ViewModels)
c. Data Layer (Room Database, DAOs, Repositories)
d. Network Layer (Retrofit / API clients)
e. External Services (Weather API, Twitter API, Google Places / Maps, Email Verification Service)
f. Widgets & Background Services
Classes by layer and package
– Activities & Fragments (e.g., MainActivity, HomeFragment, CityFragment, TravelFragment, etc.)
– Adapters & Views (e.g., CardViewOptionsAdapter, NestedListView, FlipViewPager)
– MVP Presenters & Views (e.g., LoginPresenter / LoginView, FunFactsPresenter / FunFactsView, FinalCityInfoPresenter / FinalCityInfoView)
– ViewModels (ChecklistViewModel, ViewModelFactory)
– Room Database (AppDataBase, Converters)
– DAOs (CityDao, WidgetCheckListDao, ChecklistItemDAO)
– DataSource / Injection (ChecklistDataSource, Injection)
– Local assets (JSON under assets/, raw/)
– API definitions (ApiResources.kt)
– HTTP client (Retrofit instance injected via Injection)
– Weather API
– Twitter API
– Google Places / Maps Web Services
– Email / Auth Service (for VerifyEmailActivity)
– CheckListWidgetProvider / Service
– ClockWidget / ConfigureActivity
Architectural patterns
• MVP pattern in login, fun facts, city info modules (Presenter ↔ View interfaces)
• MVVM pattern in checklist module (ViewModel ↔ LiveData ↔ DAO)
• Repository / DataSource abstraction for Room + Network