How iloveflo/mobile_programming works
This is a Flutter app for managing debt repayment schedules and viewing personal credit health, as stated in the README. Its apparent user journey spans authentication, a home/loan portfolio, loan details and repayment scheduling, with credit-health reporting as a related capability. The tree also shows mock and remote repository implementations, API infrastructure, and domain models. Those connections and runtime flows could not be verified: the supplied source excerpts cover platform runners, not the Dart product code. Dashed edges mark only tentative relationships; no platform-runner internals are included.
Main entry points: interfaces Repository contracts · loans Loan screens · auth_controller.dart Authentication · loan_controller.dart Loan operations
Components 18
User experience
- Sign-in screens
lib/screens/auth - Home dashboard
lib/screens/home - Loan screens
lib/screens/loans - Payment schedule
lib/screens/schedule - Credit health
lib/screens/credit - Profile and settings
lib/screens/profile
Financial features
- Loan domain data
lib/models - Credit domain data
lib/models/credit_profile_model.dart - Auth domain data
lib/models/user_model.dart
Application logic
- Authentication
lib/controllers/auth_controller.dart - Loan operations
lib/controllers/loan_controller.dart - App navigation
lib/routes/app_router.dart
Data access
- Repository contracts
lib/repositories/interfaces - Mock repositories
lib/repositories/mock - Remote repositories
lib/repositories/remote - API client
lib/core/network/api_client.dart - Credit health schema
credit_health_db.sql
Other components
- App user
Connections 15
- App user → Sign-in screens: uses
- App user → Home dashboard: views portfolio
- Home dashboard → Loan screens: opens loans
- Loan screens → Payment schedule: views schedule
- App user → Credit health: views credit health
- App user → Profile and settings: manages profile
- Sign-in screens → Authentication: delegates
- Loan screens → Loan operations: delegates
- Loan operations → Loan domain data: uses models
- Authentication → Auth domain data: uses models
- Authentication → Repository contracts: uses contract
- Loan operations → Repository contracts: uses contract
- Mock repositories → Repository contracts: implements
- Remote repositories → Repository contracts: implements
- Remote repositories → API client: uses client