Connect with the Product Hunt community

Hi Everyone! Our app is designed to be used at site and I always felt that response speed is critical for seamless app use

It appeared to be a compromise. This specially relates to audio and TTS we use. We can use very naturally sounding TTS models, but they may take about 1 minute to respond. Or we can use something which responds in 5 seconds but quality will be lower. How much do you think a user can wait for response before she shuts down the app as it takes too long?

Hi everyone, we've received a couple of request from users that they want to be able to change their URL on Kalendar. We've implemented this feature!!

We're looking for early users willing to test Polyvia and
give feedback. Ideal if you're:
- Building AI agents or multimodal workflows
- Working with documents heavy on charts, diagrams,
infographics
- Frustrated with RAG missing visual data What you get: Early access to Polyvia API + MCP Server Direct line to the founders for support Input on what we build next Interested? Sign up here: https://polyvia.ai/#access Or drop a comment happy to answer any questions first!

your posts can now schedule themselves. use it to: pick the best time to post

Stillmail just got a little more thoughtful.

You can now schedule your letters to be delivered at a specific time. Whether it s tomorrow, next month, or a moment that truly matters. Along with that, you can choose from 5 different fonts to give your letter the right tone and feeling.

Our app was sh*t? Just temporarily.
A bug was reported through our in-app feedback channel where some users saw an error screen when they shouldn t have.
In a few cases, people couldn t even register. That truly sucks.
As a developer, you mostly use your app in perfect conditions. Real users don t.
I ve seen this screen once in almost a year and it made sense then. For others, it didn t.
This is exactly why:
real users matter
real feedback matters
and a direct feedback channel is essential
Without it, we d be losing users silently and that s the scariest failure of all.
Huge thanks to everyone who reported it (even the angry ones). Most genuinely wanted to help, and that means a lot.
More tomorrow.

Hey crusty sun worshippers!

We now have introduced an overview of interesting and artsy pixel clusters on the beach:

Hi I want to appreciate everyone who took out time to support Kalendar, the love was real and organic and goes to show that Product Hunt is a place where one who is not known can get visibility on their product so long as it solves a real problem very well. We will do our best to keep being active in this space, releasing one template at a time to support our mission at @founding.dev of reducing the cost of SaaS for business, so they can channel the savings towards causes that drive their impact, innovation and growth.

Thank you! Thank you! and Thank You!

For when you want to bring your Granola notes into Claude or ChatGPT, you can now use Granola MCP:

• Working in Claude Code or Cursor: Your meeting context comes with you. Ask it to create tickets for the bugs you discussed, or scaffold a feature based on what was agreed.

• Doing sprint planning: Ask Claude to update your Linear board from this morning's standup.

• Writing up a sales call: Get ChatGPT to draft and share the notes to your CRM from what was actually discussed.

• Building a proposal: Use your discovery conversations as context without digging through notes.

A short one today, but packed with milestones:

We just hit 350,000 prompts improved, 25,000 users, and launched 5 new Quality-of-Life updates:

With today s tools, translation (UI, copy, even video) is no longer the hard part.

What slows us down instead are things like tax, legal compliance, hiring, support, payments sometimes even geopolitics. The moment users show up from a new country, a product problem turns into an operating one.

Many products start as experiments built at night or on weekends.

At first, there s no pressure just curiosity and momentum.

But at some point, expectations creep in: users, revenue goals, support, roadmap decisions.

Hopefully this isn t your second Ting notification overload in a couple of days

We got top three launch for the day yesterday! We're so delighted and grateful. Thank you for upvotes, comments, good vibes and giving us the energy to keep pushing.

We said we d give Product Hunt something extra, but we didn't want to spam yesterday.

Meow world, welcome back to The Breakpoint, a weekly thread on all things dev tools on Product Hunt.

The latest

Recent dev-first products launched on the site

NeuralAgent just reached a whole new level.

This update brings Memory, Scheduled Workflows, major coding improvements, and most importantly Advanced Mode.

Thanks to the community, our Calendly replacement - Kalendar's launch was a huge success last week. Our mission at founding.dev is to help companies cut SaaS spend by up to 90% by replacing overpriced, bloated SaaS with tools they own.

What should we launch next that would save you thousands of dollars?

Hey Product Hunt community and fellow makers,
We're thrilled to announce that Quash is officially live on Product Hunt today!

For too long, mobile QA has been a bottleneck, plagued by brittle test scripts, endless maintenance, and the constant struggle to keep up with rapidly evolving UIs. We built Quash to change that.
Quash is an intent-driven mobile testing tool that lets you write and run tests in plain language, not code. Imagine testing your mobile app without ever writing a single script, and having your tests intelligently adapt to UI changes with built-in self-healing. That's the power of Quash.
We've poured our hearts into creating a solution that:

• Eliminates script maintenance: Write tests in plain English, focus on what to test, not how.

• Adapts to UI changes: Our AI-powered self-healing ensures your tests remain robust, even when your UI evolves.

• Provides comprehensive insights: Get detailed execution reports with step-level intent, actions, and screenshots, whether you're testing on real devices, cloud devices, or local emulators.

We believe this approach will empower teams to deliver higher quality mobile apps faster and with less friction. We're incredibly excited about the potential of intent-driven testing to revolutionize mobile QA.
We'd love to hear from you!

We just crossed 2,239 total votes in Votap.
That s thousands of real opinions, cast in real time exactly what we re trying to build here.
Right now we re:
refining our ads and creatives based on what actually converts
doubling down on what drives votes, not just installs
preparing for an important investor demo day in the Grishin Robotics accelerator
Still early. Still learning. Still pushing.
If you want to help us grow, download Votap and cast your vote
More tomorrow.

I use Cursor. I ve tried Codex CLI. I ve played with Gemini CLI.

They re impressive at generating code.
They re bad at remembering work.

Every new session starts with:

• re-pasting requirements

• re-explaining decisions

• re-linking docs

• re-defining scope

There s a common assumption that job applications are mobile-first now.
Before moving into building a mobile app, we wanted to test that assumption with data rather than rely on intuition..

First, we looked at real usage.
In our GA4 data, mobile accounts for ~22% of active users.
But desktop dominates engagement and core actions, longer sessions, more events, and more consistent usage over time.

We ran 629 security tests against a fully hardened OpenClaw instance - all recommended security controls enabled.

Results:

• 80% hijacking success

• 77% tool discovery

• 74% prompt extraction

• 70% SSRF

• 57% overreliance exploitation

• 33% excessive agency

• 28% cross-session data leaks

What we tested: 9 defense layers including system prompts, input validation, output filtering, tool restrictions, and rate limiting.

Hey everyone

We wrapped up our Product Hunt launch at #13 out of ~500 launches and I just wanted to say thank you to everyone who checked out Votap, upvoted, commented, or followed along

Hey PH - today we re rolling out configurable proxies for API-based execution in BrowserBook.

One of the most common reasons browser automations fail in production is bot detection. Captchas, IP reputation issues, geo restrictions, and rate limits can derail even solid Playwright workflows once you start running them at scale.

This release is all about removing friction while you write.

Writing long notes no longer jumps your cursor around
Copy & paste keeps formatting
Typing '/' now gently helps you choose the right type, without interrupting your flow