Buffer API alternative: one prompt in, every network's post out

412 users asked. We finally shipped dark mode 🌑 But it took 3 weeks — because we rebuilt every single chart from scratch. The details nobody sees = the work that matters most. Drop a 🖤 if you wanted dark mode in your invoicing app #darkmode #saas #buildinpublic #productdesign #indiedev

Dark Mode is Live 🌑 | Why It Took 3 Weeks to Ship

Dark mode is finally live in our invoicing app — and 412 users asked for it before we built a single pixel. #darkmode What looks like a simple color switch was actually a full 3-week rebuild. Every chart, every data visualization, every graph had to be redesigned from the ground up to work in a dark environment. We weren't going to ship something that half-worked. In this video, we walk you through: — Why dark mode in a data-heavy app is way harder than it sounds — How we prioritized this based on real user requests — The chart redesign process, color contrast decisions, and accessibility checks — What we'd do differently next time If you're building a SaaS product or thinking about shipping dark mode yourself, this one's for you. The stuff users never see is usually the hardest work. #buildinpublic #saasdesign Timestamps: 0:00 — Why 412 people finally convinced us 1:30 — The chart problem nobody warned us about 4:00 — Our redesign process 7:20 — The final result

dark mode invoicing apphow to ship dark mode saasbuild in publicsaas product updateinvoicing app featuresdark mode chartsproduct design processsaas development behind the scenes

412 users asked for dark mode. We shipped it last week. Here's the part that surprised us: It took 3 weeks — not because dark mode is hard, but because we have charts. Every chart in our invoicing app had to be rebuilt from scratch. Colors that look clean on a white background? They're invisible or eye-straining on dark. Contrast ratios that pass accessibility standards in light mode? Fail completely in dark. So we didn't just flip a CSS variable and call it done. We redesigned every data visualization. Every axis label. Every tooltip. Every legend. Three weeks of work that most users will never consciously notice — and that's exactly the point. We track feature requests in a dead-simple spreadsheet. When dark mode crossed 400 votes, it jumped straight to the top of the queue. No roadmap committee. No prioritization framework. Just 412 real people saying the same thing. The lesson we keep relearning: Listening to users is easy to say and easy to fake. Actually doing it means sometimes rebuilding things you thought were finished. We think that's the job. If you're building a product right now — how do you decide when a feature request has earned its spot on the roadmap? #BuildInPublic #SaaS #ProductDevelopment