How sambandhabhattarai/e-gym-app works
Main Components
• • Application Core & Entry Points:
• The starting point is defined in App.xaml, AppShell.xaml, and MauiProgram.cs.
• Solution file and project file (.csproj) which configure the build and overall project settings.
• • UI Layer (Views):
• All XAML pages under the Views/Pages folder – e.g., LoginPage, HomePage, WorkoutPage, etc.
• Class files associated with these pages (code-behind such as MainPage.xaml.cs, etc.).
• • ViewModel Layer:
• The ViewModels folder features the application’s execution logic and data-binding for the UI (e.g., LoginViewModel, HomePageViewModel, various exercise view models).
• This supports the MVVM (Model-View-ViewModel) pattern.
• • Model & Data Layer:
• Under Views/Classes, you have model definitions (e.g., User, Exercise, NotificationService, WorkoutDatabase, and UserDatabase) which serve as the data layer.
• • Converters:
• The Converters folder contains classes like the BooleanAndConverter used by the UI for data transformations.
• • Platform-Specific Implementations:
• The Platforms directory separates code for Android, iOS, Windows, MacCatalyst, and Tizen.
• Each platform includes its respective initialization files (e.g., MainActivity.cs for Android, AppDelegate.cs for iOS) and resource definitions.
• • Resources:
Relationships and Interactions
• • MVVM Pattern:
• That ViewModels interact with the underlying models (e.g., User, Exercise) and services (e.g., NotificationService, database services).
• • Platform Layer:
• That the .NET MAUI framework uses a single shared code base for all platforms, while platform-specific functionalities are abstracted in the Platforms folders.
• • Data Flow:
• How user inputs in the UI layer (pages) are processed by the ViewModels, which then interact with the Models (workout and user databases) to retrieve or store data.
• • Resources and Styling:
• That the UI components reference styles, images, and fonts organized under the Resources folder.
Architectural Patterns & Technologies
• • MVVM is the primary design pattern employed.
• • .NET MAUI is the framework that drives cross-platform support.
• • XAML coupled with C# code-behind for UI definitions.
• • Platform abstraction for device-specific implementations.
• • Dependency injection is likely utilized in MauiProgram.cs to manage services.