On building a native Mac client for App Store Connect

App Store Connect, Apple’s web tool for shipping apps, is the web app that matters most in an indie iOS developer’s day. It’s where you manage metadata, push builds to TestFlight, respond to reviews, set pricing, file privacy declarations, and submit for review. Almost every studio I know spends an hour a day in it during ship weeks.

Underneath, it is a web app from 2014 that has piled on features for a decade. It works. On a long-haul flight, or in a tab next to fifteen others, it is also miserable.

I built AppMeta, a native Mac client, so I could stop being miserable.

The problem ASC has, specifically

In fairness, App Store Connect’s design constraints are not Apple’s fault. Apple manages the metadata for several million apps across two hundred regions in forty languages, with regulatory edge cases in every market. Building a great web tool on top of all that is hard, and the team behind ASC ships a lot.

What ASC isn’t optimised for is an indie developer with five to fifty apps shipping across twenty locales. The specific problems:

• Localised metadata editing is one locale at a time. Editing a description in fourteen languages means switching the locale dropdown fourteen times. There is no side-by-side view.
• Keyword fields are 100 characters per locale, with no cross-locale gap analysis. Indies find the same keyword waste again in every language because no tool points it out. (The rules for that field, and the folklore around it, now have their own post.)
• Review responses are a per-app web flow with no inbox. If you have ten apps, you have ten places to check.
• Version submission requires a multi-step flow with hidden state. “Did I save the export compliance? Did I tick advertising identifier? Did I attach the encryption form?” These have all bitten me. So has forgetting which fields only change with a new version.

None of these is catastrophic on its own. Together they are why I had a recurring “App Store Connect” calendar block on Friday afternoons for two years before I shipped AppMeta.

What does a native App Store Connect client actually change?

At its centre, AppMeta is a Mac client that talks directly to the App Store Connect REST API and shows your apps’ metadata side by side. It signs in with an API key you create yourself in App Store Connect; the key setup guide walks through that. It changes four things.

Side-by-side localised editing. Pick a field and every locale’s version of it is on one screen: the English description, then the German, French, Japanese, and Spanish ones below it, each editable in place. Or pick a locale and edit all of its fields together. Changed fields are marked, and you push when you’re ready. The hour-long localisation pass takes ten minutes.

Diff preview before push. Before anything is pushed, AppMeta shows exactly what will change against the current live metadata. I trust this feature more than I trust myself, because it caught a typo in five different localisations the day before I would have shipped them. After that happens to you once, you don’t ship without a diff preview again.

Cross-locale keyword analysis. AppMeta computes per-character keyword use across every locale and points out wasted space, duplicates, and gaps. I used to keep this in a spreadsheet by hand. Now it’s a panel in the app.

Reviews in a native list. Each app’s reviews, from every storefront, sit in one list you can sort by date or rating, one click away in the sidebar instead of behind ten slow page loads. Pick a review, type a response, send. The response still goes through ASC’s regulated channels, with Apple as the source of truth, but you never leave the Mac.

There’s also version submission, screenshot management, pricing changes, and a few smaller things. What matters more than the checklist is that every minute of friction the web tool adds compounds over a year of shipping.

Why a lifetime price, not a subscription

People ask me about this more than anything else about AppMeta, so here is the plain answer.

App Store Connect tooling is a developer tool, and developer tools have a long history of subscription pricing: JetBrains, Sketch, Figma, Linear. The market would happily pay $19.99 a month for a good ASC client. I considered it.

I shipped AppMeta as a one-time $29.99 purchase because subscriptions give a tool like this a specific bad incentive. Every month you have to ship enough perceived value to justify the next charge, and that pressure pushes the roadmap toward more features when it should go toward the right ones. AppMeta’s job is to be a fast, reliable native client, and features added to get through a renewal cycle would make it worse at that.

A one-time purchase imposes a different discipline. The tool has to be worth $29.99 once, and the next sale has to come from a new user who thinks so, not from a renewal charged to an existing one. Revenue comes in more slowly, and in exchange the design stays honest.

What AppMeta is not

AppMeta is not a build pipeline tool. It does not replace fastlane, Xcode Cloud, or your CI. It does not generate screenshots; that’s Mockly’s job. Revenue on the phone is AppMeta Pulse, the iPhone companion.

It is the native client for the metadata and review side of App Store Connect, the part you spend an hour a day in during ship weeks and the part that needed to stop being miserable.

The short version

If you’re an indie iOS or macOS developer shipping in multiple locales and you’ve spent a Friday afternoon flipping through the locale dropdown, AppMeta is the studio’s answer: $29.99, one time, lifetime. Demo mode is free if you want to look around before you buy.

If you’re not an indie developer, this has been twelve hundred words about a niche tool, and you’ve made it admirably far. Thanks for reading. The next post will be about chess.