Praneet Brar

"A completed trip is not proof of payment" is a good rule to write down. For the authorise-now, capture-later case with bookings made weeks ahead, do you re-authorise before pickup, or capture a different way once the roughly seven-day authorisation window runs out?

Interesting that Product Hunt sent a handful of people while study-group organizers sharing links in Teams and LINE WORKS drove 65 visitors. Did you find a way to tell those shared-link visits apart from the preview-bot ones, or is that still a rough estimate?

The private-window check with a spare Google account is the part I'd have skipped. Have you ever caught a closed track that looked fine in Play Console but wouldn't open for an outside account, and what turned out to be the cause?

The two matching signals plus a log is the part I was missing. Case by case is exactly where this goes wrong, because whoever is on support that day ends up being the policy. The other-admin check for team accounts is a good one too, cheap and hard to fake. I'm going to write the checklist down before the next one of these lands.

Separating 'confirmed' from 'we observed it on one account' is a nice honest touch for a public board. Since the rule-change alerts are the quieter, more expensive ones, how do you actually detect a rule change, by reading source posts by hand or something automated?

Treating 'not in the top 100' as a data point instead of a missing row is a detail most trackers get wrong. For the review buckets in step 3, which one has ended up driving your next update most often, crashes or missing features?

The line about the urge to launch cooling off while you fiddle with layout and fonts is painfully true. When you're writing a static page now, how do you decide the offer is proven enough to justify starting the real app?

Good catch on the proration, that's the kind of leftover that creates the next confused email. I hadn't thought about the cancel step leaving a credit or small invoice behind. When you cancel the extra subscription, do you also refund the duplicate charge in the same sitting, or wait to see what the final invoice looks like first?

Presence first then shape at every level makes sense, that's where the quiet pass hides. A few extra lines per test is a cheap price. Do you wrap that pair in a small helper so you don't repeat it, or do you just write it out each time?

The point that a listing can disappear if the badge comes off in a redesign is easy to miss. Putting a 'badge must stay' note in the tracker is a smart fix. Once a few of the live listings have been up for a month, which signal will you use to decide they were worth it, visits or signups?