How eloxbdeveloper/muevetecb-prueba works
Muévete CB is an offline-first simulated mobility planner for Ciudad Bolívar. A traveler enters a destination, available time, and profile; the web app plans around transit routes and active community reports, then presents a recommendation and map. Travelers can submit or confirm reports, which affect later plans. A parallel simulated WhatsApp chat offers route search and reporting through the same planning and recommendation service. Data and source excerpts support these principal flows; unsampled feature wiring is omitted. Live LLM and online map tiles are optional integrations.
Main entry points: router.ts Route planner · App.tsx Web app · ReportsContext.tsx Report state · WhatsAppChat.tsx WhatsApp chat
Components 15
Traveler experience
- Web app
src/App.tsx - WhatsApp chat
src/components/WhatsAppChat.tsx - Route map
src/components/MapView.tsx
Route planning
- Route planner
src/engine/router.ts - Transit datasets
src/data - Demo scenario
src/data/scenario.json - Data validation
src/data/validate.ts
Community reports
- Report state
src/context/ReportsContext.tsx - Seed reports
src/data/reports.json - Browser storage
Recommendations
- Shared advice
src/advise.ts - Recommendation agent
src/agent/agent.ts
Other components
- Traveler
- Optional LLM proxy
- OpenStreetMap tiles
Connections 24
- Traveler → Web app: sets trip
- Traveler → WhatsApp chat: sends choices
- Web app → Report state: reads and updates
- Web app → Route planner: plans trip
- Web app → Recommendation agent: requests advice
- Web app → Route map: shows route
- Web app → Demo scenario: loads defaults
- Web app → Data validation: checks data
- WhatsApp chat → Report state: adds report
- WhatsApp chat → Shared advice: requests advice
- WhatsApp chat → Demo scenario: loads demo
- Shared advice → Route planner: plans trip
- Shared advice → Recommendation agent: gets recommendation
- Route planner → Transit datasets: reads network
- Route planner → Report state: uses active reports
- Route planner → Demo scenario: uses trip context
- Report state → Seed reports: loads defaults
- Report state → Browser storage: persists reports
- Recommendation agent → Route planner: uses route helpers
- Recommendation agent → Optional LLM proxy: requests generation
- Route map → Route planner: reads route data
- Route map → OpenStreetMap tiles: loads tiles
- Data validation → Route planner: checks references
- Data validation → Seed reports: checks reports