Deborah Foley Portfolio Deborah Foley Portfolio

Test Page HTML

Amazon Appstore — Full Page Render

Case Study 01 · Head of UX, Amazon Appstore

One store across every surface

Selling apps and subscriptions across devices, mobile, PC, and the car — and deciding when to be a brand and when to disappear.

I led UX for the Amazon Appstore as a two-sided marketplace — setting strategy across the consumer store, the developer portal, and marketing, and building the team and practice that delivered it. Reporting into a General Manager, part of my job was showing organizations new to a mature design team how to partner with design: establishing process, design-thinking and ideation practices, and incremental agile plans, while operating as program manager and design ops. I set direction and coached the senior and junior design leads who did much of the hands-on work, ran design reviews, and partnered closely with product managers, device partners, and researchers — stepping in hands-on where we were short on resources.

[ IMAGE: detail-page-across-devices hero — one store, many surfaces ]
Role
Head of UX, Amazon Appstore
Timeframe
~2.5 years · [dates]
Team
[team size / structure]
Surfaces
Fire TV, Tablet, Mobile, Hollywood, Windows, Auto, Web
Sold
Games, apps, subscriptions

The Two-Sided Marketplace

One submission becomes the whole storefront

I owned both sides — the developer portal where partners publish, and the on-device store customers buy from. Every field a developer fills maps to a moment a customer sees.

◗ Developer · Input

Store-listing form

[ store-listing screenshot ]
Customer · Output ◖

Browse + Detail page

[ detail-page screenshot ]
◗ Developer · Input

Subscription form

[ subscription-form screenshot ]
Customer · Output ◖

Subscription cards on device

[ on-device cards screenshot ]

Cross-Device · Ecosystem

One store, every surface

The same store, obligated to work across radically different devices. The craft was deciding where to unify and where to diverge — each surface tuned to its own physics without fragmenting the whole.

Fire TV

10-foot, remote-driven

Content-forward, D-pad selection.

[img]
Fire Tablet

Touch, dense browse

Utility-forward arrays.

[img]
Amazon Mobile

One-handed

Thumb-zone, instant pay.

[img]
Hollywood

Standalone app

iOS + Android.

[img]
Mado · Windows

PC game play

Co-branded trust for auth.

[img]
Automobile

Invisible utility

Native to the console.

[img]
Web · Amazon.com

Retail channel

Sell where they shop.

[img]

Category 01

Acquisition & Discovery

Acquisition doesn't happen in one place — a customer might arrive from a content tile, an app tile, the homepage, search, or the web. I led the strategy for a discovery system where every one of those is a path to subscribe, and where the purchase moment is as close to frictionless as the platform allows.

Fire TV Subscriptions · QuickSubs
1003
Fire TV remote clicks
Strategic lead

A hundred clicks, down to three

A one-click subscribe flow that collapsed a hundred-click journey down to three — straight from the app detail screen, using the customer's permission to reuse their Amazon account and payment.

[ Peacock Fire TV subscribe screen ]
1
Ideation · User Flows

Mapping the QuickSubs flow

Mapped the end-to-end journey to find where remote clicks could be removed without losing clarity or compliance.

[ flow ]
2
Final Designs

Three-click subscribe on Fire TV

Plan, price, and payment inline; one-tap confirmation; a clean success state.

[ 3 FTV screens ]
3
Wireframe

One-click, every surface

Wireframed how the pattern extends to Amazon.com and every device.

[ wireframe ]
4
Final · Web

The Amazon.com subscribe flow

Inline plans, a subscribe-and-deliver modal, and a setup screen.

[ web ]
This started as a hands-on redesign and became a platform pattern. I directed the leads who took it across surfaces and partnered with the engineering and IAP teams to make the one-permission handoff work — the wiring that turns one good screen into a system.
Acquisition · Amazon.com
+33%
increase in sales at Amazon
Hands-on · early

Web proved it — devices followed

Early and hands-on: I designed the premium detail page and email campaign that lifted sales 33% — the proof that funded a bigger bet on devices, and the content strategy that inspired the device detail-page redesign.

[ Amazon.com premium page ]

Discovery on device

Beyond the purchase moment — how customers find and control their apps.

Personalization

"Your apps & channels"

A customizable app nav. When the 2026 redesign removed it, the criticism validated the call.

[ img ]
Offers · Two-sided

Eket targeted offers

Search "The Bear," see a Hulu-tied offer. Developers opt in via the portal.

[ img ]

Browse redesigns across surfaces

The hands-on craft underneath, tuned per device.

Tablet

Browse redesign

Before → after.

[ b/a ]
Mobile

Browse redesign

Before → after.

[ b/a ]
Fire Tablet

Offers / Sales page

Before → after.

[ b/a ]

Category 02

Monetization & Conversion

How subscriptions get packaged and paid for. I led the design of the mechanics that grow attach and retention — and because each has a developer-config side and a consumer-purchase side, this is where the two-sided marketplace shows up in the work.

Subscription Types · Add-ons

Add-ons

Hands-on

Hands-on design: a parent subscription plus affiliate content apps to add on. Peacock + NBC Sports was our first — and sales went well. The platform aligns the add-on to the customer's existing billing cycle in one click.

[ add-ons flow ]
Subscription Type

Bundles

Multiple subscriptions in one (Disney + Hulu + ESPN) — value for the customer, retention for the partner.

[ img ]
Payment Type

Uni Payment

[fill: one-line function — unified checkout across purchase types].

[ img ]
Payment Type

Customer Choice Billing

[fill: one-line function — customer choice in how they're billed].

[ img ]
These came from Business Development's retention asks, which I had to solution on both the backend automation and the developer-facing frontend at once — partnering with tech writers and the portal team so a mechanic configured once behaved correctly for every customer who bought it.

Category 03

Retention & Management

The industry makes canceling almost intentionally hard. I led the opposite bet — transparent, self-service management — and turned a legal requirement into a customer-first differentiator.

Retention & Management · Compliance

Easy to cancel, by design

Strategic lead

We met the 2-click cancel law with a clean on-device flow — where most competitors make cancellation hardest — and paired it with smart retention, so honest cancellation and retention could coexist.

[ on-device 2-click cancel ]
Amazon.com

Transparent management

Manage-and-cancel on the web; the hard part was discoverability and execution in a category that buries both.

[ img ]
Flows · Retention

Retention, winback & survey

The full set of paths mapped across many happy and unhappy use cases.

[ img ]
I made the internal argument that hiding cancellation drives long-term abandonment, and that transparency would earn trust and retention — aligning legal, product, and engineering around a design position, and turning a compliance deadline into something genuinely customer-first.

Category 04 deep-dive → own page later

The Persuasion Page, across devices

The detail page is where a browse becomes a purchase. I led the strategy for a persuasion model built around the content that actually decides a customer — then proved it and scaled it across every device team.

App Detail Page

Prove it, then scale it

Strategic lead + directed team

We proved the redesign on Tablet with higher conversion, I took the data to leadership, and then evangelized every device team to adopt the same pattern — one persuasion model, tuned per surface.

[ Tablet before/after ]
Service Design

Mapping every path

All happy and unhappy paths, so it held across edge cases.

[ img ]
Scaling · Mobile

Hollywood

Re-solved for a much smaller viewport.

[ img ]
Scaling · Fire TV

The 10-foot page

Wireframes through final mocks.

[ img ]
Delivered

Across the ecosystem

Auto, web, and Amazon mobile.

[ 2×2 grid ]
The real result wasn't a screen — it was organizational: I turned one team's proven redesign into a pattern every device team chose to adopt. That's how a design decision becomes an ecosystem standard.

Category 05 deep-dive → own page later

Brand & Marketing

The Appstore had no brand identity — and a dozen siloed teams and three global markets who disagreed on whether it should. I led the research and cross-team alignment that produced the answer, then took it to market.

Brand · Stakeholder Leadership

The brand decision

Cross-team alignment

A fractured landscape aligned around one call: a strong, guideline-backed brand for 3P and marketing, and a deliberate utility role for 1P — validated when the Fire TV release buried the Appstore's ingress and drew exactly the criticism we'd predicted.

[ final brand direction ]
Align

Make the case

A deck across every siloed team + a workshop invite.

[ deck ]
Co-create

Workshop

Co-facilitated with research, design, partners, customers.

[ workshop ]
Explore

Sprint + visual language

Concepts, prototypes, CD-led Web/Tablet exploration.

[ concepts ]
Deliver

3P brand + guidelines

Amazon.com pages + guidelines for every team.

[ outcome ]

Taking it to market

One visual language across ads, devices, and campaigns.

Activation

Campaign, on air

Before → after ads (Mobile + Windows).

[ ads ]
Platform

Template → CMS → Platform

Building blocks so marketers ship their own pages.

[ templates ]
Brand leadership has been a through-line since Chase, where a dev-portal brand direction I championed was adopted company-wide, and I hired a Creative Director who became Chase's Head of Branding. Here it meant aligning teams that didn't report to me — the hardest, and most senior, part of the job.

Category 06 deep-dive → own page later

Global / Localization — Points

When Japan needed its own loyalty currency, I led the migration from Coins to Points — a market-specific product judgment delivered as a full localized ecosystem.

Japan · Localization

Coins → Points

Strategic lead

Amazon Japan already ran on Points, the currency local customers knew. I led the move to migrate Coins users to Points — retaining them while aligning to the market's established behavior.

[ Points JP — tablet/mobile ]
1
Problem

Coins → Points

Retain Japan's engaged base by aligning to Points.

[ img ]
2
Ideation

The Points economy

Pay, spend, deficit, add, detail-page education.

[ flows ]
3
Proposal

Marketing & global

Cross-region alignment before build.

[ img ]
4
Final · Localization

Web, Tablet, Mobile

Translated, adapted per surface.

[ JP screens ]

Results

What the work moved

+33%sales lift · Amazon.com
100→3clicks to subscribe
[ · ]your number
One-permission subscribe before download · Transparent 2-click cancellation · One detail-page model adopted across every device team · Launched Add-ons (Peacock + NBC Sports) · Coins → Points for Japan · App-nav call validated by the 2026 redesign criticism.

Market context (the stage, not my win): 1-click flows lift trial conversion ~2–3× industry-wide (Flurry / industry). Fire TV ~36% of US connected-TV; ~310M Appstore users. Sourced; kept separate from my own numbers.

What it shows

Consumer and business strategy at the level executives care about — acquisition, monetization, brand, and the judgment to make different calls on different surfaces without losing coherence, plus turning regulation into a competitive edge. Across all of it I owned both sides of the marketplace and built the team, practice, and partnerships that shipped it. Ecosystems and platforms, not pages.

Next case study
Amazon Developer — the input side, rebuilt

Share Project :

  • Share Project :