Optimising data presentation, interaction feedback, and the end-to-end experience across connected tools and the app for pour-over and espresso workflows.
Led core in-brew and post-brew flow improvements, responsive phone and iPad design, component guidelines, and product-development delivery.
01 / PRODUCT POSITIONING
The app connects to a screenless smart coffee scale over Bluetooth, helping people set targets, brew with live guidance, and record, review, and share every brew.
APP
02 / AUDIT & SYNTHESIS
The audit produced 55 findings. From these, 17 directly concerned the brewing journey and 7 concerned recipe details and charts.
Priority lens
03 / CORE BREWING JOURNEY
One continuous journey board maps each critical interface to its corresponding UI and UX issues.
SMART BREWThe information hierarchy is unclear
Missing layout boundaries create visual clutter
Timing starts immediately without a pre-brew reminder
SMART BREWCore data is scattered
Pause and save controls are small and do not follow familiar conventions
Icon and text alignment is inconsistent
No data-loss warning appears when an operation fails
SMART BREWCore data is scattered
Pause and save controls are small and do not follow familiar conventions
Icon and text alignment is inconsistent
No data-loss warning appears when an operation fails
The progress bar cannot represent liquid weight beyond the target
Data is presented inefficiently
The recipe page is excessively long
There is no detail window for inspecting data at a specific moment
04 / BREWING INTERFACE REBUILD
Reordering key data, target progress, charts, and controls makes every brew faster to read.
Create a stable reading path from the core value through target progress to the live chart.
Prioritize pour or extraction volume while keeping time and live flow as supporting information.
Add an overflow range beyond the target so users can still judge deviations.
Use familiar controls for play, pause, reset, and save.
Create a stable reading path from the core value through target progress to the live chart.
Prioritize pour or extraction volume while keeping time and live flow as supporting information.
Add an overflow range beyond the target so users can still judge deviations.
Use familiar controls for play, pause, reset, and save.
Keep the information architecture and action logic consistent across both modes.
Adapt parameters, units, progress feedback, and charts to each brewing method.
05 / JOURNEY EXPERIENCE COMPLETION
Critical states, feedback, and error prevention connect the full experience from starting a brew to saving it.
01 / PREPARE · START
After the countdown, there was no clear signal for when to pour or when timing should begin.
Prompt the user to pour when the countdown ends, then start timing automatically when the weight changes.
06 / DESIGN SYSTEM
Interface improvements became reusable rules for typography, iconography, components, and color—creating one visual language across brewing modes and device sizes.
iOS uses PingFang SC for Chinese and SF Pro for Latin text and numerals; Android uses Source Han Sans and Roboto.
Iconography follows the brand's minimal visual language and primarily uses simple linear elements.
Black forms the interface background, orange is the primary color, and supporting colors distinguish functional parameter types.
TYPE · ICON · COMPONENT · COLOR
07 / MULTI-DEVICE ADAPTATION
Three layout constraints preserve information hierarchy and operating efficiency across devices.
The iPad layout redistributes modules and adapts type, spacing, navigation, charts, and controls.
iPad mini uses compact 768 pt constraints; iPad Pro uses wide 810–1024 pt constraints while preserving the same information structure.
Viewport width / logical width (pt)
08 / FUTURE FEATURE PLANNING
CONCEPT / INTERNAL REVIEW · NOT RELEASEDA new primary Coffee beans entry connects bean profiles, inventory, brewing use, and automatic stock updates.
Add Coffee beans beside Discover, Games, Brew, and Profile as the home for vault capabilities.
Keep bean details, resting status, and remaining weight together so current stock stays legible.
Select a vault bean inside the brew preset to reduce duplicate entry and connect each use.
Deduct actual usage after brewing so bean data, brew parameters, and records stay aligned.
09 / CORE EXPERIENCE & INTERFACE
CONCEPT / INTERNAL REVIEW · NOT RELEASEDA continuous digital management journey spanning bean entry, inventory management, and brewing use.
01 / CREATE A BEAN PROFILE
Core inventory comes first, while roasting, flavor, and origin details remain available when needed.
02 / MANAGE CURRENT AND HISTORICAL STOCK
Bean cards surface resting status and remaining weight, with search, sorting, history, and delete actions.
03 / CONNECT TO BREWING
A bean can be selected inside the brew preset. Its name and remaining weight enter the brew context, and the system updates stock using the actual amount after brewing.
This concept is in internal review; inventory sync is expressed through brew-preset interface states without claiming a released outcome.
