Notifio exists as two pieces of front end. There is the website, 38 pages of Next.js that explain the product and sell it, and there is the desktop app itself, an Electron renderer you install from the download page. Same product, same person writing both, a few weeks apart.
I have counted the colours on each of them separately before. The website's stylesheet turned out to lean on #a3a3a3 138 times, a value Tailwind dropped from its own palette. What I had never done is put the two sets side by side and ask how much of the brand is actually shared, rather than remembered.
The two sets
For the website I counted every six-digit hex in what it actually serves: all 38 live pages plus the single stylesheet they link.
cat p_*.html site.css | grep -oE '#[0-9a-fA-F]{6}\b' | tr 'A-F' 'a-f' | sort -u
For the app, the same expression over the renderer source.
distinct occurrences
served website 34 9,800
Electron renderer 39 322
union 58
shared 15
website only 19
app only 24
Fifty eight colours for one product, and a quarter of them are on both surfaces.
The part that agrees
The shared 15 are, almost exactly, the greyscale:
#fafafa #e5e5e5 #a3a3a3 #737373 #525252
#404040 #3a3a3a #262626 #1a1a1a #0f0f0f #0a0a0a
#4ade80 #f87171 #facc15 #14532d
Eleven neutrals and four status colours, green, red, amber, and one dark green panel background. The ranking agrees too. #fafafa is the most used value on both surfaces, 2,171 times in what the website serves and 60 times in the app's source, and #a3a3a3 and #525252 are in the top five on both. That is the Tailwind neutral ramp typed out as literals in two repos, which is a boring kind of consistency but it is real consistency: text, borders and panels do look like the same product.
The part that does not
The 24 the app has alone are the ones that surprised me least once I saw them:
#1e3a8a #60a5fa #93c5fd #0a1229 a blue and a navy panel, neither on the site
#450a0a #2a0a0a #3a0f0f #7f1d1d darker reds and their borders
#422006 #2a1f04 #241a04 #3a2c06 darker ambers
#854d0e #a1850a #7a6a10 #7c5212 more amber borders and text
#052e16 #166534 darker greens
#ef4444 #fb923c #fca5a5 #fcd34d brighter status text
#d4b106 #171717 one more amber, and one more grey
Twenty three of those 24 are a palette the website never needed. A row in the app sits in one of several states, and each state needs a tinted panel plus a border plus a text colour that stays legible on it. The website writes sentences about those states and never has to paint one, so the dark tints had nowhere to come from. That is a genuine asymmetry rather than drift. The twenty fourth, #171717, is just a grey that got typed once.
The 19 the website has alone are a different story:
#0d0d0d #141414 #1c1c1c #1e1e1e #252525 #2a2a2a #2e2e2e
#383838 #4a4a4a #6a6a6a #c0c0c0 #d0d0d0 #d4d4d4
#a855f7 #ff6568 #0a1a0a
#ff5f57 #ffbd2e #28c840
The first thirteen are greys between the greys in the shared ramp, which is the kind of thing that happens when you are drawing a mockup and want a panel slightly darker than the one next to it. Those are drift, and they are cheap to fix.
The last three are my favourite finding in the batch. #ff5f57, #ffbd2e and #28c840 are the macOS close, minimise and maximise buttons, and they appear in three components:
HeroDemo.tsx h-3 w-3 rounded-full
BrowserDemo.tsx h-2.5 w-2.5 rounded-full
AutoReplyDemo.tsx h-2.5 w-2.5 rounded-full
The website draws a picture of a Mac window, three times, on the homepage and in the demos, with hand-typed traffic lights at the top of it. The actual app opens a real window with titleBarStyle: 'default', which means macOS draws those buttons and the app never specifies their colour. So three of the colours unique to the website are a drawing of something the product gets for free, and those exact hex values will never appear in the app no matter how closely the two surfaces converge.
The typography is not shared at all
Colour at least half agrees. Type does not agree in the slightest.
font files font-family declarations
served website 3 3 families via CSS variables
Electron renderer 0 1
The website self-hosts two variable faces and pulls in a third:
const spaceGrotesk = localFont({ src: "./fonts/space-grotesk-latin.woff2", ... });
const dmSans = localFont({ src: "./fonts/dm-sans-latin.woff2", ... });
import { GeistMono } from "geist/font/mono";
which resolve through --font-display, --font-sans and --font-mono and really do render: the stylesheet applies each variable to real rules, so a visitor sees Space Grotesk in the headings and DM Sans in the body.
The app's entire typographic configuration is this, and there is not one font file anywhere in the bundle:
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI",
"Helvetica Neue", Arial, sans-serif;
So the headline a visitor reads on the website is Space Grotesk, and the same words in the app are San Francisco on a Mac and Segoe UI on Windows. Here, unlike the colours, I think the app is right and the mismatch is correct. A desktop app that imposes a brand typeface on its own chrome reads as a website in a window, which is the exact impression this product cannot afford: it is trying to be a small native utility that sits in the tray, not a web page that happens to be installed. Shipping zero font files is also the only typographic decision in the product that costs nothing to download.
What I would change
13 near-duplicate greys on the website merge into the shared ramp
24 app-only state tints keep, the website has no states
3 traffic lights keep, they are a drawing
0 shared font files keep, on purpose
The useful part of the exercise was that it separated drift from difference. Before counting I would have guessed the two surfaces had diverged generally. They have not: they share a ranked neutral ramp and the three status hues, and every real difference between them is traceable to something one surface has to do and the other does not. The one exception is thirteen greys that exist because nobody had a list.
The site is at notifio.app, where the three fake windows are on the homepage, and the real one comes from the download page. The download page itself carries one image and two inline SVGs, and not a single pixel of either palette beyond the shared ramp.
Top comments (0)