Overwolf
Dev Console: Roblox Launcher
Two features I designed for developers managing their Roblox Launcher: a notification system and a streak/reward campaign builder, both built into the Dev Console.
Role
Product Design Lead
Timeline
2026
Surfaces
Overolf Developer Console
Scale
280+ Million users

Notifications creation & managment
Developers running a Launcher needed a way to message their player base directly, live events, new content, promotions, without relying on Roblox's own notification limits (1 per experience per day, opt-in only).
What I designed:
A notification control table where devs can track every notification's status (scheduled, live, expired, deactivated), views, and clicks at a glance
A creation flow with two trigger types (scheduled push vs. "on Roblox launch"), a live preview panel that updates as the dev fills in the form, and clear content limits so the notification never breaks on-screen
The eligibility and cooldown logic behind the scenes: per-user frequency caps, retry windows, and priority stacking, so users get relevant messages instead of spam
Later extended to mobile: the same system now reaches the Android app via push, with its own content limits, timezone handling, and an automatic streak reminder trigger, on top of the desktop version devs already knew.


Roblox Streaks
A daily login/reward campaign builder, letting developers define a 7 or 30-day streak for one of their experiences, assign a reward asset per day, and track engagement over time.
What I designed:
The streak list view, showing every campaign's dates, duration, final reward, and live/archived status
The creation flow: a day-by-day reward table where devs upload an asset and name a reward for each day, with day 7 supporting multiple optional assets
A locked set of core rules to prevent misuse, only one active streak per experience at a time, and once a streak goes live, only the reward assets and names stay editable, not the structure
Later extended to mobile: the same system now reaches the Android app via push, with its own content limits, timezone handling, and an automatic streak reminder trigger, on top of the desktop version devs already knew.



Both features share the same underlying pattern: give developers real control over timing and content, while keeping the guardrails (frequency caps, one-active-campaign rules) baked into the system rather than left to trust.
More projects.
Check out the rest of the featured proojects I've worked on.




