Hacker Newsnew | past | comments | ask | show | jobs | submit | Angoleyus's commentslogin

Hey everyone!

I just pushed a series of updates to FlowDesk based on some great feedback I received over the last 24 hours. As a solo dev, I really appreciate everyone who took the time to poke around and point out where things could be better.

Here’s what I’ve improved:

Design Cleanup: Toned down the landing page UI. I’ve removed some of the excessive emojis and simplified the header styles to make it feel more professional and less cluttered. Pricing Transparency: Updated the pricing section to show the monthly equivalent for annual plans ($7.99/mo). It makes the 20% discount much easier to understand at a glance. Tighter Spacing: Adjusted the layout spacing (especially in the hero section) to make the page more compact and focused on the content. Copy Refinement: Removed some of the "marketing-heavy" claims and replaced them with straightforward facts about the privacy-first, client-side architecture. Technical Fixes: Fixed a layout shift bug in the features section, added smooth hover transitions, and finally added a proper favicon for browser tabs. Live Changelog: Added a permanent changelog section at the bottom of the site so you can track the status of new features and fixes as I ship them. Thanks again for the support and the honest feedback. It’s helping me make FlowDesk a much better tool for everyone.

Check it out live: flowdesk-ecru.vercel.app


I built FlowDesk because I wanted a lightweight freelancer command center that didn't require a backend, a database, or even a signup. It handles invoices, client management, and financial reports entirely in LocalStorage.

Technical bits:

100% Client-side: All PDF generation and state management happen on the device. Privacy as a Feature: Zero data is sent to servers. I used Vercel Serverless only for the Stripe signature verification. PWA: Fully functional offline via Service Workers. No-Signup Approach: I believe for a lot of solo-freelance work, a traditional account is overkill and a privacy risk. I'd love to hear your thoughts on building "backend-less" apps. Is LocalStorage enough for professional work, or is the risk of losing data too high for this use case?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: