App Store Connect 2.0 has been rolling out to developer accounts over the last few weeks, and beneath the cosmetic refresh sits a real shift in what Apple expects you to do with your store presence. There's a new marketing asset generator that produces share-ready images for product launches, version updates, and feature placements. There are eleven new languages for promotional content that meaningfully change the math for anyone targeting India, Sri Lanka, or Slovenia. And the underlying flow for managing screenshots, custom product pages, and localizations has been redesigned around a model that assumes you'll be promoting your app outside the App Store, not just inside it.
This guide walks through what's actually changed in App Store Connect 2.0, which features are worth your time as an indie developer, and which ones are window dressing that won't move the needle. It also covers the practical workflow for getting marketing assets out of the new system and into the channels that drive installs.
What's actually new in the 2.0 release#
The headline change is the marketing asset generator. App Store Connect now includes a dedicated section for creating shareable images that promote your app outside the App Store — think social media announcements for a new feature, version update tiles for your changelog, or "featured on the App Store" badges when Apple gives you a placement on the Today tab. Apple generates these from your app's existing metadata: icon, screenshots, name, description, and any feature graphics you've uploaded.
The second change is the language expansion. Promotional content — which includes the marketing assets, custom product pages, and the in-store text that appears in App Store Today features — now supports eleven additional languages: Bangla, Gujarati, Kannada, Malayalam, Marathi, Odia, Punjabi, Slovenian, Tamil, Telugu, and Urdu. Nine of those eleven are Indian subcontinent languages, which tells you exactly where Apple expects the next wave of App Store growth to come from.
The third change is structural. The screenshot and metadata management screens have been redesigned around a "version" and "locale" axis, which makes it easier to manage many localizations at once but harder to make targeted changes to a single locale without affecting others. If you're used to the App Store Connect 1.x flow where each language was a separate set of forms, the new model takes some adjustment.
The marketing asset generator, in practice#
The asset generator lives under a new "Promote" tab in App Store Connect, alongside the existing app version and pricing tabs. Open it and you'll see three asset categories:
Launch assets. Designed for announcing a new app or major version. The generator pulls your icon, primary screenshot, and short description, and renders them into a square or vertical card sized for Instagram, X, LinkedIn, and Threads. You pick a layout, an accent color from your icon's palette, and a headline.
Update assets. Designed for promoting a version update or new feature. The generator surfaces your release notes and lets you select a feature to highlight. The output is a tile-style image with the feature name, a one-sentence description, and your app icon.
Featured assets. Generated automatically when your app gets an editorial placement on the Today tab. Apple notifies you of the placement and produces a "Featured on the App Store" image you can share to your own channels — something Apple has historically been protective of and is now actively encouraging.
The generator is opinionated. You don't get pixel-level control over the layout or typography; you pick from a set of templates Apple has designed. That's a deliberate choice — Apple wants the assets to be consistently branded so they're recognizable as App Store-originated content when they show up in social feeds.
What the generator is good for, and what it's not#
The generator is fast. If you've been hand-rolling launch graphics in Figma or Canva for every release, the time savings on routine update announcements are real — five minutes versus an hour, and the output is consistent across releases.
It's also a useful baseline for indie developers without design skills. The templates are clean, the typography is professional, and the asset will look credible next to a tile from a major publisher.
What the generator is not good for: anything that needs to communicate beyond "this app exists and looks polished." It cannot:
- Articulate a specific value prop in copy you control. The headline character limits are tight and the templates favor app name over feature description.
- Localize beyond the eleven new languages plus the existing thirty-some App Store languages. If you target a market Apple doesn't, you're back to your own tools.
- Adapt to platform-specific aspect ratios beyond what Apple ships. TikTok-style vertical video isn't generated; LinkedIn carousel formats aren't either.
- Pull from anything outside your App Store metadata. If your strongest marketing copy lives in your launch press release, you'll be retyping it.
For indie developers shipping frequent updates, the practical use is: let the generator handle routine version announcements, keep custom assets for launch moments and large features.
The eleven new languages and what they actually unlock#
The language expansion is the most underrated change in 2.0. Apple has supported app metadata in roughly forty languages for years, but promotional content — the high-conversion surfaces like custom product pages, in-app event listings, and the new marketing assets — was limited to a smaller subset. The eleven additions close most of the South Asian gap and add Slovenian for the EU.
The strategic implication for indie developers: India has been a high-download, low-revenue market for the App Store for a decade, but the revenue side has been climbing fast as the iOS install base in India grew. Indie developers who localize promotional content for Tamil, Telugu, Bangla, Marathi, and Gujarati now have access to the same conversion-optimized surfaces (custom product pages, event listings, marketing assets) that English-language listings have. That changes the unit economics of localization for any app with an addressable market in India.
The cost of localization has also dropped meaningfully because of LLM-assisted translation. Hand-localizing eleven new languages was a serious investment two years ago. Today it's a few API calls, plus a native-speaker review pass.
The redesigned screenshot and metadata flow#
The screenshot management redesign is where most indie developers will feel friction. The 1.x flow was a separate page per locale: you'd click into "English (U.S.)," upload your screenshots, write your description, and save. Each locale was effectively its own form.
The 2.0 flow is matrix-style. You see a grid of locales versus assets (screenshots, descriptions, keywords, promotional text), and you edit cells. The intent is to make bulk operations easier — uploading the same screenshots across thirty languages, copying English text to all locales as a starting point — and it succeeds at that.
The cost is that targeted edits are harder. If you want to change just the German subtitle without touching anything else, the new UI requires more clicks and exposes you to the risk of accidentally overwriting another field. The undo state is per-cell, not per-page, so a stray paste can ripple in ways the old flow never let it.
For indie developers managing one or two locales, the new flow is fine. For agencies or developers managing fifteen-plus locales, the matrix is a real productivity win, but only if you build a workflow around it that's deliberate about which cells you're editing.
Practical workflow: getting marketing assets out the door#
Here's the workflow I'd recommend for an indie developer using App Store Connect 2.0 for the next release:
First, before opening the generator, write your release notes in plain language and decide on the one feature you want to highlight. The generator pulls from release notes; if those are vague, the output will be vague.
Second, generate update assets in the Promote tab for each major locale you support. The generator is fast enough that creating a set of fifteen localized assets in twenty minutes is realistic — much faster than the old hand-design flow.
Third, pull the assets into a queue for posting. App Store Connect 2.0 doesn't schedule posts; it generates assets you then post elsewhere. If you have a social scheduler (Buffer, Hootsuite, your own tool), upload the assets there and schedule.
Fourth, monitor the App Store Today tab for editorial placements. If you get featured, the Featured asset is generated automatically and pushed to your account. Use it — featured placements drive a meaningful spike, and a "featured on the App Store" image in your social feed extends the spike beyond the placement window.
Fifth, after the release lands, run an analytics check in App Store Connect's Analytics tab to see whether the promotional assets drove product page traffic. The generator doesn't have built-in attribution, but the timestamps line up well enough that you can see lift on the days you posted.
What this means for indie developers#
App Store Connect 2.0 is Apple acknowledging that the App Store is no longer a destination users come to on their own. Discovery has fragmented across social, search, AI assistants, and direct links from creator content. The marketing asset generator is Apple's way of saying: we'll help you promote your app off-store, because we know that's where the install pipeline starts now.
For indie developers, the practical reads are:
The generator is a real time-saver for routine release announcements. Use it.
The eleven new languages open up promotional surfaces in markets where indie developers historically couldn't compete on conversion. Localize promotional content, not just metadata.
The new flow assumes you're treating store presence as a marketing channel, not just a submission target. Apps that lean into that — fresh promotional assets per release, localized custom product pages, regular in-app event listings — will out-discover apps that treat App Store Connect as the place you upload a build and walk away.
App Store Connect 2.0 is more capable than 1.x. Whether it makes you competitive depends on whether you use the new surfaces.
Where Stora fits#
Stora's screenshot and store-listing engine pre-dates App Store Connect 2.0's marketing asset generator and is doing related but different work. The generator produces social-ready promotional images from your existing App Store metadata. Stora's screenshot factory produces the App Store screenshots themselves — captured in the cloud, framed in device chrome, localized across every supported language, and pushed to App Store Connect via the API. The two stack rather than overlap: Stora handles the assets that show up on your product page, the generator handles the assets that show up in your social feed.
Stora's localization automation is the more direct fit with the eleven new languages. Pushing promotional content into Bangla, Tamil, Marathi, and the rest is exactly the kind of repeated work Stora is built for — generate the localized copy, run it through review, push to App Store Connect. The old workflow of doing this by hand is what App Store Connect 2.0 is retiring, and tools like Stora are how you retire it without burning a sprint.
If you've held off on localizing because the asset volume looked like a project, the math has changed. Apple gave you the surface; the rest is execution.