How hyuniedev/ryokou-mobile works
Project Type and Purpose
• This is a mobile tour booking application aimed at providing a transparent, personalized, and efficient experience for both customers seeking tours and service providers managing them.
• Although the README mentions Flutter, the file structure (with Gradle, AndroidManifest.xml, and Kotlin/Java source code) indicates an Android native project implementing an MVVM-like architecture.
File Structure to Define Architectural Components
• The “Code/app” directory contains the main Android application.
• The “src” folder separates different layers:
• The UI layer is represented by packages such as view (components, items, scenes) and viewmodel.
• The domain or business layer is in “model” which contains entities (e.g., User, Tour, Notification, etc.), enum classes, controllers (e.g., DataController, FirebaseController, NotificationController, UserAnalytics), repositories, and UI states.
• The “tool” package holds utility classes (e.g., ToolReadDataTour, ToolUpdateTour) that likely facilitate business operations or data manipulation.
• Resources (in “res”) support the visual assets.
• Build and configuration files (gradle settings, wrapper, Gradle Kotlin scripts) indicate the project build process.
README for Additional Architectural Insights
• The README explains that Ryokou is focused on the tour booking domain—involving functionalities like tour search, booking, personalized recommendations, and management for both users and providers.