Meeting Minutes ‐ Frontend

List of Frontend Meeting Minutes

• 2025-09-17: Frontend Tech Stack Discussion

Frontend Tech Stack Discussion

Wednesday, September 17th, 2025

Attendance:

• Thomas Mahut
• Jutipong Puntuleng

Absent: none

Note takers: Thomas Mahut

Notes:

• The following technical stack was decided on by the frontend team:
  1. React (React Router v7)
  2. Mapbox (mapbox-gl)
  3. tailwindcss
  4. shadcn/ui
  5. No state management library
• A state management library like Redux might not be necessary - we opt to start without one and we remain open to adopting one if it becomes a good idea.
• Jutipong suggests Zustand as a possible state management library - more research should be done in this area.
• Jutipong hasn't worked with Mapbox before, but agrees with proceeding with Mapbox given:
  1. Mapbox is more versatile when it comes to adding interactive elements to the map
  2. Mapbox is based on OpenStreetMap (OSM) data, which the simulation sub-system may use for generating routes.
• Attendees agree to proceed with using mapbox-gl directly (instead of through some third-party React library) for performance and control reasons.
• All dedicated frontend contributors have experience with tailwindcss.
• Jutipong hasn't used shadcn/ui components before, but understands their advantages and has no issue with using them.
• Attendees agree with the rough wireframes that map out sprint 1's frontend implementation

Action items:

• Add a section on Zustand to the tech stack research document.
• Finalize the frontend portion of the tech stack research document.
• Get feedback from Stakeholder on wireframes.
• Add frontend requirements to the SRS document.
• Create & assign tasks for Sprint 1's frontend implementation.