Reading up on Fizzy
12 deep · digging since dec 02, 25
- 37signals Isn't Smarter Than You, But They Are Different
37signals achieves clean code by keeping teams small, cutting scope, and hiring top engineers, a strategy most companies cannot adopt due to feature-driven revenue models.
- Fizzy Design Evolution: A Flipbook from Git
The article describes a technical process extracting Fizzy's daily git screenshots and scoring a flipbook video with Claude-composed music from the app's own audio samples.
- New product mode
Basecamp launched Fizzy, an open-source Kanban app, and describes their 'new product mode' approach using Shape Up with more flexibility for rapid experimentation.
- Vanilla CSS is all you need
37signals builds complex web apps with vanilla CSS, no build tools, proving modern CSS features are sufficient for production.
Takes
The original plan for Fizzy was to ship the SaaS version with one sqlite database per customer. That didn't end up happening, but we built all the Rails infrastructure needed to make it possible. Mike goes through it all here: https://t.co/f285jYyYcc
@dhh
"...what I noticed within seconds of trying Fizzy was the absence of overwhelming menus, buried options, and integrations I never asked for. At the same time, I was struck by the presence of a distinctive design and sense of whimsy that’s largely faded from the greater software…
@jasonfried
CSRF token headaches in Rails will be a thing of the past thanks to Rosa. She first tested the solution based on Sec-Fetch-Site header in Fizzy (1), and then upstreamed to Rails (2) 🎉(1) https://t.co/jWVDhgCPZQ(2) https://t.co/yfCDyWR1Ko
@jorgemanru
As promised: a video talking about how we architect Rails apps and Fizzy. Includes thoughts on Domain Driven Design, service objects, callbacks, and concerns.I will record more of these, but probably not as long! pic.twitter.com/3rMDe7civw
@jorgemanru
Rob continues to kill it with his Fizzy demos. He's showing the potential better than we are! https://t.co/J6vvujk0TA
@jasonfried
34-minute video walkthrough and rundown of the Fizzy codebase by @BeautifulRubyHQ.https://t.co/T6EaY5tGPN
@jasonfried
Unlike Campfire, where we shared a zero-history copy of the codebase, Fizzy's public codebase has the entire life of the product development cycle out in the open. 1,792 pull requests of historical fun and insight into how we make things at 37signals! https://t.co/b0PrQBfJGC
@dhh
INTRODUCING FIZZYHave you noticed that every issue and idea tracking tool you loved slowly morphed into boring, sluggish, corporate bloatware?Trello put on 40 pounds of cruft. Jira started charging by the migraine. Asana tried to become everything to everyone. GitHub Issues… pic.twitter.com/7cGxaWA8kd
@jasonfried