On a transit homepage, the temptation is to put every useful tool above the fold: route planning, alerts, fares, passes, news, schedules, and service links. On a phone, that can turn one important task into a crowded, slow experience.
In our CARTA work, we treated trip planning as a primary rider task rather than another piece of homepage decoration. The mobile experience benefits from a dedicated destination that gives the planning tool enough room, keeps the user’s attention on the journey, and avoids fighting with other homepage content.
A homepage should orient; a task page should help someone finish
The homepage still has an important role. It can make trip planning easy to find, communicate the service brand, and surface active disruptions. But a rider entering an origin and destination needs a calmer environment, clear labels, a large enough interface, and a sensible path back to related service information.
- Use an obvious “Plan your trip” action in the mobile navigation or homepage tools area.
- Give the trip planner a dedicated URL that staff can link to in alerts, email, and social posts.
- Keep related items nearby: service alerts, fare information, rider help, and accessibility details.
- Test it on an actual phone, not only a desktop browser narrowed to mobile width.
Task clarity beats feature density
This is a useful lesson for any public-service site. A permit search, payment portal, service request, or job application may deserve its own focused entry point. The website feels more helpful when the high-value task is allowed to breathe rather than being squeezed into an all-purpose homepage layout.