How niaefeup/uni works
Main System Components
a) Client Layer (Mobile Application)
• Flutter UI Components (under lib/view/)
• State Management (using Provider pattern, under lib/model/providers/)
• Local Storage (under lib/controller/local_storage/)
b) Network Layer
• HTTP Clients (under lib/http/)
• Authentication Controllers (under lib/session/)
• API Integration (under lib/sigarra/)
c) Backend Services
• University Systems (Sigarra)
• Authentication Services (OIDC)
• External Services (bus schedules, restaurants, etc.)
Component Relationships
a) Data Flow
• User Interface → Controllers → Network Layer → Backend Services
• Backend Services → Local Storage → UI Components
• Authentication Flow: Login → Session Management → Protected Resources
b) State Management
• Provider Pattern Implementation
• Lazy Loading Components
• Background Workers
Architectural Patterns
a) MVC-like Structure
• Models (lib/model/entities/)
• Views (lib/view/)
• Controllers (lib/controller/)
b) Feature Modules
• Academic (exams, schedule, courses)
• Services (library, restaurants, transportation)
• User Management (profile, settings)
Technical Implementation Details
Elements:
a) Cross-Platform Components
• Android-specific (packages/uni_app/android/)
• iOS-specific (packages/uni_app/ios/)
• Shared Flutter code (packages/uni_app/lib/)
b) Supporting Services
• Background Workers
• Notifications System
• Local Storage (Database)
[Mobile Clients]
• ↓
[Flutter Application Layer]
• ↓
[Controllers & Services Layer]
• ↓
[Network & Authentication Layer]
• ↓
[External Systems & APIs]