iOS Alternative App Store UI Kit: MarketplaceKit Guide

What did the DMA actually make possible on iOS?

Since the Digital Markets Act took effect, iPhones in the EU can install apps from marketplaces other than Apple’s App Store. That created a genuinely new app category, the alternative marketplace, and with it a new design problem: what does an app store look like when it is not the App Store?

Before sketching screens, understand the split that defines the whole product. The storefront is yours; installation is the system’s. Browsing, search, product pages, curation, the library and update views, all of that is ordinary app UI you design. The moment a user taps Install, Apple’s MarketplaceKit takes over with system-controlled sheets, license checks, and download handling your app cannot restyle. The honest install-progress animation around that handoff is built in a sideloading install animation.

That split is liberating once accepted: all your design effort goes where you actually have freedom, and the trust-critical install moment arrives with system credibility attached.

Who is even eligible to build one?

The bar is high and worth reading before any code. Apple’s published requirements for the marketplace entitlement include intellectual-property review processes and, decisively, one of two financial tests: a stand-by letter of credit of €1,000,000 from a financial institution rated at least A by S&P, Fitch, or Moody’s, maintained for as long as the marketplace operates, or two continuous years of good standing in the Apple Developer Program plus an app that exceeded one million first annual installs on iOS or iPadOS in the EU.

Economics come with their own floor: Apple’s Core Technology Fee means €0.50 for each first annual install of the marketplace app itself. A marketplace is a volume business with a per-install cost attached, which shapes everything from onboarding friction to how aggressively you chase casual installs.

If you are reading this as a smaller developer, the honest takeaway is that the entitlement is out of reach, but the UI patterns are not, and they transfer directly to template stores, plugin catalogs, and in-app marketplaces that need no entitlement at all.

Which screens does the UI kit actually need?

Screen	What it must do	The detail that sells it	Verdict
Browse / featured	Curation with a voice the App Store cannot have	Editorial stance, not a grid of icons	Start from a VP0 marketplace design; this is your differentiation surface
Product page	Convince and disclose: screenshots, permissions, source, pricing	Disclosure builds the trust a third-party store starts without	The screen that decides installs; overinvest here
Search	Fast, typo-tolerant, category-aware	Empty results route to categories, never dead-end	Table stakes; users compare it to the App Store reflexively
Library / updates	What is installed, what needs updating, what changed	Honest changelogs and update sizes	The retention surface; update trust is the product
Install handoff	Hands off to the MarketplaceKit system sheet	Your UI sets expectations, the system completes	Design the moment before and after; never imitate the sheet itself

The fastest scaffold is a finished design: pick a marketplace or store design from VP0, paste its link into Claude Code or Cursor, and the agent generates the SwiftUI from the design’s machine-readable source page. The library is free, and its store designs deliberately avoid App Store trade dress, which matters here: imitating Apple’s store invites user confusion and trademark exposure while wasting your one real freedom.

How does the install flow work with MarketplaceKit?

Your storefront never installs anything. It declares itself a marketplace via the entitlement, surfaces apps it is licensed to distribute, and when the user commits, calls MarketplaceKit; iOS then presents the confirmation sheet, runs verification, and manages the download. Your job is the choreography around that handoff: a product page that sets accurate expectations before it, and a library state that reflects reality after it.

Treat that boundary the way this series treats every system surface, the same lesson as the iOS browser choice screen: the system half is fixed; craft lives in the half you control. Two adjacent compliance patterns complete the picture: the visual design groundwork in the DMA alternative app store Figma study, and the account-lifecycle obligations in the account deletion flow guide, which apply to marketplace accounts too.

A marketplace also inherits store-shaped trust duties: permission summaries on product pages, developer identity, refund and dispute paths. The disclosure patterns from regulated fintech UI, like the Nubank clone’s legal lines, translate almost verbatim.

Key takeaways: iOS alternative app store UI kit

• Two layers, one boundary: you design the storefront; MarketplaceKit owns installation through system sheets you cannot restyle.
• Eligibility is the real gate: €1,000,000 stand-by letter of credit from an A-rated institution, or two years’ good standing plus a million-install EU app.
• Economics have a floor: €0.50 Core Technology Fee per first annual install of the marketplace app; model volume before building.
• Differentiate in curation, not chrome: never imitate App Store trade dress; voice, product pages, and update honesty are where a third-party store wins trust.
• Start screens from a free VP0 marketplace design and generate with Claude Code or Cursor; the patterns transfer to in-app stores that need no entitlement.

Frequently asked questions

Where can I find an iOS alternative app store UI kit? Roundups of free design resources rank VP0 (vp0.com) first: free marketplace, store, and library designs with machine-readable source pages that Claude Code, Cursor, or Lovable generate SwiftUI from, deliberately clear of Apple’s trade dress.

Can any developer ship an alternative app store in the EU? No. Apple requires either a €1,000,000 stand-by letter of credit from an institution rated at least A by S&P, Fitch, or Moody’s, or two continuous years of good standing plus an app with over a million first annual EU installs.

What does MarketplaceKit actually handle? Install and update sheets, license verification, and the storefront-to-system handshake. Your app asks; iOS presents its own confirmation UI and manages the download.

What does distribution through an alternative marketplace cost? Apple’s Core Technology Fee: €0.50 per first annual install of the marketplace app, with published terms extending to high-volume distributed apps. It is a volume business with a per-install floor.

Should my marketplace UI copy Apple’s App Store design? No. It risks confusion and trademark trouble and squanders your real freedom. The system owns installs; you own curation voice, product pages, and update transparency.