danielmonettelli/dotnetmaui-mitawi-weather-app-challenge

Purpose and Entry Points

Mitawi is a cross-platform .NET MAUI weather client migrated from an earlier Mitawi app. It retrieves weather data from OpenWeather using a developer-provided API key and presents welcome, home, and detail experiences across mobile and desktop targets. App startup and dependency setup originate in Mitawi/MauiProgram.cs; Shell navigation is rooted at Mitawi/App.xaml and Mitawi/AppShell.xaml.

Runtime and Platform Boundary

The application runs on .NET MAUI/XAML, with shared UI, models, services, and view models in Mitawi/. Native hosting and packaging are isolated under Mitawi/Platforms/Android, Mitawi/Platforms/iOS, Mitawi/Platforms/Windows, Mitawi/Platforms/MacCatalyst, and Mitawi/Platforms/Tizen. This separates common application behavior from platform lifecycle, manifest, entitlement, and package concerns.

Application Composition and Navigation

Mitawi/App.xaml.cs initializes application-level resources, while Mitawi/AppShell.xaml.cs coordinates Shell-based page routing. The primary user flow is Welcome → Home → Home Detail, represented by Mitawi/Views/WelcomePage.xaml, Mitawi/Views/HomePage.xaml, and Mitawi/Views/HomeDetailPage.xaml. Orientation-specific layouts under Mitawi/Views/Orientations provide alternate presentations without moving weather logic into platform code.

Presentation and State Layer

The project follows an MVVM split: XAML pages bind to view models, which hold UI state and commands, rather than directly owning API operations. Mitawi/ViewModels/Base/BaseViewModel.cs supplies shared view-model behavior. Mitawi/ViewModels/WelcomeViewModel.cs, Mitawi/ViewModels/HomeViewModel.cs, and Mitawi/ViewModels/HomeDetailViewModel.cs correspond to the major stages of the navigation flow and mediate service results for display.

Weather Data Boundary

Mitawi/Services/IWeatherDataService.cs defines the weather-data abstraction used by the presentation layer. Mitawi/Services/WeatherDataService.cs implements the outbound integration with OpenWeather, keeping HTTP/API specifics outside views and view models. API endpoint and key-related constants are centralized in Mitawi/Constants/APIConstants.cs; credentials are an external deployment/developer concern, not an app-owned backend.

Data Mapping and UI Transformation

Weather payload state is represented by Mitawi/Models/WeatherData.cs, forming the main contract between service and view models. XAML converters transform raw values into presentation-ready values—for example timestamps, images, signs, and abbreviated text—at the binding boundary: Mitawi/Converters/UnixTimeToDateTimeConverter.cs, Mitawi/Converters/OpenWeatherImageUrlScalingConverter.cs, and Mitawi/Converters/NegativeAndPositiveNumberConverter.cs. Shared visual resources and converter registration reside in Mitawi/Resources/Styles/Converters.xaml and Mitawi/Resources/Styles/Styles.xaml.

Assets and Delivery

MAUI-managed branding, fonts, images, splash assets, and styles are contained in Mitawi/Resources. The solution/project entry for builds is Mitawi/Mitawi.sln and Mitawi/Mitawi.csproj. CI is configured through .github/workflows/mobile.yml, indicating automated mobile build validation; no server-side infrastructure is present in this repository.