User Model
End-to-end redesign of OneSignal's core data model from devices to users, enabling Custom Events, Event Streams, and enterprise deals the old architecture couldn't support.
Overview
Led the end-to-end redesign of OneSignal's core data model from devices to users, coordinating across 6 product pods and shipping new APIs, SDKs, and UX across every platform. The new model directly enabled Custom Events, Event Streams, and new integrations, and opened the door to enterprise deals the old architecture couldn't support.
The Problem
OneSignal's device-centric data model didn't reflect how modern apps think about users. A single person might have multiple devices, multiple platforms, and multiple identities across an app. Developers were working around limitations constantly, and it created real product and compliance risk for OneSignal long-term.
My Approach
I partnered deeply with the SDK team to understand the technical constraints before defining requirements. We built in three phases — Alpha for early feedback, two Beta rounds for iteration, and GA with a full migration guide and documentation — to reduce risk and gather signal at every step.
What We Built
- →New user-centric identity model replacing the legacy device model
- →SDK updates across iOS, Android, and Web
- →Migration guide and documentation for existing customers
- →Internal tooling to support the SDK team's development workflow
- →Alpha (Jan 2023), Beta 1 (Feb), Beta 2 (May), GA (Aug 2023)
Outcome
The new model shipped end-to-end — touching all APIs, SDKs, and UX across the platform — coordinating 20+ engineers across 8 product pods with a backwards-compatible migration path for a platform used by 1 in 5 apps in the App Store. Custom Events was directly unlocked as a downstream result, and the new identity layer expanded enterprise sales opportunities that weren't possible before.