Using Trello as a real Mac app

The Trello Mac app is easy to find and free to install, so the search usually ends within a minute. The decision it is supposed to settle does not. Boards live in a browser tab that keeps sliding out of position, notifications arrive somewhere other than where the work is happening, and installing an application feels like the fix. Whether it is depends on three published facts: where the installer comes from, which macOS versions it accepts, and what the installed copy does that a browser window does not. Two of those three surprise people.

One distribution channel, and no fallback installer

There is exactly one official place to get it. The Atlassian support documentation states that Trello for Mac comes from the Mac App Store, and Trello for Windows from the Windows Store. No disk image sits on trello.com waiting to be downloaded directly.

The App Store listing gives the specifics. The app is free, published by Trello, Inc., filed under Business, and the current listing shows version 2.16.7 at a size of 148.5 MB. Installing pulls that 148.5 MB down, hands the update channel to Apple, and ties the copy to the Apple Account signed into the Mac.

Single channel distribution is convenient right up until the channel is closed. On a Mac managed by an employer, the App Store is often restricted, and on a shared or lab machine there may be no personal Apple Account signed in at all. Some vendors publish a direct download as an escape hatch for exactly those cases. This one does not, so a blocked store means the installed app is off the table entirely, and the choice narrows to the browser or something built on top of it.

That is worth checking before anything else. Open the App Store, search, and see whether the install button responds. A minute spent there prevents an afternoon of looking for an installer that was never published.

Two published minimums that do not match

The requirement appears in two official places with two different numbers.

Source Stated requirement

Mac App Store listing Requires macOS 12.0 or later

Atlassian support documentation macOS 11.0 or higher, 64-bit only

The one that governs the install is the store listing, because that is the gate the download passes through. A Mac running macOS 11 can read the support page and reasonably conclude the app will work, then find the App Store refusing to install it. The support documentation appears to describe an earlier state of the app that has not been revised.

The practical rule: check the macOS version in About This Mac first, and treat macOS 12.0 as the floor. Below that, the installed app is not an option regardless of what any documentation says, and a browser based approach becomes the way forward, since the effective requirement then becomes whatever the installed Chromium browser still supports.

This gap is also a reminder about minimum versions generally. They move upward, they move without warning, and a Mac that runs an app today is not guaranteed to run next year's build of it. A window built on a browser inherits the browser's support window instead, which tends to be longer.

The offline argument does not exist here

The most common reason given for installing a desktop application is that it keeps working when the connection drops. For this service, that reason is explicitly ruled out by the vendor.

Just like Trello on the web, the Trello desktop apps require an active internet connection and do not support offline syncing. Source: support.atlassian.com

That single sentence removes the strongest argument for the native build and changes the shape of the whole decision. On a plane, on a train through a tunnel, or in a building with poor coverage, the installed app and the browser tab fail in the same way. Nothing is being bought with the 148.5 MB in terms of resilience.

What remains on the table is narrower and more honest: windowing, notifications, and keyboard access. Those are real benefits, and they are the only benefits. Anyone installing the app expecting a working board on a flight is going to be disappointed at the worst possible moment, so it is better to know now and plan around the browser being required either way.

What the installed build actually adds

The desktop specific features are documented, and they are worth listing precisely rather than vaguely.

Native operating system notifications, including a Dock icon badge that updates to show unread activity. A global shortcut, Command Option T on Mac, that reaches the app from wherever focus currently sits. A Touch Bar interface on compatible MacBook Pro models, offering a new window, a new card on any board, and back and forward through history. A dedicated menu bar with custom keyboard shortcuts, and a setting for which board counts as the default.

Two of those deserve caveats. The Touch Bar item only applies to the MacBook Pro models that shipped with one, so on most Macs in service it contributes nothing. The global shortcut is genuine and cannot be reproduced by a browser window, in the same way that any application specific system hotkey cannot.

The notification badge is the item people most often assume they are losing by staying in the browser, and it is the one they are least likely to lose. A standalone window built from the web version carries its own Dock icon and can show web notifications through the browser engine underneath it, so activity still surfaces outside the window. The badge behavior is not identical, but the practical outcome, which is noticing that a card moved without staring at a tab, is covered.

Power-Ups are not the thing that varies

A recurring worry before installing is whether the board will lose functionality outside the official application. For Power-Ups, it will not. They are attached to the board rather than to the machine, so a calendar view, a card repeater, or a connection to a code repository behaves the same in the installed app, in a browser tab, and in a standalone window, and the same allowance applies on every plan.

What does vary is the layer above the board. Browser extensions live in the browser profile, not in the board, and an application that bundles its own runtime cannot see them. Anyone relying on a password manager to fill the login, a clipper that files a page into a card, or a timer that reads the card title is depending on that layer.

So the question to ask before choosing is not which route supports Power-Ups, since all three do equally. It is which route keeps the browser tooling that has quietly become part of the routine. That answer usually separates the official install from the other two options faster than any feature list does.

The comparison that decides it

Three routes exist, and they differ on fewer axes than the marketing around them suggests.

Browser tab Official Mac app Standalone app from the web version

Where it comes from Already installed Mac App Store only Built locally in a minute

Minimum macOS Whatever the browser supports 12.0 or later Whatever the browser supports

Works offline No No No

Own Dock icon and Command Tab entry No Yes Yes

System wide hotkey No Yes No

Browser extensions available Yes No Yes

Second account open at the same time With a second profile No Yes, one app per profile

Extra disk used None 148.5 MB Effectively none

Read down the offline row and the usual argument disappears. Read down the extensions row and a different one appears, which is the reason many people end up choosing the third column.

Multiple Workspaces are where the single session bites

Trello work tends to spread across Workspaces rather than staying in one. A contractor sits as a guest in two client Workspaces and runs their own on the side. An agency has a board per client. A volunteer organizer has a personal Workspace and a shared one that belongs to someone else's Atlassian account.

Workspaces that belong to the same account switch cleanly inside one window. Workspaces that belong to different accounts do not, and that is where an installed application stops being enough. One copy holds one signed in session, so reaching the other identity means signing out, signing back in, and repeating that every time attention moves between the two.

Browser profiles were built for precisely this, and a standalone app can be bound to a specific profile. Two identities become two applications with two icons, two windows, and two independent sessions, both visible at once. The board from the client Workspace and the board from the personal one can sit side by side on the same screen, which is not possible with a single installed copy.

Extensions follow the profile as well. Password managers, screenshot and clipping tools, time trackers that attach to cards, and anything else already living in the browser keeps working inside that window, because the window is that browser with the tab strip removed. An application that carries its own bundled runtime starts from an empty profile where none of that is present. The Features page sets out which parts of the browser carry across, and the Supported services list shows more than 300 sites already configured with the right address and icon, so building one is a minute of work rather than a project.

The plan, not the app, sets the ceiling

Installing changes nothing about limits, and the limits are what people actually run into. The published numbers are specific.

The free plan allows up to 10 boards per Workspace, unlimited Power-Ups per board, unlimited storage at 10 MB per file, and 250 Workspace command runs per month. Standard is $5 per user per month billed annually, or $6 billed monthly, and raises those to unlimited boards, 250 MB per file, and 1,000 command runs per month. Premium is $10 per user per month billed annually, or $12.50 monthly, with unlimited command runs. Enterprise is $17.50 per user per month billed annually, which the pricing page also expresses as $210 per user per year.

The command run allowance is the one that catches people first, because automation rules consume it quietly in the background while nobody is watching a counter. The 10 board ceiling on the free plan arrives next, usually within a few months of separating work from everything else. Neither number moves because an application was installed, which is the point: the install is a question about windows and keyboards, and the plan is a question about capacity. Answering one does not answer the other.

What to change first

Check the macOS version, then check whether the App Store is reachable on this Mac. If both clear and only one account is in play, install the official build and be done. If the store is blocked, the Mac is on macOS 11, or two accounts need to be open at once, build a standalone window from the web version instead, one per profile. Kagemusha covers that second route step by step.