All workEsc

Connecting campaignsthrough the Offerwall.

An Offerwall brings together campaigns and offers where people earn rewards. I connected campaign placements across our partner companies’ apps to this shared destination, first as a designer and later as product owner. Internally, we called it Feed, then Hub.

1 feed 4 allMany ways in. One destination.

Inside a publisher app

daylight®A
Your points12,440PA little more, every day.
Daily check-in
Invite a friend
Today’s steps4,820 / 8,000
Discover & earnPicked for you
Fictional FORME skincare campaign with green glass bottles on sunlit stone
FORMESponsored

Find your daily ritual

Visit the brand

The shared Feed

Rewards12,440P
Earn pointsMy activity

Offers selected for you Updated daily

A campaign in the app. A direct route to more offers.

Reimagined product scenes with fictional campaigns and rewards.

The audience grewbeyond our own app.

Buzzvil’s software brought reward-based campaigns into partner apps, where publishers earned revenue and people earned points. Honeyscreen, our own app, remained a place to try new experiences.

May 2019Monthly active users
10MAcross the Buzzvil network.
October 2021Monthly users
20MAcross more than 150 publishers.
Q3 2021Company revenue (KRW)
₩22.3B₩12.3B in Q3 2020; +81% year on year.

Company-reported figures. Business growth reflects work across teams. Company history2021 company release

The product foundation

One product had to feelat home in many apps.

Hundreds of interfaces had to fit inside hundreds of different apps. I built much of the early design system around that challenge: keep a shared product, while letting each partner’s brand shape how it looks and feels.

Rewards12,440P
Earn pointsMy activity

Offers selected for you Updated daily

A shared product, their identity

The brand changes.
The structure holds.

Creative, task and reward stay in the same place. Partners can adapt the surface to their app.

Appearance
Publisher accent
Shared hierarchy
  1. 01Brand creative
  2. 02A clear action
  3. 03A visible reward
Try a different appearance, filter offers or open a campaign. A refreshed reconstruction using fictional brands and sample points, not an exact SDK configuration preview.

Phantom, Chameleon and the systems that followed were successive attempts at the same problem. We rebuilt and refined our UI kits through hundreds of iterations. From the start, the ambition was a headless design system: separate the product’s behavior from its visual identity, with design decisions expressed as tokens or configurable values for each brand.

Zoom in · Where the brand decisions live

A new brand should change the design values, without requiring a separate version of every screen.

Two layers today.
A third layer to grow into.

Tokens are named design values. Separating the raw values from their purpose lets the same interface take on a different identity.

  1. In the SDK today

    01 Core

    The raw material: colors, spacing and other foundational values.

    A brand’s color palette
  2. In the SDK today

    02 Semantic

    What those values mean: a primary action, a background or readable text.

    Primary actionA shared role, a brand-specific value
  3. A next step

    03 Component

    How a particular element uses those roles, allowing more precise control.

    Claim rewardFor example, a reward button’s background

The layers, illustrated. Component-specific tokens remain a direction to develop.

The system kept growing.
So did its flexibility.

The team continued this work after my early systems. Today’s SDK has a solid core-and-semantic token foundation and a full server-driven interface, configured from the server. I would like to take it further with component-specific tokens, so individual elements can adapt without changing a shared role everywhere.

Inside the original system · 2021
2021 Feed prototype with tabs, filters, image and video cards
The full Feed: a hierarchy for navigation, creative and reward.
2021 Feed component system adapted to a bottom sheet
The same hierarchy inside a bottom sheet, with publisher context behind it.

Original designs with sample campaigns and rewards.

Zoom in · Connecting campaigns to more offers

The shared Feed needed ways in from the campaigns people already encountered. One example was the carousel I created: a horizontally scrolling row of campaign cards inside a partner’s app, with a link and final card that opened the wider Feed.

We kept the connection.
Publishers shaped the placement.

A bundled carousel UI made customization too heavy. We moved to an integration guide and sample implementation, with SDK support for the final Feed-promotion card.

Compare the original carousel
Original Honeyscreen designs showing a native ad and the final Feed promotion card in the same carousel placement
The original design: a final card opens the Feed. Sample rewards.
Original Carousel UI file

Exposure grew. Engagementstill needed work.

Connecting the units drove substantial Feed-impression growth. As product owner, I also needed to understand its limits: the overall product, a layout test and one carousel placement told different stories.

Feed product totals / 2021

The Feed grew
across platforms.

May–June compared with July–August 2021.
Two-month totals across all platforms.

Feed page views

392.0M432.2M

Feed revenue

₩3.37B₩3.61B

Wider publisher adoption contributed to this growth. These totals describe the product; they do not isolate the effect of a redesign.

Zoom in · Feed density

Growing exposure was not enough. Could a different layout turn more of those visits into advertiser value?

Feed layout A/B / 2022

More ads shown. More revenue.
A smaller share clicked.

OriginalRevised
Ads shown per visit+16%
6.88
7.96

More offers were exposed.

Revenue / 1,000 visits+7%
12.87
13.77

Each visit generated more revenue.

Share of ads clicked−12%
8.54%
7.49%

Exposure did not translate equally into clicks.

Showing more ads increased revenue per visit, but a smaller share of those ads were clicked. A more prominent action button did not close the gap. There was no difference in people returning the next day or the following week.

Honeyscreen, Buzzvil’s rewards app · Android, 2022. Rounded changes; each chart uses its own scale. Design: Brice, Diane and Max. Analysis: Cathie. Analysis

Zoom in · The carousel’s connection to Feed

The carousel introduced more campaigns, but did people continue to the shared destination?

Back to the product · The next constraint

A bigger Hub exposed thelimits of a single feed.

The team continued the ecosystem after I moved on. By 2025–2026, adding more formats meant competing for the same attention: moving one section up could move another out of sight.

Requiring partner apps to have their own points system also limited who the product could serve. The next questions were about the experience itself, and what would make people participate.

Continue with Game UA
Later finding · Visibility within the pageKB StarBanking
Upper sections93–95%
Shopping11%

Share of Hub visitors who saw each section. Later team research.

Read the team’s findings

What I learned.

Design the connections.

The Feed became more valuable when the units around it had a clear route into it. My scope grew from individual screens to the network of connected ad placements.

Let the publisher own the context.

A shared destination did not require identical placements. Integration guidance gave publishers room to adapt the carousel while keeping its connection to the Feed.

Read beyond the uplift.

Impressions, visits, revenue and engagement answer different questions. Their tradeoffs were more useful than a single headline number.

Image detail

Loading full-size image…