Feature creep devours software.
Picture this: a sleek note-taker born in 2016, block-based magic that feels like Lego for your brain. Notion. By 2018, databases sneak in. Project management follows. AI arrives by 2023—like clockwork. 2024? Calendar. 2025? Email client. One hundred eighty features crammed into last year alone. And that desktop app? An Electron beast munching 200 MB on disk. We’re talking dental insurance next, right?
But here’s the thing—it’s not just Notion. This plague hits everyone. Jira, birthed in 2002 by Sydney engineers on a $10k credit card for bug tracking (named after Godzilla, no less). Fast-forward: it serves devs, DevOps, PMs, IT, HR, marketing via 3,000 plugins. Teams configure more than they create. Linear calls itself “the anti-Jira,” loads twice as fast. Sympathy for the marketing spin, sure.
Slack. 2014 team chat. By 2017, workspaces guzzle RAM—130 MB to 960 MB. 2019? 5 GB reports. Electron’s fault, each workspace its own bloated webview. They rewrote in 2019, halved memory. Still 200-500 MB disk for text. Text!
Why Does Notion’s Kitchen Sink Feel So Heavy?
Teams now idles better post-WebView2—1 GB idle. Progress. But “1 GB for chat”? Satire in 2005. Evernote? Started light, added scans, chats, socks (!). Bloated to 1 GB for four notes. Market king to ghost. Notion’s repeating it, faster.
iTunes: music player turned video/podcast/app/iCloud Frankenstein. Apple axed it 2019, split into three. WWDC roast included. Took 14 years.
Google? Killed 299 things. Reader’s death sparked riots—100k signatures. Feedly boomed.
Notion launched in 2016 as a note-taking app with a clever block-based editor. By 2018, it had databases and project management. By 2023, AI. By 2024, a calendar. By 2025, an email client.
That’s the original siren song. Seductive. Fatal.
Apple fumbled Save As in Lion—users revolted, downgraded OSes. Hid it behind four keys. Windows 11 stripped taskbar joys; GitHub hacks exploded. Reddit’s API greed nuked beloved clients—8,800 subs dark. Firefox torched XUL extensions overnight.
Feature creep. Two faces: bloat (performance killer) and overreach (user revolt). Same root? No kill switch. No discipline.
Look, I’m the guy who sees AI as the next platform quake—like electricity wiring homes, not just factories. But even I blink at Notion’s AI bolt-on amid the calendar-email frenzy. It’s like strapping a jet engine to a bicycle—thrilling crash incoming.
My hot take? This echoes the mainframe era. Monoliths ruled—IBM’s System/360 packed punch but choked on custom cruft. Minicomputers exploded modularity. Today? Apps ape mainframes. AI flips it: imagine composable agents summoning just the blocks you need. Notion but lightweight, on-demand. No 200 MB tax. Prediction: by 2027, AI-orchestrated “micro-apps” make bloat extinct. Notion pivots or perishes.
Short para. Boom.
And Slack’s RAM wars? Electron’s the villain—web tech in native drag. Teams escaped somewhat. But why rebuild when AI could proxy chats server-side, client featherweight? Wonder that.
Jira’s plugin hell? AI auto-configures workflows. No more config purgatory.
But companies hype velocity over velocity of value. Notion’s 180 updates? PR spin for “ship fast.” Reality: user fatigue. Evernote’s socks were the canary.
Will AI Finally Starve Feature Creep?
Yes—if we let it. Think agents as butlers, not hoarders. Pull email only when summoned. Calendar? Ephemeral. Notion’s block editor + AI smarts = dream. But they’re sprinting blind.
Google’s kills teach: users flock to lean alternatives. Feedly post-Reader. Linear vs Jira.
Reddit’s CEO meltdown? Audio proved the hubris. Apollo’s 1.5M users gone.
Firefox extensions? Ecosystem gutted.
Windows taskbar? Still half-broken.
Pattern clear. Bloat breeds backlash. Lean wins.
So, devs—ship surgically. Kill ruthlessly. AI’s your scalpel.
Envision: your IDE summons Notion blocks, Jira tickets, Slack pings without launching apps. Zero bloat. Platform shift.
One sentence wonder.
Notion, heed Evernote. Jira, feel Linear’s breath. Slack, remember 5 GB shame.
Future’s modular. AI-powered. Electric.
How Do You Spot Feature Creep in Your Stack?
RAM spikes. Config time > work time. Users hack workarounds. Petitions brew.
Measure disk. Time loads. Survey rage.
Then prune.
Apple did with iTunes. Microsoft half-assed Teams.
You can too.
🧬 Related Insights
- Read more: Blazor WASM, JS Rewrite, Blazor Again: The Rollercoaster of a 3D Chrome Extension
- Read more: RSAC 2026: Five Vendors Peddle AI Agent IDs, But Two Fortune 50 Screw-Ups Show It’s Useless Alone
Frequently Asked Questions
What is feature creep in software?
It’s when apps pile on unrelated features, bloating performance and confusing users—like Notion adding email to notes.
How to avoid feature creep as a developer?
Prioritize ruthlessly, measure resource use, kill unused features yearly, and lean on AI for modular add-ons.
Does Notion’s feature creep hurt performance?
Absolutely—Electron app at 200 MB disk, slower loads, mirroring Evernote’s downfall trajectory.
