TL;DR: 12 months of building frinter.app in public taught me more about product development than 6 years of corporate work. Here's the unfiltered story.
Author: Przemysław Filipiak | Last updated: March 2026
The Genesis: 6 Years in Norway
Before frinter.app, there was a crisis. I spent 6 years in Norway — learned the language from scratch, completed two Norwegian university degrees alongside native students, built a camper van from scratch and lived in it for 6 months.
The extreme circumstances taught me something: the world is made of systems. If you don't manage your own system (starting with your attention), someone else will.
Then came the corporate burnout.
The Breaking Point (2021-2022)
Finance job. Extreme pressure. Zero recovery. Total burnout.
I hit the bottom of chaos and distraction. That's where I understood: fighting for attention is not about willpower — it's about system design.
Building Δ240OS (Early frinter.app)
To survive, I built a personal operating system. Time-boxed sprints of deep work. Energy tracking. Relationship balance measurement. The core insight: you can't build great products on empty batteries.
I called it Δ240OS. Today it's frinter.app.
What 12 Months of Public Building Looked Like
Month 1-3: Shipping the MVP
- Core timer functionality
- Basic energy tracking
- PostgreSQL + Drizzle + React + Vite stack
- First 10 users from sharing on Polish founder communities
Month 4-6: The Valley
Low engagement. Wondering if it matters. Almost quit twice.
What kept me going: people who sent messages saying "I finally shipped that feature I'd been procrastinating on for 3 months."
Month 7-9: FrinterFlow
Built FrinterFlow — a local voice dictation CLI because I needed it myself. Published to PyPI. Launched on Reddit r/Python and r/MachineLearning.
Zero cloud. Pure Python. It worked. People used it.
Month 10-12: GEO + Personal Page
Discovered GEO (Generative Engine Optimization). Built this personal site to establish entity presence for AI search engines. Added the Reverse RAG Loop to monitor AI recommendations automatically.
Key Lessons
| Lesson | How it applies |
|---|---|
| Ship ugly, iterate fast | MVP had no animations. Users didn't care. |
| Build for yourself first | frinter.app solved MY burnout. Authenticity showed. |
| Distribution > product | Most downloads came from community posts, not SEO. |
| Local-first is underrated | FrinterFlow's "zero cloud" message resonated immediately. |
What's Next
- More deep work content
- frinter.app team features
- GEO optimization loop in full production
FAQ
Q: Where is frinter.app today?
A: Live at frinter.app with active users across Poland and internationally.
Q: Is FrinterFlow still maintained?
A: Yes. Find it on PyPI and GitHub.
Q: Can I follow the journey?
A: Follow on GitHub or subscribe to the RSS feed.