How hasibcore/train-router works
This is a Flutter application named train_router; the README provides no product-specific behavior beyond identifying it as a starter project. The tree suggests a user-facing flow spanning startup, authentication, train search/details/seats, and profile/navigation, but the Dart implementations were not excerpted, so those connections are shown as unverified. The platform runner files are framework shells; no booking, routing, or train-data service can be confirmed from the available evidence.
Main entry points: home_page.dart Home page · auth_service.dart Auth service · main.dart App startup · splash_screen.dart Splash screen
Components 16
App shell
- App startup
lib/main.dart - Splash screen
lib/splash_screen.dart - Home page
lib/home_page.dart - Unavailable page
lib/under_construction_page.dart
Account
- Auth service
lib/auth_service.dart - Login page
lib/login_page.dart - Login screen
lib/login_screen.dart - Sign up
lib/sign_up_page.dart - Profile page
lib/profile_page.dart
Train experience
- Train search
lib/train_search_page.dart - Train details
lib/train_details_page.dart - Seat display
lib/seat_show_page.dart
Shared navigation
- App bar
lib/custom_widgets/app_bar.dart - App drawer
lib/custom_widgets/app_drawer.dart - Bottom navigation
lib/custom_widgets/bottom_navigation.dart
Other components
- App user
Connections 12
- App user → App startup: opens app
- App startup → Splash screen: may show
- Splash screen → Home page: may enter
- Home page → Login page: may navigate
- Home page → Train search: may navigate
- Login page → Auth service: may authenticate
- Login screen → Auth service: may authenticate
- Sign up → Auth service: may register
- Home page → Profile page: may navigate
- Train search → Train details: may select
- Train details → Seat display: may view
- Home page → Unavailable page: may navigate