App Store Connect for indie iOS developers.

What indie developers specifically struggle with

The stack of small App Store Connect annoyances is what eats your Friday afternoon. Individually none of them are a blocker. Collectively they are the reason a "quick metadata update" turns into two hours.

• The web UI is slow. Every click triggers a server round-trip. Switching between Distribution, App Information, and App Privacy is three full page loads. On a weak hotel wifi connection you can watch the spinner for longer than you spend typing.
• Per-locale editing is a form loop. If you support English, German, French, and Japanese, changing a single subtitle means opening the locale picker, selecting the locale, scrolling to subtitle, editing, saving, confirming, and repeating four times. There is no multi-locale diff view.
• Fastlane has a maintenance cost you did not sign up for. Updating a gem, fixing a Ruby version mismatch after a macOS upgrade, regenerating a match certificate — none of this ships features. For a solo dev, an afternoon fixing Fastlane is an afternoon not fixing the thing users emailed about.
• Release notes across locales go stale. You remember to write English What's New. You forget German. Apple lets you submit anyway, and your German users see English notes on a German-localised app. It looks unprofessional, and you catch it three days after release.
• Review-status refreshing. After submission, you keep reloading the Versions tab to see whether Apple has moved you from Waiting for Review to In Review. Over a 24-hour window that is a measurable amount of your attention.

How AppConsul helps indie developers

The promise is boring on purpose: do the App Store Connect work you were going to do anyway, but faster, in one window, and with fewer chances to forget something.

Every locale in a single editor

AppConsul's metadata screen shows every locale you support side by side. Type the subtitle into English, tab across to German, paste the translated value, tab to French. Save once. The same editor enforces Apple's per-locale limits live (30 for name and subtitle, 170 for promotional text, 4000 for description, 100 for keywords, 4000 for What's New). You can read more about how the character budgets work on the metadata character counter.

Screenshots pulled once, edited in place

The Store Assets screen imports the screenshots currently live in App Store Connect. You can reorder by drag, swap a single shot in one device class, and upload only the diff — not the full set. For the required iPhone 6.9", 6.5", iPad Pro 13", and iPad Pro 12.9" device classes this removes a huge amount of re-upload work. The screenshot size reference covers exact pixel dimensions.

Versions and review status as notifications

After you submit, AppConsul polls App Store Connect and fires a native macOS notification when the version moves to In Review, Pending Developer Release, or Ready for Sale. You get the update the moment it lands — no refreshing the web page between getting coffee and reading email.

Guided flows for the releases you do every few weeks

Guided Flows are opinionated walkthroughs for the operations that repeat: Publish First App Listing, Refresh Screenshots, Update Metadata, Generate Store Assets, Set Up TestFlight Beta. Each flow takes you through the right tabs in the right order so you do not submit with a missing privacy URL or an un-rated age rating.

Free tier covers one full app

If you only ship one app, AppConsul is free forever. Full metadata, screenshots, versions, app details, analytics, publish, guided flows, and command palette. You upgrade to Pro when you publish a second app or want IAP management, custom product pages, territories and pricing, or AI-assisted translation.

Recommended workflow for an indie release

This is the loop I'd use for a routine minor version update on a single app with three locales. It assumes the build is already in App Store Connect via Xcode Organizer or a CI uploader.

1. Open AppConsul → Apps view. Your app shows the last-sync time and the current live version. Click through.
2. Versions → Create new version. Set the marketing version number. AppConsul pulls the available builds from App Store Connect; pick the one you just uploaded.
3. Write What's New across all locales. One editor, three columns. Use the same bulleted format in each for consistency. If you bought Pro, click the translate button to draft the non-primary locales from English.
4. Refresh screenshots if the UI changed. Open Store Assets, reimport, replace only the shots that changed, upload diff.
5. Pre-flight check. AppConsul validates that metadata is filled, a build is attached, screenshots are present for each required device class, age rating is set, and the privacy URL resolves. Fix whatever it flags.
6. Submit. Click Submit for Review. Phased release and manual-release toggles are in the same panel.
7. Wait for notifications. Don't refresh the website. When macOS tells you the status changed, act on it.

For a first submission, the submit-app-store-without-rejections guide covers the extra App Details work (age rating questionnaire, category, privacy nutrition labels) that first-time reviewers flag most often.

Tools you'll use most

These companions to AppConsul are free and do not require an account:

• Metadata character counter — live UTF-16 counts for every App Store Connect field. Use it when drafting copy in a doc before pasting into AppConsul.
• Submission checklist — the pre-flight list in standalone form. Print it, tick boxes, submit confidently.
• Version and build number helper — explains CFBundleShortVersionString vs CFBundleVersion rules and catches combinations Apple will reject.

Frequently asked questions

Is AppConsul worth it if I only have one app?

Yes. The free tier supports one app with the full core workflow. You only pay for Pro when you publish a second app or need features like IAP management, custom product pages, territories and pricing, the store-asset generator, or AI translation.

Do I still need Fastlane?

Not for metadata, screenshots, versions, or submission. Many indies keep Fastlane for the narrow job of building and uploading IPAs from CI. If you ship from Xcode Organizer or Transporter, you probably do not need Fastlane at all.

How fast is a metadata update compared to the App Store Connect website?

A single-locale change is seconds either way. The difference scales with scope. Updating the same subtitle, keywords, and What's New across five locales is roughly one form per locale on the web. In AppConsul every locale is a column in the same editor — you tab across and save once.

Can I use my existing App Store Connect API key?

Yes. Any Team Key created at appstoreconnect.apple.com/access/integrations/api works. Paste the issuer ID, key ID, and downloaded .p8 file into AppConsul and it is stored in macOS Keychain. See the API key setup guide.

What if my app is React Native or Flutter?

Framework doesn't matter. AppConsul manages your App Store Connect listing and uploads — not your build. Your build still comes out of Xcode, EAS, Codemagic, or your pipeline.

Does AppConsul work for solo founders who aren't developers?

Yes, and we have a separate overview for solo founders that focuses on the non-engineering side of publishing an iOS app.