Physical button
Short pressLong press
Case 03 · OPPO Find X Series Shortcut Button · Core design & launch Nov 2024—Jun 2025
A complete shortcut-button experience—from predictable response to first-time setup.
As software experience design lead, I defined the short-press and long-press rules, state feedback, and setup journey from the ground up across 5 behavior categories × 5 context groups and 10 functional modules. Once the response model was stable, I reframed the next challenge around when people would first understand and configure the button.
20.5% → 49.3%One-Tap Notes share among users who configured any button function
- Role
- Software Design Lead, Shortcut Button
- Timeline
- Nov 2024—Jun 2025
- I led
- Interaction rules · State feedback · Setup flow · Usability testing · Metric definition and interpretation
- Partners
- Product · Engineering · Research · QA · Visual · Motion
- Rule scope
- Short press · Long press · 5 behavior categories × 5 context groups · 10 modules
- Validation
- Usability testing · Aggregated production data
Case chapters
Current chapterChallenge01 / 08⌄
01 / Challenge
A physical button can be pressed before any interface is visible.
If 10 functional modules defined short press, long press, and feedback independently, the same action could produce contradictory outcomes while the screen was off, the device was locked, an app was open, or a task was running. The work first had to answer how the system should respond, then whether people would discover the button and complete setup. Cross-checking exposed 14 experience risks, most involving comprehension and state awareness.
- 01
Across 5 behavior categories and 5 context groups, when should an action execute, adapt, wait, or be blocked?
- 02
How should short press and long press remain predictable? Double press was not part of the model.
- 03
How should the system communicate the outcome, current state, and expectation for another press?
02 / Method
Define the rules before designing the screens.
I synthesised and applied a four-step hardware–software method to avoid defining the experience from one screen or idealised context.
Rule model
Every press passes through the same state model.
The rules do not begin from a screen. They cross action, context, and system state before selecting a response and feedback channel.5 behavior categories × 5 context groups
Across 10 integrated functional modules
Home & appsLock screenActive taskAlways-OnSpecial state
Also checks current system, configuration, and task stateRespond to the current state
ExecuteAdaptWaitBlock
Make the outcome immediately perceptible
VisualHapticAudio
Legible state · Predictable next press
Consistency does not mean identical feedback everywhere. It means a predictable relationship between intent, state, and outcome.
03 / A rule in practice
5 behavior categories × 5 context groups across 10 functional modules.
The full specification defined both short press and long press and cross-checked behaviors against contexts. Switching the device sound state shows how feedback can make a change perceptible without interrupting the current task.
Make outcomes perceptible
Confirm execution through clear visual, haptic, or audio feedback.
Keep state legible
People should know whether a function is active, a task is running, and what another press will do.
Adapt without breaking causality
Responses may change by system state, but the same intent cannot produce contradictory outcomes.
Representative rule · Ring / Vibrate / Silent
Change the device sound state without leaving the current task.
When the device is in Ring mode, a long press switches it to Vibrate or Silent.
An OPPO Fluid Cloud status capsule shows the result, reinforced by haptic feedback.
The outcome is immediately perceptible without a full-screen interruption.
Representative rule: switching the device sound state.
04–05 / Iterations
Two local improvements exposed two problems at different levels.
Iteration 01 · State visibility
Instant application does not mean people know that something changed.
The first version applied One-Tap Notes immediately when Settings opened, while horizontal swiping changed the function. In a test with 10+ primarily younger participants—configure a function on a new phone, then trigger it in any context—roughly half verbally reported that they did not know setup had already succeeded.
When an interaction changes system state, state visibility matters more than pattern familiarity.
Iteration 02 · Feature discovery
Making setup visible did not explain why the button was worth setting up.
Version 2 launched in Feb 2025 with an explanation, explicit confirmation, and visible current selection. Production data and usage observation showed One-Tap Notes at 20.5% among configured-button users, while many people still discovered the feature through an accidental or exploratory first press.
A first-press prompt only explains after discovery, while Settings assumes prior awareness. Neither builds an expectation when people first learn the device.
06 / Final direction
Move setup into onboarding and establish an expectation before first use.
The final solution launched in Jun 2025 and moved introduction and setup to the last stage of device onboarding. Continue automatically assigned One-Tap Notes; Customize remained visible at the same hierarchy. The step could not be skipped, but people could go back. Instead of refining Settings again, the design connected button introduction, function choice, and setup confirmation within the moment people first learned the device.
Understand
Explain the control while the device is first being learned.
Choose
Offer a recommended path inside a required step while keeping Customize at the same hierarchy.
Confirm
Provide clear completion feedback so people know the device is ready.
07 / Production outcome
The target-function configuration share increased from 20.5% to 49.3%.
After the final solution shipped, production data from new-user cohorts on the same handset model, drawn from different sales periods, showed a substantial increase in One-Tap Notes among users who configured any button function.
Metric scope: new users of the same handset model across different sales periods; the measure is One-Tap Notes share among users who configured any shortcut-button function. In the final version, Continue completed the recommended setup, so the result reflects the post-guidance configuration outcome.
08 / Reflection
The rules must be correct, and the value must be understood at the right moment.
Begin with a state model
A single ideal context cannot represent the real complexity of a physical control.
Keep state visible
A mature pattern cannot replace understanding the product’s own context and feedback needs.
Treat discovery as a system journey
When a local screen cannot achieve the objective, find the right moment for the decision.
For a physical button, correct response rules are only the starting point. A complete experience also helps people understand it, choose it, and confirm it is ready before first use.