Small milestone today: The landing page for ASO Analytics is live. I’ve been building a native iPhone, iPad & Mac app to bring App Store analytics, subscriptions, markets, and keyword tracking into one place. The app is currently in review. Until then, I finally have somewhere to show what I’ve been working on: aso.guide Now comes the uncomfortable part for every developer: shipping it and finding users

Hey builders/founders Looking to connect with people building in: - Saas - Tech - Al Tools - Web Apps - Dev Tools Drop 👋 and let's connect

A product decision I’m making with ASO Analytics: changes matter more than snapshots. Knowing that your app ranks #24 for a keyword is useful. Knowing that it moved: #51 → #24 in 7 days is much more useful. Same data, completely different context. That’s how I want to approach the product: less “here’s your current ranking” more “here’s what changed, what might need attention, and where you’re making progress.” For analytics products, I think the delta is often more useful than the number itself.

What does your first App Store screenshot tell people they can do? new guide walks through a five-frame storyboard, clearer captions, and a practical checklist for your next screenshot set. Read the guide: aso.guide/blog/app-store-scr…

Your App Store name, subtitle, and keywords each have a job. A new guide walks through a before-and-after example, field limits, and where to make changes in App Store Connect. aso.guide/blog/app-store-met… #ASO #IndieDev

307 connections already, and the energy here is unmatched! Thank you to everyone who connected so far. I want to fill my feed with more builders, founders, indie hackers, and devs. If that’s you: - Drop a 👋 or your current stack in the replies - Follow anyone who likes your comment Let's connect, support each other's tech journeys, and win together. Drop your links below! 👇

ASO Analytics has been live for 4 days. Very early numbers: - 42 downloads - 168 App Store impressions - 51.2% product page conversion One thing already surprised me: the conversion rate is much higher than I expected. Now I want to understand whether that holds as impressions grow, and which parts of the product page are doing the most work. Still early, but this is exactly the kind of signal I wanted to start measuring.

Which apps compete with yours, and what can you learn from their listings? new ASO guide walks through competitor research with a comparison matrix and ideas to test Read the guide: aso.guide/blog/aso-competito… #ASO #IndieDev

Yesterday I launched ASO Analytics on the App Store. Today, the job changes. Before launch, most product decisions are based on assumptions: “What should I build?” “What will developers find useful?” “What belongs on the dashboard?” After launch, those assumptions can finally meet reality. My focus now is simple: Watch how the product gets used, find the friction, and improve what actually matters. Shipping isn’t the finish line. It’s when the useful information starts arriving.

ASO Analytics is now live on the App Store 🎉 I built it for indie developers who want one place to understand: - downloads & revenue - subscriptions & MRR - market performance - keyword rankings & analytics It started as a tool I wanted for myself. Now it’s finally out in the world. If you build iOS apps, I’d love to hear what analytics you wish were easier to understand. apps.apple.com/us/app/aso-an…

Your first App Store keyword list should start with user needs. Our new ASO Guide covers search intent, keyword evidence, and a practical worksheet for building a shortlist you can explain. aso.guide/blog/app-store-key…

This week I’m continuing to build ASO Analytics. The App Store Connect integration is working. Now I’m focusing on turning that data into something I’d actually want to check every day. The goal isn’t to build the dashboard with the most charts. It’s to answer a few important questions quickly: • How are downloads and revenue changing? • Which markets are driving growth? • What’s happening with subscriptions and MRR? • How are important keywords moving? Still early, but I like this constraint: Less reporting. More answers.

Building ASO Analytics is forcing me to think about what an indie developer actually needs from analytics. Not more charts. Better answers. I want to open one app and quickly understand: - Are downloads growing? - Which markets are driving them? - What’s happening with revenue and subscriptions? - How are the keywords I care about moving? The App Store Connect integration is already in place. Next: turning the raw data into something genuinely useful for making decisions. That’s what I’ll be working on this week

I’m building ASO Analytics because app data gets fragmented fast. App Store performance, revenue, subscriptions, markets, keywords each metric is useful on its own. But the interesting questions usually connect them: Which markets are growing? Which keywords are actually worth tracking? What changed when revenue moved? That’s the direction I’m exploring: one place to understand how an app is performing, not just another dashboard full of charts. Still very early. Building it for myself first.

Just published the first article on ASO Guide: What Is ASO? A Practical Guide for App Store Developers I wanted it to be useful for indie developers who know ASO matters, but aren’t sure what to work on first. It covers: - discovery vs conversion - metadata and screenshots - keyword visibility - App Store metrics - what to measure before making changes - a practical first ASO plan aso.guide/blog/what-is-aso/

I'm already halfway to 500 followers looking for more builders to connect with if you’re building SaaS, AI tools, mobile and internet products or just shipping random ideas if you’re building something, let’s connect 🤝

Update on my ASO Analytics The goal is to bring the metrics I actually care about as an indie app developer into one place: • downloads & revenue • MRR & subscriptions • performance by market • keyword tracking & analytics I already have the App Store Connect integration working Still early, and the scope will probably change as I build I’ll share the process here, including what works, what doesn’t, and how the product evolves

The biggest shift in how I build apps: I no longer start with “What should I build?” I start with: “Where are people already looking for a solution?” Find the pain. Find the distribution channel. Then build the smallest product that connects the two. Distribution before code.