Evolving Registry Sync - Web & Mobile

At a Glance

Internal Project: MyRegistry.com

Role: UX Research, UI Design

Year / Duration: 2024 / ~ 2 weeks

Reporting to: Creative Director

Collaborators: 2 UX Designers

Skills: User Flows, Wireframing, Prototyping

Tools: Figma

Context

User Goals

Clear guidance reduces abandonment

Transparency builds trust and adoption

Strong hierarchy balances usability

Business Goals

Define

Problem Framing

Logged-in desktop users managing registry syncs across multiple stores

need to

quickly see available sync stores, existing connections, and any issues

because

unclear structure and weak visual cues previously made syncing confusing and error recovery hard.

POV

Logged-in web app users managing registry syncs need to quickly understand what can be synced, what is already connected, and whether any issues need attention, the previous page structure and limited visual cues made the experience confusing.

HMW?

How might we restructure the web app sync landing page so users can immediately understand where to sync, which stores are supported, and whether any existing syncs need attention?

Registry owners setting up their registry on mobile

need to

know what is happening during syncing and what action, if any, is required from them

because

long-running or failed syncs without feedback cause confusion and abandonment during setup.

POV

Mobile app users trying to sync an external registry need clear, lightweight feedback about progress and outcomes because syncs can take time or fail, and uncertainty leads users to lose trust, repeat actions, or drop off before completion.

HMW?

How might we provide meaningful, non-intrusive feedback throughout the mobile sync experience so users understand progress, get notified of outcomes, and have clear recovery options when syncing takes longer than expected or fails?

Final User Flow

Prototypes

Mobile App Feedback & UI Refinement

Successful Sync Flow

The successful sync flow focuses on transparency and reassurance during asynchronous syncing. Users receive clear feedback when syncing is delayed and are guided through completion states, including scenarios where a registry syncs successfully but has no items yet, ensuring clarity and confidence throughout the experience.

Sync Failure & Recovery Scenario

The flow addresses sync failures by clearly differentiating between system-related errors and user-correctable issues. Users are guided toward customer support when backend failures occur after a registry match, and provided with recovery options when no matches are found. Delayed failures are communicated transparently to maintain clarity and trust.

Desktop Sync Layout & Interface Refinement

After

Before

Visual Cues & Guidance

For the desktop experience, the focus was on improving clarity and discoverability within the existing sync interface. Contextual UI elements were introduced such as visible warnings when syncing is unavailable to ensure users are informed about system-level issues rather than encountering silent failures. Iconography was added to better signal available actions and encourage syncing, as the previous layout did not clearly communicate where or how to proceed. In addition, the instructional content accessed via the help icon was updated to visually explain the sync process, setting clearer expectations before users begin.

Reflections

The project highlighted how incremental refinements can meaningfully improve complex product experiences. Rather than introducing new functionality, the focus was on strengthening clarity, transparency, and recovery across platforms. Designing around asynchronous behavior and system constraints required balancing technical realities with user expectations. The project reinforced the value of cross-functional collaboration and iterative improvements in evolving an established feature.