Search for a Notion alternative for Mac and you get lists. The lists agree with each other, which should be your first clue that most of them were written from other lists. What almost none of them do is tell you how to check the one thing that people actually mean when they say they want a “real Mac app”.
You can check it yourself, on your own machine, in less time than it takes to read a review.
Test one: is it Electron?
Electron apps ship an entire copy of Chromium inside the bundle, and they cannot hide it.
Download the app, drag it to /Applications, and run this in Terminal:
ls "/Applications/Some App.app/Contents/Frameworks/"
If you see Electron Framework.framework, it is an Electron app. If
you see Chromium Embedded Framework.framework plus a set of
“Helper (Renderer)” and “Helper (GPU)” bundles, it is Chromium too, just a different wrapper.
Either way, the window you are looking at is a browser.
Test two: does it have a Mac interface at all?
An app whose interface is built with Apple's own toolkits compiles that interface into files
with .nib and .storyboardc extensions. An app whose interface is HTML
has almost none, because there is nothing to compile.
find "/Applications/Some App.app" \( -name '*.nib' -o -name '*.storyboardc' \) | wc -lNumbers in the hundreds mean a Mac interface. A single-digit number, on an app with a complex window, means the interface came from somewhere else.
What that looks like in practice
I ran both commands on one Mac on 9 September 2026, against whatever versions were installed on it that day. This is a snapshot of specific builds on one machine, not a permanent statement about these products — which is exactly why the commands are above.
| App | Frameworks folder | Interface files |
|---|---|---|
| Slack | Electron Framework | 1 |
| Discord | Electron Framework | 1 |
| Figma | Electron Framework | 1 |
| Spotify | Chromium Embedded Framework | 3 |
| Keynote | Apple frameworks | 456 |
| iTerm2 | Apple frameworks | 226 |
Notion is not in that table on purpose. I did not have it installed, so I have not measured it, so I am not going to tell you what it is — you can run the two commands above against it in less time than it took to read this sentence, and then you will know rather than having been told.
Where this test stops working — and it does
This is the part the listicles leave out, and it matters more than the rest of the page.
The commands detect Electron and Chromium Embedded Framework. They do not
detect every web app in a wrapper. macOS ships its own web view, WKWebView, and an
app built as a thin native shell around one will link Apple's frameworks, carry a handful of
interface files, and pass both tests above while still being a website. Microsoft Teams on my
machine reads as native by the framework test and ships a WebView library alongside it.
A low interface-file count is also weak evidence on its own: an app written entirely in SwiftUI genuinely has very few, because SwiftUI builds its interface in code. So a small number can mean “this is HTML” or “this is modern Swift”, and the framework test is what separates them.
In other words: a positive result is proof, a negative result is only an absence of proof. That is a real limit, and anybody telling you they can spot a native app from a screenshot is guessing.
The thing you actually care about
“Native” is a proxy, and now you know the proxy is leaky. It is worth asking what you wanted it to predict, because those things can be measured directly, in a fifteen-minute trial:
- Cold launch. Quit it, open it, count. This is the one people feel every day and the one benchmarks never cover.
- Memory at rest. Activity Monitor, after ten minutes idle with your real content in it. Chromium-based apps typically run several helper processes; add them up, not just the one with the app's name.
- Offline. Turn off Wi-Fi, create something, quit, reopen. Still offline. This one question separates more apps than the architecture does — see what Notion actually does offline.
- Mac behaviour. Does ⌘F find things? Does the Services menu work? Does text substitution? Does it survive a Space switch? These are the small courtesies that make an app feel like it belongs, and they are independent of what it is built with — plenty of Electron apps get them right and plenty of native apps do not.
- Battery. Energy tab in Activity Monitor, over an afternoon of your normal use.
If an app is quick to launch, quiet at rest, works on a plane and respects Mac keyboard conventions, it does not matter what it is built with. If it fails those, the architecture is an explanation, not an excuse.
What I am building
Platform is my answer to the same question: databases, workflows, a knowledge graph and charts in one app that is native on iPhone, iPad and Mac, and keeps working with no network because the records are on the device.
It is not on the App Store yet, so it is not on any shortlist and I am not asking you to take my word for any of the above — when it ships, run the two commands on it. Until then the waitlist is the only thing there is to join.