Citymapper on the desktop: the route beside what you are doing

Most journeys are planned somewhere other than the street. They are planned at a desk, with a calendar invite open, a booking confirmation in another window, and a question that sounds like whether leaving at ten past eight is early enough. That is a desktop task, and it is the reason people search for Citymapper on the desktop rather than reaching for a phone that is sitting right there. The answer is better than the search results suggest, and it is not an application.

Where Citymapper actually runs

The App Store listing is unusually narrow, and reading it is the fastest way to stop looking for something that does not exist. Citymapper: All Live Transit, published by Citymapper Limited, is free, sits in the Navigation category, and lists two device classes: iPhone on iOS 17.0 or later, and Apple Watch on watchOS 10.0 or later.

There is no iPad entry and no macOS entry. The absence of the iPad line is the more striking of the two, because it means this is a phone application by design rather than a phone application that happens not to have been ported. And without a macOS line, which is what Apple adds when a developer allows an iPhone and iPad build to run on Apple silicon, there is no App Store route on any Mac.

The company's own site is consistent about this. The download section on the home page offers two destinations, iPhone and Android, and no third. The listing also carries a note that the app may use location even when it is not open, which can decrease battery life, and that single line explains the whole design: this is software built around knowing where a person is, right now, on the move. A laptop is not that.

The website is a real journey planner

This is the part that search results bury. The home page carries a working journey planner: a start field, an end field, and a choice between planning for now, for a chosen arrival time, or for a chosen departure time, with a GO button and a city selector alongside.

Opening a city goes further. A city page shows a live map with layers for the modes that city has, which in London means cycles, bus, tube, rail, ferry and tram, and underneath it a list of lines with current status against each one. On a single visit the list distinguished lines that were closed for the night from lines with amended timetables and lines with major disruption between named stations, and it named the stations. There is also an all lines view, a nearby view, an account to sign into, and a meet me feature for finding a point between two people.

For planning, that is most of what anyone needs. Comparing two departure times, checking whether a line is running before committing to a route, and working out whether a connection is realistic are all reading and comparing tasks. They belong on a large screen, next to whatever prompted the question. The desktop version is not a cut down preview of the app. It is the planning half of the product.

What stays on the phone

It is worth being specific about the other half, because the difference is not arbitrary. The app description lists turn by turn navigation for transit, walking, cycling, bike shares and scooter trips, a GO mode that follows progress through a journey, alerts for when to get off, guidance on the best train car to board and the best station exit to use, charge levels for nearby e-scooters and e-bikes, offline access to maps including the official New York subway map and several bus maps, live trip sharing so a friend can follow an arrival, and saved Home and Work locations for fast planning.

Almost every item in that list depends on a device that moves with the person and knows where it is. None of them are things a laptop on a desk can do, and no browser window will change that. The honest division is simple:

	Phone app	Website in a browser	Website in its own window
Plan a journey ahead of time	Yes	Yes	Yes
Compare departure and arrival times	Cramped	Yes	Yes
Live line status for a city	Yes	Yes	Yes
Turn by turn navigation while moving	Yes	No	No
Offline maps	Yes	No	No
Reachable in one keystroke at a desk	No	Buried in a tab strip	Yes

The last row is the only one a reader can change today, which is why the rest of this is about the window rather than the features.

Seen that way, the two halves stop competing. The desk decides the question, which is which route and what time to leave, and the phone executes it, which is the part that needs a moving device and a battery. The listing's own warning about background location use is a reminder of what that execution costs, and it is a cost worth paying only while actually travelling. Deciding at a desk and navigating on the street is not a compromise forced by a missing app. It is the division the product was built around, and the website exists because the company knows the deciding happens somewhere else.

One feature does sit oddly across the line. The city pages include a meet me view for finding a point between two people, which is a planning task by nature and a conversation that usually happens over a keyboard rather than on a pavement. It is one more reason the browser side is worth having reachable.

Why a tab is the wrong container for it

A journey planner has an unusual usage pattern. It gets opened for ninety seconds, several times a day, always in the middle of doing something else. That pattern is the one browsers handle worst.

It is never where it was left

A tab opened this morning is now somewhere in a strip of thirty favicons, and finding it takes longer than retyping the address. So people retype the address, which means a new tab every time, which means the strip grows. Within a week there are four Citymapper tabs and none of them is the one with the route in it.

The map is the first thing squeezed

A map wants vertical space. A browser gives away the top of the window to a tab strip, an address bar and often a bookmarks bar. On a laptop display that is a meaningful fraction of the height, taken from the one element that needs it most, before any journey has been planned.

The wrong keystroke closes it

Cmd+W closes the frontmost tab, and in a crowded window the frontmost tab is regularly not the one intended. A half entered journey with two addresses typed into it is exactly as easy to lose as a search result nobody wanted.

Location prompts and extensions

A planning site asks for location once, and the answer is stored per browser profile and per site. In a browser carrying a content blocker and a dozen other extensions, that permission and the map's behaviour are entangled with everything else installed. A window whose extension state and permissions are set for one site is a smaller thing to reason about.

Giving the map its own window

macOS has a documented route that costs nothing. In Safari, open the page and choose File then Add to Dock. Apple's support article states what that produces.

The web app is saved to the Applications folder of your home folder, and you can also open it from the Dock or Spotlight. Source: support.apple.com

That is an item on disk rather than a bookmark, so Spotlight finds it and Cmd+Tab reaches it directly. The same article notes the feature requires macOS Sonoma 14 or later, and lists the settings each web app carries: the name, the URL the window opens, the icon, whether navigation controls appear in the toolbar, and whether the title bar takes its colour from the site. Setting the URL to a specific city page is the detail that pays off daily, because it means the window opens on the right map instead of on a city selector.

Where that route stops is worth knowing. It is Safari only, with no choice of engine, and it needs a recent macOS. A site to app tool covers the rest: a Chromium based window, a profile that belongs to that window alone so the signed in account and the location permission are not shared with every other tab, per app control over extensions, and the option to hide the tab bar and address bar entirely so the map gets the whole window. The supported services list shows how the same pattern is applied to maps, mail and calendars, which is the group of sites people most often want one keystroke away.

The three settings worth getting right

Point the window at a city page rather than the home page, so no selector stands between opening it and reading a route. Turn the navigation controls off, because a planner needs no back button and the pixels are better spent on the map. And give it a distinct icon, since the value of this arrangement is entirely in being able to find it without looking.

Cities, and the thing to check before committing

Coverage is the one variable that decides whether any of this is worth doing, and it is city by city rather than country by country. The site describes a city list covering major transit cities worldwide and maintained centrally, and a separate advertising page describes reach across more than 400 major cities. The correct move is not to trust a number but to open the city switcher and look for the relevant city, then check whether the line list for it shows live status rather than a timetable.

Two other facts are worth carrying. The company now sits within Via, which is described on the site as the next stage of the same journey, and the news feed shows a subscription tier called CLUB whose boundary has moved recently: one entry describes CLUB features becoming available to everyone, and a later one describes an AI assisted route selection beta limited to CLUB members. The practical reading is that the feature line is not fixed, so a claim about what is behind the tier is worth checking in the product rather than in an article. The guide covers the window side, which is the part that does not change.

What to change first

Open the city switcher on the website and confirm the relevant city shows live line status, because that single check decides whether a desktop window is useful at all. If it does, put that city page into its own window today with the navigation controls hidden, so the next journey is planned without hunting through a tab strip, and if the window needs its own profile and its own permissions rather than sharing the browser's, Kagemusha is one way to get it.