Developer platforms
Building for developers is different. The people using these tools are technical, opinionated, and have zero patience for friction. They'll go around a bad experience, and at Meta, they were. Bug reports were landing on Reddit and Twitter. The developer center was buried under outdated Oculus branding and thousands of pages of documentation with no clear path through.
Company
Meta Reality Labs
Year
2025 – 2026
Documentation
The Horizon Developer Center redesign gave developers a clearer, faster path into the Meta ecosystem. The previous site carried outdated branding and forced developers to dig through thousands of pages of documentation to find what was relevant to them. The redesign introduced structured navigation organized around build paths, an improved API reference with quick code copying, and the foundation for AI-powered search.
Release Notes
I redesigned the Meta Horizon OS release notes page from the ground up, introducing dynamic filtering by year and platform, AI-generated summaries for each entry to make dense technical changelogs easier to scan, and a content architecture where dates and entries surface dynamically based on what the developer is filtering for.
The creation and authoring flow I designed to power this is internal, but the impact extended well beyond the developer platform: the system was adopted cross-company by Facebook, Instagram, and WhatsApp, giving those teams a streamlined release notes authoring process for the first time.
Developer Feedback Hub
We built a zero-to-one tool, Feedback Hub, within Meta Quest Developer Hub to give developers a structured, official channel to report issues and communicate directly with Meta for the first time. Before it existed, bug reports were scattered across Reddit and Twitter with no visibility into whether Meta had even seen them. The core flow covers three moments: an at-a-glance view of all cases, a guided submission flow, and a detailed status view for each issue.
