AniMe vision

ROG Phone 8/9

ROG Phone 8/9

ROG Phone 8/9

AniMe Vision

AniMe Vision

AniMe Vision

Connecting software personalization with a physical dot-matrix display.

Connecting software personalization with a physical dot-matrix display.

Connecting software personalization with a physical dot-matrix display.

WORK AT

WORK AT

ASUS

ASUS

ASUS

TYPE OF WORK

TYPE OF WORK

Hardware–Software Integration

Hardware–Software Integration

Hardware–Software Integration

DURATION

DURATION

2025-2026

2025-2026

2025-2026

CONTEXT

AniMe Vision is a dot-matrix display on the back of ROG Phone. It shows system feedback, text, and personalized graphics. Users configure content on the front screen and see the result on the back.

AniMe Vision is a dot-matrix display on the back of ROG Phone. It shows system feedback, text, and personalized graphics. Users configure content on the front screen and see the result on the back.

AniMe Vision is a dot-matrix display on the back of ROG Phone. It shows system feedback, text, and personalized graphics. Users configure content on the front screen and see the result on the back.

I led the UI/UX planning from 0→1, defining setup flows, preview specifications, and interaction requirements. I worked with software, BSP, and hardware engineers to investigate differences between UI previews and on-device output.

I led the UI/UX planning from 0→1, defining setup flows, preview specifications, and interaction requirements. I worked with software, BSP, and hardware engineers to investigate differences between UI previews and on-device output.

I led the UI/UX planning from 0→1, defining setup flows, preview specifications, and interaction requirements. I worked with software, BSP, and hardware engineers to investigate differences between UI previews and on-device output.

I compared three stages of the experience: original animation assets, the in-app dot-matrix preview, and on-device LED output.

I compared three stages of the experience: original animation assets, the in-app dot-matrix preview, and on-device LED output.

I compared three stages of the experience: original animation assets, the in-app dot-matrix preview, and on-device LED output.

THE PROBLEM

Different setup needs

Different setup needs

Different setup needs

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.

Limited preview context

Limited preview context

Limited preview context

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.

Preview and device differed

Preview and device differed

Preview and device differed

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

89

89

89

Animations retained without individual edits

Animations retained without individual edits

Animations retained without individual edits

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.

ROG Phone 9 — AniMe Vision

Rear dot-matrix animations showcased on the finished device.

ROG Phone 9 — AniMe Vision

Rear dot-matrix animations showcased on the finished device.

ROG Phone 9 — AniMe Vision

Rear dot-matrix animations showcased on the finished device.

01 / Establish a dual-track experience strategy

01 / Establish a dual-track experience strategy

01 / Establish a dual-track experience strategy

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 translated this strategy into System Events and Personalization, defining the controls, content options, and previews for each.

I translated this strategy into System Events and Personalization, defining the controls, content options, and previews for each.

I translated this strategy into System Events and Personalization, defining the controls, content options, and previews for each.

Experience Strategy

Experience Strategy

Experience Strategy

Freedom to personalize

Freedom to personalize

Freedom to personalize

Personalization

Personalization

Personalization

Choose preset content, or create your own with Draw, Signature, and Import.

Choose preset content, or create your own with Draw, Signature, and Import.

Choose preset content, or create your own with Draw, Signature, and Import.

Ready-to-use feedback

Ready-to-use feedback

Ready-to-use feedback

System Events

System Events

System Events

Preset animations provide feedback for incoming calls, charging, camera countdowns, and entering X Mode.

Preset animations provide feedback for incoming calls, charging, camera countdowns, and entering X Mode.

Preset animations provide feedback for incoming calls, charging, camera countdowns, and entering X Mode.

System Events

System Events

System Events

Ready-to-use feedback

Ready-to-use feedback

Ready-to-use feedback

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.

Personalization

Personalization

Personalization

Three ways to create

Three ways to create

Three ways to create

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

02 / Make the UI preview easier to evaluate

02 / Make the UI preview easier to evaluate

02 / Make the UI preview easier to evaluate

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.

• Unlit gray dots reveal the full grid, helping users judge how much display space their image occupies.

• Unlit gray dots reveal the full grid, helping users judge how much display space their image occupies.

• Unlit gray dots reveal the full grid, helping users judge how much display space their image occupies.

• A rear-cover reference shows image size and placement relative to the phone and camera module.

• A rear-cover reference shows image size and placement relative to the phone and camera module.

• A rear-cover reference shows image size and placement relative to the phone and camera module.

• Images rendered as dots let users check outlines and small details in the UI preview.

• Images rendered as dots let users check outlines and small details in the UI preview.

• Images rendered as dots let users check outlines and small details in the UI preview.

03 /Compare source assets, UI preview, and hardware to isolate display discrepancies

03 /Compare source assets, UI preview, and hardware to isolate display discrepancies

03 /Compare source assets, UI preview, and hardware to isolate display discrepancies

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.

Finding 01

Finding 01

Finding 01

Uneven edge brightness

Uneven edge brightness

Uneven edge brightness

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

Finding 02

Finding 02

Finding 02

Lost grayscale detail

Lost grayscale detail

Lost grayscale detail

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.

05 /Conclusion

05 /Conclusion

05 /Conclusion

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.