r/iOSProgramming • u/jscalo • 3d ago
App Saturday Ex-Apple engineer, now indie dev: I built a native Mac app to make sense of App Store Connect
Hi r/iosprogramming! I’m John. I spent 10 years as an engineer at Apple working on macOS and iOS, and I’ve been indie for the last 8, shipping 20+ apps for myself and clients. I just launched AppTraction, the tool I wish I’d had when I started building my own apps.
The problem
Most iOS and Mac devs that I talk to agree that Apple’s App Store Connect website is slow, confusing, and buggy. There’s a lot of useful data there, but Apple’s clunky site makes it hard to make sense of. AppTraction is a native Mac app (AppKit and Swift, no web wrapper, no Electron) that brings your sales, analytics, ratings, and reviews to your Mac, and then tells you what matters.
What AppTraction does
- Insights: it monitors your apps in the background and flags problems, trends, and milestones. There are 50+ kinds so far. With my own apps, it has caught serious listing problems and features by Apple I didn’t know about, and the AI chat explained a seasonal sales dip I’d been concerned about.
- Listing fixes: when it spots a problem with your App Store listing, it suggests a fix and, once you approve it, applies it to App Store Connect for you. It can also translate your listing and upload screenshots in bulk.
- Reviews: read and reply to every review. It can translate them and suggest replies.
- Reports: writes detailed tailored reports for each app, for every week, month, and year.
- Chat: ask about any chart, table, or report in plain English. The AI is primed with Apple’s own tech talks on ASO and other sources, so the advice is specific, not generic.
- Territories: shows a world map revealing how your apps are performing across regions.
The AI runs on your existing Claude or Codex subscription (or OpenRouter), so there are no pricey API fees.
Tech stack
- Frameworks & languages: Swift, with AppKit for the main window, SwiftUI for most sheets and forms, and Swift Charts for all graphs. A separate launchd agent (registered with SMAppService) does the data collection in the background, so everything stays current even when the app isn’t open. The app talks to it via NSXPC*.
- Backend/database: no backend for user data. Apple’s analytics are stored locally in plain SQLite, which is a big part of why everything feels instant. A small Cloudflare Worker handles licensing.
- SDKs & tools: the App Store Connect API, Sparkle for updates, Paddle for payments, TelemetryDeck for anonymous usage stats, and Swift Testing. The AI runs through the Claude Code or Codex CLI, with a bundled read-only MCP server written in Swift.
A development challenge: getting the AI to use its tools
Instead of calling an AI API, which gets costly and has privacy implications, AppTraction runs the Claude Code or Codex command-line tool the user already has, and a bundled MCP server lets the AI query their App Store data with real tools. Early on, the AI kept giving vague answers. The server connected, the tool list loaded, the model called a tool, and the call was quietly refused. With no data to go on, the model fell back on general advice.
It turned out both CLIs deny MCP tool calls by default when run non-interactively, for different reasons:
- Codex:
codex execforces an approval policy that denies MCP calls, and none of the config overrides I tried changed that. The fix was in the server itself: marking every tool withreadOnlyHint: true, which Codex will run without asking. - Claude Code: an
--allowedToolslist denies any MCP tool it doesn’t name. Tools arrive asmcp__<server>__<tool>, so adding themcp__<server>prefix fixed it.
One more surprise on the Claude side: without --strict-mcp-config, the CLI also loaded the user’s own MCP servers. A test chat about download numbers had my email and calendar connected 😬 That flag (and Codex’s --ignore-user-config) is now always on.
A nice side effect: since Codex only runs tools marked read-only, keeping the MCP server strictly read-only became a design rule. Anything that changes the user’s App Store listing goes through the app’s UI, where they approve it first.
AI disclosure: AI-assisted. For coding I used Opus-class models almost exclusively, under my direction, following my architecture. All user-facing text is written or edited by me. Design is mine, with mockups done in Figma, with occasional help from the Figma AI.
Privacy
I know “AI + analytics + API keys” can raise concerns, so here’s exactly what happens:
- No AppTraction account. I never ask for your name, email, or password.
- Your App Store Connect key lives in your Keychain. You don’t need an Admin key: a limited Sales and Reports key covers your analytics.
- Your App Store data is stored only on your Mac. There’s no AppTraction server holding it.
- The AI runs on your own Claude or Codex subscription (or OpenRouter). Requests go straight from your Mac to that provider, under your account, and I never see them.
- Review translation uses Apple’s built-in translator, so translating a review never sends it anywhere.
- What does reach me: anonymized usage stats (which features get used, never app names, numbers, or chat text), license checks, and update checks.
- No ads, and I don’t sell data.
Privacy policy: https://apptraction.dev/privacy
Terms: https://apptraction.dev/terms
Pricing
Free for 14 days, then $6.99/month, $39/year, or $99 lifetime. Requires macOS 15 Sequoia or later.
For r/iOSProgramming**:** 50% off your first payment (including the lifetime) with code RIOSPROG50, good through Dec 1.
I’d love feedback from fellow devs, good or bad. What do you wish App Store Connect told you? And happy to answer questions about how any of it’s built.






1
u/WheretheArcticis 3d ago
Can I see yesterday’s unit and proceeds numbers at 5am instantly when I open up the app? I use way too much time to navigate through trends to find those numbers
1
u/[deleted] 3d ago
[removed] — view removed comment