@Wispr Flow launched on Product Hunt back in 2024. Since then it has become one of those tools that quietly sticks. It's the AI dictation tool a bunch of us here use day to day (yes, there are still a few people committed to typing everything out). It works anywhere on your Mac or PC, so you can just talk and have clean text land wherever your cursor is.

For the next three days, it is showing up on the leaderboard in a different way. From April 14 to 16, you can upvote and comment on Product Hunt using Wispr Flow directly. If you use dictation, those upvotes and comments will carry a bit more weight. Try it out by clicking the Wispr Flow unit on the Leaderboard and telling it to upvote a product name

Hey Product Hunt,

I'm Adrin, co-founder of Oculi Medical. We're building Kim, a personal AI health assistant.

Kim connects to your wearables and blood labs to deliver personalized insights. Ask any health question and Kim answers backed by your data and medical research. All your health data lives in one place, presented in a way that's actually easy to understand.

Kim also tracks calories, scans food products, and tells you what's healthy or not based on your personal data. Kim suggests supplements based on your data along with research. Run experiments to discover which supplements work for your body. The more you use it, the smarter it gets.

For the first year of building Murror, we optimized for the same metrics every other app optimizes for: daily active users, session length, screens per visit. The dashboard looked healthy. Usage was growing. We felt good about it.

But something was off. Our most engaged users were not our happiest users. People who spent the most time in the app were often the ones who left the harshest feedback. Meanwhile, users who opened the app twice a week for five minutes were writing us emails about how it changed how they handle difficult conversations.

I've been building my app for 8 months now, and i ended up having 5 repositories

• nextjs app

• databases

• customer facing API

• node-sdk that wraps the api

• react-sdk, for both reusing shared component and customer facing components

So i thought, it's gonna be great if i create a mono repo with submodules. But it was terrible. I realized that turborepo does not like external packages, and as i tried to reuse my own customer facing libs, the DX became terrible. It was very time consuming to ship a feature. Even when i wanted to use Codex or Cursor 3, it was not able to show git diff properly, also i was not able to use Cursor's cloud agents properly to ship complex features.

The meeting paradox

The async revolution was supposed to kill meetings, but it did the opposite. Since 2020, weekly meetings have increased 153%, despite every company adopting Loom, Slack, Notion, and a dozen other async tools. The tools multiplied, the meetings stayed. Something structural is broken.

Hey everyone! Just shipped v0.10.17 here's what's new:

- Boards New /boards slash command with node types, collapsible groups, and node notes

- Terminal Drag-to-Split Drag to split and unsplit terminal tabs

- Dark Mode & Themes Refined surface system and improved colors

Let me start from the creator s perspective:
I personally don t have a product (apart from hiring people for creative work or offering personal consultations).

But as a creator, I constantly share content, insights, and information, value that helps me build trust (for free). Based on that perceived expertise, people eventually decide to work with me (a paid service).