App Store Connect for React Native teams.

What React Native teams specifically struggle with

Cross-platform-by-default teams tend to optimise the build pipeline — Expo Application Services (EAS), Metro, Hermes — but the App Store Connect side stays the same click-heavy web forms it has always been. The friction is specifically around ownership: who on a JS-heavy team actually knows how to drive an iOS release?

• One person is the iOS bottleneck. Screenshot updates, metadata tweaks, privacy nutrition label changes, age rating declarations — they all queue up for the teammate who has Xcode installed and has seen the ASC website before.
• The "I don't do iOS" tax. A marketing hire who could perfectly well write release notes ends up filing a ticket for the iOS dev to copy their text into App Store Connect, because the ASC web UI mixes content fields with TestFlight distribution, capabilities, and other scary-looking developer controls.
• Builds land in App Store Connect and nobody notices. EAS finishes uploading, Apple finishes processing, and the build sits in "Prepare for Submission" until the iOS dev comes back from lunch and attaches it to a version.
• Screenshot specs are iOS-specific. iPhone 6.9", 6.5", iPad Pro 13", iPad Pro 12.9" — each has its own pixel size. Your design team knows the Android equivalents and has to re-learn the iOS ones every time.
• Age rating and privacy labels feel like legal homework. The questionnaires are specific to Apple and don't match what you filled out for Google Play. Every release you have a five-minute debate about whether "user interaction" means what it looks like.

How AppConsul helps React Native teams

A GUI that removes the iOS-knowledge requirement

AppConsul's interface is narrow on purpose. You see your apps, versions, metadata, screenshots, app details, analytics, and submit. You don't see provisioning profiles, signing certificates, or build settings — EAS handles those. A marketing hire or PM can open AppConsul and update What's New across locales without ever opening Xcode.

Works with EAS, Codemagic, Bitrise, and GitHub Actions

Your CI pipeline (EAS Submit, Codemagic, Bitrise, GitHub Actions with xcbeautify) uploads the IPA to App Store Connect. AppConsul picks up the processed build from App Store Connect's build pool and lets anyone on the team attach it to a new version. No CI reconfiguration, no extra credentials to manage.

Every locale in a single editor

If your RN app supports English, Spanish, Portuguese, and Japanese, each locale is a column in AppConsul's metadata editor. Subtitle, description, promotional text, What's New, keywords — all side by side, all with live UTF-16 counts that match Apple's limits (see the character counter).

Screenshot capture from a running simulator

Run the iOS simulator with your RN app, switch to AppConsul, and capture screenshots directly for the device classes Apple requires. No manual simctl screenshot + rename + re-upload loop. Dimensions for every device class are in the screenshot size reference.

Notifications so builds don't get stuck

When your build finishes processing in App Store Connect, AppConsul notifies macOS. When you submit for review, AppConsul walks you through Submitted → In Review → Pending Developer Release → Ready for Sale. No more builds sitting unattached for three days.

Pro unlocks IAP management and custom product pages

If your RN app monetises through subscriptions or one-off purchases, Pro's in-app purchase management lets you edit products from AppConsul. Custom product pages let you create variant listings for ad campaigns — different screenshots and promo text per campaign, without bouncing back to the web.

Recommended workflow for a React Native release

1. CI builds and uploads. EAS Submit, Codemagic, or your pipeline archives and uploads the iOS IPA.
2. AppConsul notifies the team that the build finished processing. Anyone can pick it up from here.
3. Create version. Versions → New version → pick the build from the build picker.
4. Metadata update. Write the English What's New, use Pro's AI translation (or a human translator) for the other locales. Save.
5. Screenshots. If the UI changed, run the simulator, capture through AppConsul, upload. If not, skip.
6. Pre-flight. AppConsul validates metadata, build attached, screenshots, age rating, privacy URL, privacy nutrition labels.
7. Submit. Review the App Details panel (age rating, category, privacy URL) if anything has changed. Submit.
8. Monitor via macOS notifications. Phased release and manual-release toggles are in the same panel you just submitted from.

Tools you'll use most

• Screenshot size reference — because your RN design team is constantly re-checking iPhone 6.9" and iPad Pro 13" dimensions.
• Submission checklist — shareable pre-flight checklist so the submitter-of-the-day doesn't miss anything.
• Metadata character counter — for drafting copy in a doc before pasting into AppConsul.

Frequently asked questions

Does AppConsul care what framework the app is built in?

No. It manages App Store Connect, not your build. React Native, Expo, or bare RN all work the same. Your build still comes from EAS, CI, or Xcode.

We ship through EAS Submit. Does AppConsul replace that?

EAS Submit handles archive-and-upload. AppConsul handles what happens after: versions, metadata, screenshots, app details, review submission, TestFlight groups. Many RN teams use EAS for builds and AppConsul for App Store Connect.

Do JS developers need to understand Xcode to use AppConsul?

No. Once someone with Xcode has generated the App Store Connect API key, anyone on the team can use AppConsul to push metadata, manage screenshots, or submit a version without opening Xcode.

How do we manage iOS separately from Android?

AppConsul is iOS-only by design. Google Play has its own tooling; trying to unify the two produces lowest-common-denominator UI. Keep Play Console open in a browser for Android, use AppConsul for iOS.

Can non-engineers use AppConsul?

Yes. PMs, marketing, localization can all work in AppConsul directly. The credential in Keychain is a Team Key, not a personal Apple ID — rotate it to revoke access.