Phia
Product and Web Design

- Role
- Product & web design
- Surfaces
- Web, SEO pages, iOS
- Industry
- Shopping
- Stage
- Series A, $35.5M
Impact
11K to 400K+ brand pages from one template.
Phia is a shopping product with 1.7M users and a $35.5M Series A. Over the summer of 2026 I designed the pages people land on from a Google search, before they install the app or the Chrome extension: brand pages, editorials and the partner page. I also designed the iOS app's notifications. Most of the work was one-on-one with the growth PM.
- 54% deal click-through on the redesigned sales calendar
- 305K clicks a month from about 1,700 editorial pages

Brand pages and editorials
Brand pages open on the brand, then one coupon prompt, and the template grew from 11K to 400K+.


The sandbox
The team reviewed real interactions instead of static frames, in a sandbox I built.


In-app browser and partner page
Engineering shipped the partner page from my build.

Notifications
PRD to a reviewed second version in about a week, after the review overturned six of my calls.


Featured
App of the Day and Apps We Love on the App Store, Featured on the Chrome Web Store.



Looking back
Design with the user in mind and keep asking them questions. The weekly feedback sessions at Phia gave me what people actually did and said, and that taught me more than going over information again.
Scope
Brand pages, including the luxury version and the states for brands with little data.
Editorial pages (home, index, category and article) and the block kit behind them.
The iOS notification feed and settings.
The in-app browser tests, and what I recommended from them.
The partner page, which I designed and built.
The sandbox, where the team reviewed every prototype.
Images for the Chrome Web Store and the App Store.
Contributions
A rework of the marketing landing page. I moved "How it works" up, swapped in real photography, made the hero grey and kept blue for the buttons.
The sales calendar, redesigned as a full-screen view, which reached a 54% deal click-through rate. I also ran its development for a week while the PM was away.
Design input on search, web chat, the creator program and a points campaign.
Build reviews on the SEO pages with engineering. I also made QA simpler: one doc and one ticket for bulk fixes, and separate tickets for one-offs.
The start of a design system. I cleaned up components that had drifted and started an illustration library.
The Current, which won the 48-hour Phia x Design Meetup Designathon and has its own case study here.
Lessons
People react to what they can tap. Once the team could swipe and reveal things in a coded prototype instead of looking at frames, we agreed faster, whichever way it went.
Being overruled was useful. Six of my first notification calls were overturned in review, and V2 was better for it.
A PRD can work against its own goal. It asked for one switch for all push, which one careless tap could turn off, so I suggested a switch for each topic.
Ask the person doing the checking. Reviewing builds against Figma frames was slow, so I sat down with the PM doing QA to work out what would help, and that turned into the sandbox I built.
PRD to launch
PRD review: Every week, on mockups, so we agreed on scope before the full designs.
Design review: One-on-one with the growth PM in Figma, until we picked a direction.
Prototype: I built the direction we picked in code, at desktop and phone sizes, with the real interactions.
Team review: The team reviewed the build, and I wrote each decision next to its screen.
Build review: After the engineering kickoff, we reviewed their build until it matched the design.
Phased launch: We launched in stages, starting with what the data could support.
Brand pages and editorials, Problem
Phia's first brand pages were adapted from the mobile app, and traction on them was really low. That's why we rebuilt them.
Most people reach a brand page from a Google search. If it pushes coupons before saying who the brand is, it looks like an affiliate site, and people leave.
Editorials had a few jobs at once: bring in search traffic, keep people reading, and carry placements the partnerships team could sell.
Brand pages and editorials, Decision
I opened the page with the brand and one short coupon prompt, put products right below, and kept the SEO copy as plain text instead of tucking it into an accordion.
Codes stay blurred until you tap one. That opens a single unlock modal where you can add the Chrome extension or scan a QR code for the app. A Phia-exclusive code gets its own card.
Most brands are missing something, so I designed states for no codes, few products or no editorials. Luxury brands use the same template with the coupons turned off.
The partnerships team builds editorials in a block-based dashboard, so I gave them a kit of blocks. Home, index, category and article pages all come from it and one data file.
I laid out the editorial index the way placements are sold: a hero card, a row of medium cards, then compact cards that are mostly there for SEO.
Long articles alternate text and products so the products read as part of the story, and a product grid drops in every eight items.
Brand pages and editorials, Results
The first brand template shipped with a three-part SEO copy block. Brand descriptions are generated, and the team can edit them in the admin.
While I was there, the template grew from 11K pages to more than 400K.
Editorials came to four page types and three article templates from one kit. The old pages stayed live and kept earning traffic until the new ones replaced them.
The editorial templates reached about 1,700 pages, with 23M impressions and 305K clicks a month.
Both ran as coded prototypes at 1440 and 390 wide, with the real fonts and the coupon reveal working.
Brand pages and editorials, Tradeoffs
We cut three things in PRD review. Shop Similar needed brand-to-brand data we didn't have yet, and return policies and seasonal sales are waiting until the data is reliable.
For editorials I left out what the backend couldn't support yet, like tags and the oversized lead image. I still designed them, so the team could see where it was heading.
The sandbox, Problem
The SEO pages had to match Figma closely, and checking builds against static frames was slow for everyone. I sat down with the PM who was doing QA to work out what would actually help.
The sandbox, Decision
I built a small Next.js app that holds the coded prototypes in device frames. You can pin comments to the screen, there's a notes panel, and a spec list compares the design with the build.
When we changed our minds, the old version stayed walkable. Notifications V1 still lives there as an archived tab.
The sandbox, Results
Reviews happened on the real interactions, like the unread highlight, swipe to delete and the coupon reveal, and the reasoning stayed next to each screen.
The sandbox, Tradeoffs
A build takes longer than a frame, so early ideas still started in Figma, and only the direction we picked got built.
In-app browser and partner page, Problem
Editorials were becoming where Instagram and TikTok traffic landed, so people read them inside those apps' built-in browsers. The brief was to move them into a real browser before asking them to install anything.
The old partner page sat below the main navigation and split people between a sign-in and a long free-text form.
In-app browser and partner page, Decision
I built a replica of the in-app browser and tried five placements on one real editorial, with four versions of the copy and the host app as switches I could flip live.
Layout changes how much the nudge interrupts, and copy changes whether people act, so I changed one at a time to see which was doing the work.
For the partner page, I moved it into the main navigation and gave it one Get in touch button that scrolls to a short form.
I built that page myself in plain HTML, CSS and JavaScript, with help from AI, so engineering got a working page instead of a Figma file.
In-app browser and partner page, Results
I recommended the top strip. It sits right next to the menu it's teaching people to use, and inside an iOS in-app browser a link into the Phia app opens, while a link out to Safari doesn't.
Engineering shipped the partner page from my build and connected it to the backend.
It changed how we worked. Designers got much finer control over the final page, and going from design to code to shipped got a lot faster. The team used the same approach on later projects.
In-app browser and partner page, Tradeoffs
Open in browser can't open Safari from inside the app, so it copies the link and shows how, and the reader takes the last step.
With a single button, the dashboard sign-in lost its spot on the partner page.
Notifications, Problem
The app needed a notification feed and settings, from a PRD, quickly.
I wanted any idea we turned down to stay somewhere people could still try it, because those ideas tend to come back.
Notifications, Decision
V1 was a sheet over Home, grouped by day, with a blue dot for unread.
The review overturned six of my calls, and V2 is better for it.
In V2 the feed is a full page and settings stays a sheet, since a backlog needs the whole screen and a preference doesn't. The day headings and the blue dot are gone, and unread rows get a grey highlight that clears after about a second.
A row holds an image or a button, never both, and only gets a button when the action finishes right there.
Notifications are kept for 30 days, so the empty state got a way out: Find items to watch.
The PRD had one switch for all push notifications. One careless tap would turn everything off, so I suggested a switch for each topic, and we went with it.
Notifications, Results
It went from PRD to a reviewed V2 in about a week, with every screen tappable.
Microcopy alone lifted the onboarding permission opt-in by 3%.
The six calls that were overturned are still in an archived V1 tab, each with the case for and against, so nobody has to argue them again from memory.
Notifications, Tradeoffs
There's no undo, so swipe to delete only commits well past the point that shows the button.
Anyone who wants everything off has to turn off each topic one by one.




