UX, UI, Design System — 03 / 000%EN日本語繁中
Case 03 — ASUSTeK Computer Inc. — 2024

How might we go from supporting a team with no designers to designing an app that lets everyday people repair their own laptops?

  1. Support the team
  2. Clarify the current state
  3. Align on fixes
  4. Complete the design
  5. Users repair on their own
Company
ASUSTeK Computer Inc.
Role
Senior Product Designer
Collaborators
Customer service team, GUI team
Platform
Mobile app (iOS / Android)
Period
2024.09 – 2024.10

Overview

Right to Repair laws in the EU and several US states require manufacturers to give consumers access to parts, tools and repair information. ASUS started Repair Assistant in response. Having the parts doesn’t mean people can do the repair, so the app guides them through it step by step.

At ASUS, the design center is an independent unit, and business units come to it when they need design support. This project was led by the customer service team, which didn’t have enough design resources and asked the design center for help. I joined in September 2024 and owned the design end to end, from sign-in to the end of the repair flow. I first reviewed where the project stood, found the flow issues and worked through the fixes with the customer service team. Then I asked the GUI team for their UI kit and built the interface with components from the ASUS design system.

Two months later, I handed off the design, and after the customer service team signed off, it went into development.

Design pages delivered
41
Detailed flows compared with the original brief
2×+
Flow issues fixed
3
From joining to handoff to development
2 months

Objectives

  1. Understand the current state and propose solutions
    Learn what the customer service team needed, sort out the issues and propose solutions.
  2. Meet ASUS design standards
    Help a team without enough design resources ship a product that follows the guidelines.
  3. Make self-repair possible for everyday users
    People with no repair experience can replace a part by following the flow.

Problems and fixes

I went through the existing design screen by screen and found three places where users could get stuck or make mistakes, then discussed each flow change with the customer service team:

  1. Users could skip camera permission
    The app checked camera access at sign-in but let users continue without granting it. They only got stuck later, when scanning a QR code or entering AR mode, with no idea how to continue.
    Fix: Moved the camera permission check to right before the QR code and AR features are used
  2. Items still triggered their actions in multi-select
    With several items selected, tapping an item again to deselect it triggered the item’s own action instead, which led to mistakes.
    Fix: In multi-select, removed every event except selecting and deselecting
  3. Saved procedures didn’t show every step
    Tutorial videos were downloaded one step at a time, so Saved Procedures listed only the steps already downloaded. With limited mobile data, users couldn’t always download the rest on the spot.
    Fix: Changed tutorial videos to a single full download, with a data-usage warning before it starts on mobile data
Camera permission is requested only when the user taps Launch AR
Camera permission is requested only when the user taps Launch AR
Delete confirmation in multi-select; selected items no longer trigger their actions
Delete confirmation in multi-select; selected items no longer trigger their actions
After a full download, every step is available from saved procedures
After a full download, every step is available from saved procedures

Research and constraints

Before I joined, the project used Dell’s AR Assistant as a reference. Through the phone camera, it overlays disassembly steps on the real device, and some models also have a 3D model you can view from any angle. After joining, I downloaded and used it myself, studied the full flow, and marked the points where users should be warned about mobile data use. My observation: with AR, you hold the phone up to look first, then put it down to work. You can’t look and work at the same time.

  • No design resources on the team In about two months, the details of the existing flow had to be filled in and handed off to development.
  • ASUS design standards Interface components had to come from the design system and be reviewed by the GUI team.
  • Limited mobile data overseas Videos are large (500 MB–1.5 GB per procedure), and many overseas users have limited mobile data.
  • AR feasibility unconfirmed At the time, it wasn’t confirmed whether the AR mode in the design could be built.

What we built

New feature: Favorites

To work around limited mobile data overseas, I added Favorites. Users can save a model without downloading any videos, then find it quickly later. Adding a favorite never starts a download, and new items are marked with a red badge count.

Not saved (outline star)
Not saved (outline star)
Saved to Favorites (filled star), with no download
Saved to Favorites (filled star), with no download
Bringing in ASUS design standards

I asked the GUI team for their UI kit, built the interface with design system components, and had them review it with me. Where existing components fell short, I designed new ones following the guidelines and confirmed each one with the GUI team.

Added late in the project: Smart Matching Mode

Late in the project, the team decided to add image recognition and asked me to design it. After users select their model, they now choose how they want to be guided:

  • Smart Matching Mode Uses image recognition to assess repair progress, then suggests the next step with videos.
  • Step-by-Step Guidance Mode Users watch the repair videos in order and follow along one step at a time.
Mode selection
Mode selection
The full journey, from sign-in to the end of the flow

I designed the whole journey, from sign-in to the end of the repair flow, in this order:

1 Sign in
1 Sign inSupports biometric sign-in, with a manual retry if it fails.
2 Find the device
2 Find the deviceKeeps the three existing ways: enter the model name, enter the serial number (or scan a QR code), or pick from the model list.
2 Choose a guidance mode
2 Choose a guidance mode
3 Choose the part
3 Choose the partUsers pick the part to replace and see the recommended tools.
3 Recommended tools
3 Recommended tools
4 Safety check
4 Safety checkPrecautions appear first, and users confirm them before they start.
5 Video download
5 Video downloadOn mobile data, the app shows the estimated data use and suggests Wi-Fi. Users can also download all steps at once.
6 Step navigation
6 Step navigationEach procedure is split into numbered steps (1/4, 2/4…) with a video preview. Tap any step to jump straight to it.
7 AR guidance
7 AR guidanceTapping Launch AR asks for camera permission first, then opens the AR view (see How the released version differs).
Full flow map, including branches and edge cases
Full flow map, including branches and edge cases

How the released version differs

AR overlay guidance

The project’s original direction was an AR mode. Users tap Launch AR, point the camera at the laptop and align it with the outline to lock on, and the screen marks where to remove each part (1-1, 1-2…). My design included this mode, with a note that technical feasibility still needed to be confirmed.

Late in the project, the team decided to add image recognition, and I was the one who first put Smart Matching Mode into the design. The released version dropped AR and centers on AI image recognition with video guidance. The form changed, but the core idea stayed the same: knowing which step the user is on.

AR overlay: after aligning with the outline, removal points 1-1 to 1-4 appear (in the design, not released)
AR overlay: after aligning with the outline, removal points 1-1 to 1-4 appear (in the design, not released)

When I handed off the design, the app was called AR Repair Assistant. The released version is named ASUS Repair Assistant and has no AR feature.

Outcome

Delivered 41 pages of design into development. The app later launched on iOS and Android, and the product won a Red Dot Design Concept 2025 award.

  • A week before I left, the team told me testing could start the following week. I left before it began, so I wasn’t part of testing.
  • The product later won a Red Dot Design Concept 2025 award (Ready for Market / Artificial Intelligence).
  • The app later launched on iOS and Android, keeping the two guidance modes and the QR code entry into each procedure (App Store).
  • Since I wasn’t involved in testing or launch, I don’t have test results or usage data.

What I took from it

  1. Understand the current state before you start
    Teams that come to the design center usually have a clear goal and a competitor they’re looking at. But bringing a competitor’s approach into your own product raises technical and market issues, and differences between users in each region. Weighing all of these before proposing a solution is what helps the project reach its goal.
  2. A complete design system gives under-resourced teams something to build on
    The more complete the components, the more a team without enough design resources has to work from, and the more the company’s products stay at the same baseline. On this project, I spent a lot of time checking with the GUI team, and designed new components following the guidelines.
  3. Clarify regulations and regional differences, and stay close to the PM
    Understanding regulations and regional differences first is what makes it possible to optimise the whole flow. That takes good communication with the PM, which is how the team delivered efficiently in a short time.