Popslide: Experiments on a Lockscreen Product
I built and evaluated Android experiment variants for Popslide and worked on lockscreen behavior, notifications, caching, and production state handling.
[delivery dossier] 2 sections
The lockscreen changed the standard
Popslide mixed rewards, ads, and task-based interactions in an Android product that could appear on the lockscreen. I worked with Kotlin, lockscreen integration, notifications, Flux-style state, and Firebase services. Changes in this part of an app are hard to ignore because they sit outside the usual open-app-and-browse flow.
I implemented A/B test variants and supported their rollout. I also worked on caching and notification behavior, where stale state or a repeated event could show up immediately. A variant had to coexist with the control path and with the Android lifecycle; it couldn't be treated as a completely separate demo screen.
An experiment left code behind
Part of my work was keeping rollouts reversible and refactoring fragile areas when they blocked the next change. After a test, the unused branch needed to be removed or deliberately retained. Otherwise temporary experiment code became another permanent path that future work had to understand.
I kept changes close to the feature being shipped, cleaned up obsolete branches after experiments, and made the existing notification and lockscreen paths easier to follow.
My work centered on Android experiment variants, rollout support, notifications, caching, and the cleanup needed to keep the next test from inheriting old behavior.