Sprint 2 Development Flutter - G33-Moviles-2026-1/Wiki GitHub Wiki

Developers

  • Juanes:

    • BQ 12: Which are the most used tags (chilling, studing, teaching) in bookings (by building + time window)?
    • Screens: Header, Footer, Bookings, Homepage
    • SF: Near-me (Front)
    • CA: Light - dark theme
    • Sensor: Light sensor

  • Daniel:

    • Part 1

      • BQ 9: What is the most common way users upload/import their schedule (ICS/PDF file, manual), and which method has the highest drop-off by step?

    • Part 2

      • A: Clean Architecture
      • P: Repository Pattern, Use Case Pattern, Dependency Injection, Data Model Pattern (DTO),

    • Part 3

      • Screens: Schedule (3), Login, Sign up

    • Part 4

      • Sensor Used: Light Sensor for CA
      • Type 2 Question: Which rooms should the app recommend to a user during their free schedule gaps, based on their daily behavior, preferred buildings/floors, and upcoming classes?
      • CA: It detects when the phone's light level is low and switches the theme to dark mode.
      • SF: Gap-based room recommendation with fixed weights (Front y Back)
      • Auth: Sign Up and Login In
      • ES: Smart room recommendation based on the uploaded schedule (connected in the Backend)

  • Cesarín:

    • Part 1

      • Type 2 Question: What are the closest available rooms to the user?

    • Part 2

      • A: Clean Architecture
      • P: Repository Pattern, Use Case Pattern, Dependency Injection, Data Model Pattern (DTO).

    • Part 3

      • Screens: Room Detail, Search Results.

    • Part 4

      • Sensor Used: GPS for SF and CA.
      • CA: Recomends Based on the current location of the user.
      • SF: Location based recomendations on nearby rooms (backend development of the navigation graph and dijkstra)
      • ES: Smart room recommendation based on the uploaded schedule (connected in the Backend)

Diagrama de arquitectura Flutter