in 
p/general
p/generalWhat are some overpriced SaaS tools packed with features you don’t need but still have to pay for?
Adana Marukhyan:@farrukh_butt1 What PM tool do you use? can you please tell which layer is essential for you, and which are just exist without using them?
in 
p/introduce-yourself
p/introduce-yourselfStudent founder from India — building dev tools for AI products
Aryan Jambholkar:@rianbrob Sounds exciting, looking forward to it! Let me know when you launch — happy to support. 🚀
in 
p/livesyncdesk
p/livesyncdeskLiveSyncDesk temporarily tackled the panic situation and saved the Audit.
Raaguttam :LiveSyncDesk is a solo developer project. In very early stage. Free to use Tool. Opens instantly on Browsers. It basically for moments where two people are trying to explain something visually — and screenshots or async screens views just break the flow. Try it now and tell me your experience.
in p/general
p/generalI maintain 20+ open-source projects across 4 ecosystems. Should I have focused on just one?
Giovambattista Fazioli:@julia_zakharova2 Great question — these are all side projects. My full-time job is Lead Developer, where I work with React, TypeScript, and Go. The open-source work happens in evenings and weekends, and the honest answer is: the time distribution is very uneven. Mantine Extensions get the most consistent time — maybe 5-6 hours/week. Each component is self-contained, so I can ship one in a weekend and forget about it until someone opens an issue. FinderGit goes in bursts. Some weekends I’ll spend 10+ hours on a feature (like the AI commit messages). Then nothing for two weeks. SwiftUI work requires focus blocks that are hard to find on weekdays. WP Bones is mostly maintenance now — maybe 2-3 hours/week. The framework is mature, so it’s bug fixes, dependency updates, and answering questions on Discord. octoscope is the lightest — maybe 1-2 hours/week. Go compiles fast, the scope is small, and the codebase is simple enough that I can pick it up after a month and still understand everything. Total: roughly 10-15 hours/week on open source, depending on the week. Some weeks it’s 20, some weeks it’s 3. The key is that none of these projects need me every day — they’re designed to survive my absence. What about you — do you work on anything outside your main job?
in 
p/problemhunt
p/problemhuntHi builders! 👋 It’s Saturday. What’s your way to relax and recharge?
Terrence Wang:@gostroverhov I like mystery film a lot, just watched Shutter Island again over the weekend, love Leonardo’ performance!
in p/general
p/generalStop waiting for users to explain themselves. They never will.
Vladislav Prozorovskiy:@jonayed_tanjim Thanks. Very interesting! Putting more weight on post-activation churn does seem logical! Were you able to tell whether the feedback coming from those users was actionable or not?
in 
p/mindbloom-smarter-journaling-with-ai
p/mindbloom-smarter-journaling-with-aiWhy do most people quit journaling after a few days?
luo he:Hard to stay consistent is the real killer. I'd love something that just asks me one question a day instead of expecting paragraphs of reflection. The blank page is intimidating.
in p/general
p/generalThe New Pre-Seed: Harder to Get In, More Reward if You Do (with Julia Yu)
Sandra Jirongo:The links to the article appear to be broken
in 
p/self-promotion
p/self-promotionI built an App for Cost conscious and Style conscious people
Raaj Chitnis:@rianbrob Thanks a lot, really appreciate it! The Sponge sounds cool - I’ll check it out and follow your PH launch. All the best!
in p/general
p/generalWhat are you building, and what does your stack look like?
SLetras:Hey, this is a really interesting area to research. As a solo builder, I try to keep the stack as simple and reliable as possible so I can focus more on the product itself. For authentication, I usually go with ready-made solutions like Firebase Auth or Supabase since they save a lot of time and handle edge cases well. For billing, Stripe is pretty much my go-to because of its flexibility and solid documentation. Permissions are kept lightweight, mostly role-based access depending on the feature set, nothing overly complex unless the product really needs it. Right now I’m working on a small web tool around creative text generation, similar to letras bonitas, where simplicity and speed matter more than heavy architecture. So I’ve leaned towards a minimal backend and more client-side logic. Happy to share more details if that helps your research.