Zubair Collier

Hey everyone!

Coming off our launch last week, we spent some time digging into our analytics for SoundGate and one metric really stood out: our onboarding drop-off rate is sitting at less than 1%.

When we originally sat down to design that first user interaction, we spent a massive amount of time debating and refining the experience. It is incredibly tempting to use onboarding as a data-gathering exercise, but we set a few strict rules for ourselves to prevent that:

• Zero Fluff: We audited every single step. If a question didn't directly improve the user's immediate experience in the app, we cut it.

• UX > Marketing: We had tough conversations about what data helps marketing versus what the user actually needs to get started. We kept the focus entirely on the user's momentum.

• Vibe is a Feature: We didn't just want a functional flow. We wanted to show off the musicality and tone of the app from the very first tap. Onboarding shouldn't feel like filling out a tax form - it should feel like the opening track of a great album.

The App Store shows downloads, revenue, crashes. Fine as a pulse check. Not enough if you care what people do inside the app: which paywall they hit, whether they finish a session, whether a feature even got used.

For Briskly I built a small event tracker and a private dashboard for that. It works. I m just not sure it s the smartest use of solo time, or if there s a simpler setup most people use.

Hey Product Hunt community,

With hundreds of products launching every single day, I ve been trying to understand the underlying architecture of homepage visibility and traffic distribution.

As a maker, when you launch a product, you often notice it doesn't always appear directly on the main featured feed for every visitor or on every device/browser.

This got me curious about how the platform balances fairness vs. algorithmic curation: