Back
ROG Phone - AniMe vision
ROG Phone - AniMe Vision
Shaping the experience
before the pixels
Turning system states into intuitive visual feedback through light.
WORK AT
ASUS
TYPE OF WORK
Hardware–Software Integration
DURATION
2023-2024
CONTEXT
ASUS ExpertLumi uses a laptop light strip to signal system events, helping users notice important changes beyond the screen.
As use cases grew, lighting definitions became inconsistent. I established shared lighting behavior rules and drove the development of a WYSIWYG lighting tool to simplify handoff and speed up development.
THE PROBLEM
System: Lighting and UI feedback lacked shared rules for new scenarios.
Process: Gaps between design specifications and actual lighting behavior required repeated clarification and adjustments with engineering.
Experience: Whether users would notice and understand light signals during focused work was still unverified.
WHAT I DID
◆ Defined shared rules: Clarified the roles of lighting and UI feedback, establishing a common design basis across scenarios.
◆ Partnered with engineering : Initiated requirements for a lighting editor and worked with engineers to enable direct preview and adjustment.
◆ Tested and refined: Used hardware testing to identify when signals went unnoticed, then refined the lighting behavior.
RESULT
95%
Signal Noticeability
95% of participants noticed the lighting signal, and 100% of those who noticed it correctly understood its meaning.
10+
Scenarios Built on Shared Lighting Tokens
Defined reusable lighting rules as development tokens, enabling new and similar scenarios to reuse standardized parameters and behaviors.
-60%
Design-to-Engineering Handoff Time
Built a lighting editor that streamlined configuration and review, reducing handoff and iteration time between design and engineering by 60%.
LIGHTING BEHAVIOR IN CONTEXT
These examples show how the lighting rules translate into device feedback. Each signal is designed around a specific event, the user’s immediate need, and its relationship with on-screen information.
Power on
User need: Know startup has begun.
Design decision: Confirm startup without implying Windows is ready.
How it came together
3 min read · 6 sections
THE FULL CASE STUDY
THE FULL CASE STUDY