laem
Instructions détaillées pour l'itinéraire de transport en commun
Statut
- [ ] une 1ère version basique mais jolie des instructions <--- fixed by #592
- [ ] donner la direction du transport de façon bien visible
- [ ] représenter les trajets d'approche exacts sur la carte
Pour ça, il faut s'inspirer de l'UI Motis qui fait des appels à un autre point d'API.
{"destination":{"type":"Module","target":"/ppr/route"},"content_type":"FootRoutingRequest","content":{"start":{"lat":47.196087,"lng":-1.542473},"destinations":[{"lat":47.196194,"lng":-1.542561}],"search_options":{"profile":"default","duration_limit":900},"include_steps":true,"include_edges":false,"include_path":true}}
- [ ] afficher les prochains départs, très pratique mais pas trivial https://github.com/motis-project/motis/issues/546
Inspirations
Super retour à propos du design des détails de l'itinéraire TeC.
nyc mta’s train app has shockingly good design - even better than apple maps!
google is what you’d expect - tons of clutter iteratively added over time. no typographic hierarchy, everything kind of blends in, “live” information stands out more than critical things like which train you’re supposed to take.
apple has clearer hierarchy but feels like it could be better. “exit” is confusingly sequenced before the route, scheduled vs live times are laid out inefficiently and it’s needlessly causing anxiety with prominent schedule change alert (just tell me what’s current).
mta’s app isn’t doing anything in a super unique way, but the IA is so much clearer. trains and stations are clearly called out, alternate options are thoughtful (clock time + wait time) and more efficiently laid out.
such great execution by a public entity, i’m curious how the team pulled this off.
https://x.com/gem_ray/status/1830621889867215030
