Flightradar on a Mac: a tracking window you can leave open

Searching for a Flightradar app for the Mac produces a strange set of results. The top of the page is the App Store listing for iPhone and iPad, followed by an emulator site explaining how to run the Android version, a download mirror, and two forum threads where people ask the same question and receive no product link. That pattern is the answer, even though nothing on the page states it outright. There is no Mac application to install. The tracking map on a Mac is a web page, and the real decision is not which app to download but what kind of window that web page deserves.

What the search results are actually telling you

The pages that rank for this query fall into three groups, and each one is a different kind of dead end.

The App Store listings are for the mobile apps. They are the most substantial pages Google has to offer, which is why they rank, but installing them requires an iPhone or an iPad.

The emulator tutorials describe running the Android build inside an Android runtime on macOS. That path exists, and it is a large amount of machinery to end up with a phone interface on a desktop screen, driven by touch gestures translated from a trackpad.

The forum threads are the most honest results. People ask whether a desktop version exists, and the thread continues without one being produced.

The service's own subscription page settles it. In its answer about where a subscription can be used, it states that the subscription works on web and mobile with the same login credentials across all platforms, and that flights can be tracked on the web or in the iOS and Android mobile apps. Web and mobile is the full list. A Mac is the web half of it.

That is less of a compromise than it sounds. The browser version is the full product, with the map, the filters, the 3D view, the playback of past flights and the account that carries a subscription. What it lacks is not features. It lacks a place to live.

Why a tab is the wrong container for a live map

A flight tracker is unusual among web pages because the reason to open it is that it keeps changing. A map of current traffic is worth watching in the background, glanced at between other work, or left running on a second display during an interesting arrival sequence. That is exactly the usage pattern browser tabs handle worst.

A tab is one of thirty. It has no icon in the Dock, so returning to it means either remembering which window holds it or typing into the address bar again. It shares its window with tabs that have nothing to do with it, so closing that window closes the map too. Browsers throttle background tabs to save power, which is a sensible default for a news article and an unhelpful one for a live feed. And a map is a page that wants space: a window sized for reading text is the wrong shape for watching an approach corridor.

There is one more detail specific to this service. The plan comparison on the subscription page lists Remove timeout as one of the features that separates the free tier from the paid ones. A tracking page that is meant to stay open all afternoon is precisely the case where a session timeout is felt, and that puts the free tier and the paid tiers in genuinely different positions before any window decision is made.

What the plans change, in the terms that matter here

The subscription page lists four tiers: a free tier for personal use, then Silver, Gold and Business, with Business being the one that permits commercial as well as personal use. Prices are shown in the visitor's own currency at checkout rather than as a fixed figure on the page, so the useful comparison is in features rather than numbers.

Plan	Flight history	Usage permitted	Notable for a window left open
Free	Shortest history of the four	Personal	Session timeout applies, ads and sidebar remain
Silver	90 days	Personal	Ads and sidebar removed, more bookmarks
Gold	365 days	Personal	Longer history, more bookmarks again
Business	3 years	Commercial and personal	Longest history, highest bookmark count

Three items from that list bear on the window directly. Removing the ads and the sidebar changes how much of the window is map, which matters more the smaller the window is. Bookmarks are the saved aircraft and flights a returning window should show. And the timeout determines whether an untouched window is still tracking an hour later or waiting for a click.

The page also notes that the API is sold separately from all four plans, that each paid tier offers a seven day free trial with one trial per account, and that paid tiers can be billed monthly or yearly. None of that changes with the window, but it is worth knowing before assuming a plan covers automated access.

Three ways to give the map its own window

macOS offers two built in routes and one category of third party tool. They differ in ways that matter for a page like this one.

Route	What it needs	Session	Multiple windows	Engine
Safari, Add to Dock	Safari 17 on macOS Sonoma or later	Separate from Safari browsing	One per site, created one at a time	WebKit
Chrome, Install page as app	Chrome, any recent version	Shared with the Chrome profile	One per site, tied to that profile	Chromium
A site to app tool	Varies by tool	Separate per app in most tools	Built for making several	Usually Chromium based

Apple's WebKit team documented the Safari route when it shipped. Safari 17.0 for macOS Sonoma brought web apps to the Mac, and the procedure is File then Add to Dock, with the chance to adjust the name and icon before the app appears in the Dock. The resulting web app behaves like an application rather than a page: it works with Stage Manager, Mission Control and Command plus Tab, and it can be opened from the Dock, from Launchpad and from Spotlight.

Google documents its own route in the Chrome help pages. Installing a web app is done from the More menu, then Cast, save, and share, then Install page as app, and on some sites an Install button appears at the right of the address bar instead. The installed app inherits the profile it was created from, which means the account already signed in carries over with no second sign in.

The third route is a category rather than a single product, and it exists because the first two are designed around making one window at a time from whatever page is in front of you. Anyone who ends up with a map window, a separate window for a second account, and a third window for an unrelated service is repeating the same menu sequence and managing the results by hand. Tools in this category treat the app list itself as the thing being managed, and the Features page of one of them shows the settings that tend to matter: which browser engine an app uses, whether the tab bar and address bar are visible, and how popups are handled.

Settings worth getting right for a map window

A map window benefits from different choices than a mail window, and the defaults are tuned for neither.

Hide the browser furniture, keep the map

A tracking page has its own controls along its own edges. Stacking a tab strip and an address bar above them costs roughly sixty vertical pixels that would otherwise be sky. Both built in routes remove that furniture automatically. Tools in the third category usually make it a per app switch, which is useful when the same tool also produces windows where an address bar is wanted.

Give it its own session

Profile isolation sounds like an administrative detail until two accounts are involved, or until signing out of a Google account in one tab signs the browser out everywhere. A window with its own cookie store is a window whose login state is nobody else's business, and for a page that is supposed to survive being ignored, that independence is the whole point.

Decide what happens to popups

Authentication dialogs are popups. So are the panels some map layers open. A blanket popup block breaks the first category along with the second, which is why the more considered tools offer a middle setting that permits authentication windows and blocks the rest.

Size it once and let it stay

Web apps remember their window geometry. A map window sized to the left half of a display, or stretched across a second monitor, comes back the same shape tomorrow. That is a small thing that removes a daily gesture.

Pick the page the window opens on

The habit is to point a new window at the service's front page and pan the map into position afterwards. The map's address bar carries the current position, zoom level and filters, which means a window can open directly on a specific airport, a saved filter set or an aircraft type view. Someone watching one airfield should build the window on that airfield rather than on the global map, because the global map is a wasted first click every single time. Someone who watches two different areas is better served by two windows with two names than by one window that has to be dragged back into place. Naming each window after the place rather than after the product also makes the application switcher readable, since three windows all called the same thing are indistinguishable at the moment of switching.

What tends to break, and what to check first

Two failure modes account for most complaints about wrapped web apps, and both are avoidable.

The first is a browser update. Chromium based browsers update every few weeks, and wrappers that copy a binary or hard code a version stop launching or lose their icons when that happens. Tools that reference the installed browser rather than copying it survive the update, and some add a watcher that re sends the apps afterward. Before committing to a tool, it is worth knowing which approach it takes.

The second is the session. If a window opens to a signed out state every morning, the cause is almost always that the window is sharing a cookie store with something that clears it, or that the plan in use applies a timeout. Those are different problems with different fixes, and the plan comparison on the subscription page is where to check the second one. The FAQ of a wrapper tool is the place to check the first.

A third, smaller issue is worth naming because it is easy to misdiagnose. Map pages are demanding. A window kept open on a laptop running on battery will be throttled by macOS regardless of how it was created. That is power management doing its job, not the window failing.

What to change first

Decide whether the tracking page is something glanced at weekly or watched most days. For weekly use, a bookmark is honest and enough. For daily use, build it a window with its own session and no browser furniture, size it once, and check the Pricing of the route you choose against the plan you are already paying for.