Storeboard/For agencies & freelancers

App Store listings for agencies & freelancers

Shipping one app's store page is a task. Shipping twelve clients' store pages is a different problem — with two risks that only show up when you work at that volume.

Last updated 16 July 2026

Risk one: your clients look like a reskin factory

This is the one that costs real money, and almost nobody sees it coming.

Guideline 4.3 exists to stop people mass-producing near-identical apps. It's aimed at template factories — one codebase, forty icons, forty listings. Now describe a typical agency: a shared internal framework, a house design system, the same screenshot template applied across clients, and sometimes several apps under one developer account.

From App Review's side of the glass, those two things can look identical. Your work is legitimate, bespoke and separately commissioned — but the signal Apple reads is the product pages, and yours share a visual language because that's what having a house style means.

Risk two: NDAs and the upload button

Most client contracts have a confidentiality clause covering unreleased work and restricting disclosure to third parties. Most screenshot tools are web apps that render server-side — meaning you upload the client's unshipped interface to a vendor.

Whether that's an actual breach depends on the contract, and plenty of the time it's fine. But it's a question you want to have answered before the upload, not during an incident review. The awkward version of this conversation starts with a client asking where their pre-launch screens have been.

Processing locally sidesteps the question entirely: there's no third party, so there's nothing to disclose. For regulated clients — health, finance, government — that's often the difference between a tool you can use and one you can't.

The volume maths

The workload isn't linear in clients. It's clients × device families × languages.

Each set is up to 10 images at Apple's exact pixel sizes, each with its own translated caption. Done by hand, this is where agency margin quietly dies — and it's why client listings so often ship English-only with a note to "revisit localization later." Later doesn't come.

What to standardise (and what not to)

The instinct at volume is to standardise everything. Resist it selectively:

• Standardise the process — the checklist, the export step, the keyword method, the review-notes template. All upside.
• Standardise the reference material — pixel sizes, character limits, the submission blockers. These don't vary by client.
• Do not standardise the look. This is the one that bites. A house screenshot template across eight clients is exactly the pattern 4.3 hunts for, and it makes every client's page weaker in its own category.

Things worth putting in the contract

Store-page work has a few recurring disputes. Naming them up front is cheaper than arguing later:

• Who owns the developer account. This decides who carries 4.3 exposure and who keeps the app if you part ways.
• How many languages are in scope — and that adding one isn't a small change, it's another full screenshot set.
• Who writes the App Review contact and notes. Missing these blocks submission, and it's usually discovered at 6pm on a Friday.
• Who responds to a rejection. Resolution Center replies need someone who knows the guideline, and the clock is running.

FAQ

Keep reading