Watch-only app? You might be marketing in the dark (until you ship an iOS companion)

Original article (source): Ravi Shankar - “I Marketed My App for 18 Months Without Knowing If It Worked” (Feb 21, 2026)

• https://www.rshankar.com/watch-app-analytics-invisible/

What happened (and why it matters)

Ravi shipped a Watch-only app (ChantFlow) and spent 18 months with basically one metric: sales. He did real marketing pushes (blog, Reddit, social), but couldn’t connect any activity to outcomes.

Then he shipped an iOS companion app. Within a day, App Store Connect analytics “came alive”: impressions, product page views, conversion rate, sources, and territories.

The kicker: the data appeared to be backfilled all the way to the original launch date. Apple had been collecting it, but it wasn’t surfaced in the dashboard until an iOS app existed.

The practical insight

If you have a Watch-only app, you may be missing the exact signals you’d normally use to steer:

• which markets are responding
• whether you’re getting Browse vs Search discovery
• whether a marketing push increased product page views (even if installs didn’t)
• whether your store assets (screenshots) deserve more attention than your keyword list

In Ravi’s case, once the data was visible, he learned that:

• the spike he’d suspected during a marketing month was real
• his strongest market was India (and a few diaspora-heavy markets), which should have changed his messaging and distribution choices
• a large share of downloads came from App Store Browse, not Search, implying store visuals and category context mattered a lot

What to do if this is you (tiny checklist)

1. Ship a minimal iOS companion if you’re Watch-first or Watch-only.
   • It doesn’t need to be feature-complete. A settings screen or basic dashboard may be enough to unlock visibility.
2. In App Store Connect, look at:
   • Sources (Browse vs Search)
   • Territories (where momentum actually is)
   • Product page views around any marketing activity
3. If Browse is doing heavy lifting, prioritise:
   • first-3 screenshot clarity
   • messaging that matches category browsing intent (not just “keyword intent”)

My editorial take

This is a good reminder that “measurement” isn’t only about attribution tooling. Sometimes the first win is just making sure the platform is actually showing you the built-in data.

If you’re building for Watch (or any edge-case store surface), add “analytics visibility” to your launch checklist, not as a nice-to-have, but as a prerequisite for learning.

Read the original: https://www.rshankar.com/watch-app-analytics-invisible/