CONTEXT

THE PROBLEM
System events and personalized content needed distinct setup paths.
WHAT I DID
I separated System Events from Personalization, giving automatic feedback and content creation dedicated paths.
The preview provided little context for judging the display area, image size, and placement on the phone.
WHAT I DID
I added unlit gray dots, a
rear-cover reference, and images rendered as dots to the UI preview.
Image edges and grayscale brightness differed between the UI preview and the physical display.
WHAT I DID
I compared source assets, UI previews, and device output, then worked with engineering on asset guidelines and brightness mapping.
RESULT
I compared source assets, UI previews, and on-device output to guide brightness adjustments. BSP engineers adjusted firmware-level brightness mapping, preserving the original assets for 89 animations and allowing the UI preview and device output to continue using the same source files.
PRODUCT SHOWCASE
The final AniMe Vision experience on ROG Phone 8/9, showcasing the rear dot-matrix display and its animations.
To avoid the rear display becoming a novelty, the team used early interviews to define two directions: ready-to-use system feedback and flexible personalization.
I mapped everyday events to preset animations, including incoming calls, charging, camera countdowns, and X Mode. Users could enable event feedback without first creating or importing content.



I defined three creation paths: Draw, Signature, and Import. Users could create content in the editor or bring in their own images and GIFs, then check the result in the UI preview.

Draw
Signature
Import
During testing, users repeatedly flipped the phone over to check the back cover because a plain preview offered little context.
The preview needed to show more than the image itself. It also needed to help users judge the display area, image placement on the phone, and details in the dot-matrix version.
I added three elements to the UI preview.




By comparing source assets, UI previews, and physical output side by side, I separated display discrepancies into two layers: asset sampling and firmware brightness mapping.

I worked with engineering to define artwork alignment rules based on each LED’s sampling position.

I supplied visual comparisons for BSP’s Gamma Mapping adjustments, preserving the original assets used by the UI preview.

Asset rules govern outline precision and grid alignment; Gamma mapping governs physical grayscale rendering. Separating these two layers prevented redundant asset rework while keeping both the UI preview and hardware output accurate.
The challenge of AniMe Vision was to connect setup flows, in-app previews, source assets, and on-device output. My core contribution was turning issues across these layers into clear design requirements, using side-by-side visual comparisons to help engineering locate display discrepancies and determine where to make adjustments.
What I'd do differently
I would establish a testing baseline earlier and repeat the same tasks after each preview iteration.
Alongside observing user behavior, I would track how often users turn the phone over and how accurately they judge content size and placement. This would help assess whether the preview reduces the need to check the physical display while maintaining judgment accuracy.
What I'd still defend
I would keep the principle of locating the source of a discrepancy before deciding what to change.
Outline precision and LED-grid alignment call for asset guidelines, while on-device grayscale rendering calls for firmware brightness-mapping adjustments. Distinguishing these issues helped the team address their underlying causes and avoid editing animations individually to compensate for firmware-level brightness differences.




