This redesign focused on three main goals:
(1) Reduce ambiguity in how the denoising works,
(2) Offer users both default simplicity and advanced control,
(3) Build user confidence in the system through clear status feedback and shareability.

1. Enhance real-time noise reduction visualization

Remove the play button from the thumbnail.Instead, use clear status labels such as “Processing,” “Edit,” or “Complete.”

• Design Rationale:
  ‍I observed that the presence of a play icon suggested the file was ready for preview, creating false expectations. In reality, the noise reduction might still be processing or only partially complete. Removing the play button ensures the UI reflects the actual system state and guides users more accurately.
• Hypothesis:
  ‍If I remove the misleading play icon and replace it with explicit status labels, users will:

• Better understand the current file state.
• Feel more confident that the noise reduction is working.
• Be more likely to proceed with the next step (edit, download) without hesitation.

• Trade-off:
  ‍I considered keeping the play button to allow users to preview audio directly. However:

• It risked playing the original, unprocessed audio, which could cause users to think the tool failed.
• Clarifying this distinction through tooltips or dialogs added cognitive load and interrupted flow.

We prioritized clarity and trust over offering early playback interaction.

Noise Control: Combining Presets with Custom Flexibility

• Design Rationale:
  A gray but draggable slider allows users to see the preset noise reduction levels (e.g., voice vs. background mix) while maintaining control to fine-tune. This approach balances transparency and customizability, giving users clarity on system logic and freedom to personalize.
• Hypothesis:
  Users will better understand how each preset works and feel more in control when they can adjust values directly. This will lead to increased trust in the product and reduced frustration when outcomes differ from expectations.

• Trade-off:
  ‍The gray appearance may initially suggest the slider is disabled, potentially causing momentary hesitation. However, I offset this by ensuring instant visual feedback—once the slider is touched, the label switches to "Custom," reinforcing interactivity and system response.

2. Unify the app and web user experience. Reduce the learning curve and increase user retention rate.

Add the edit function of the file name.

Make the prime icon the same between different platforms.

I refer to Canva and Google Slides which are popular editing tools, and I found that they use tooltips to help users understand the icon's function.

To decrease the user's learning curve, I follow their solution. When users hover over the background and voice icon, a tooltip notification appears above the icons on the web. Moreover, as for the mobile version,  it will show the tooltip for several seconds when the users jump to this page.

When users click the different buttons, a tooltip notification appears on the video to inform the user of the currently used filter.

Validation:

This solution aligns with established UX best practices (e.g., Nielsen Norman Group’s heuristics).

3. Add real-time autosave notifications (Autosave Toast) → Reducing operational uncertainty.

• Design Rationale:
  ‍Inspired by tools like Google Docs and Canva, we introduced a real-time autosave toast that appears as soon as editing begins. This lightweight yet visible feedback mechanism is designed to reduce operational uncertainty, especially for users unfamiliar with the system. Unlike mature tools (e.g., Figma) that rely on user trust, our early-stage product needed explicit, reassuring system feedback to build confidence from the start.
• Hypothesis:
  ‍I believe that by clearly communicating autosave status in real time, users—especially new ones—will:

• Feel safer and more confident making edits
• Form an accurate mental model of how the system handles saving
• Avoid confusion or anxiety over potential data loss

• Trade-off:
  ‍Compared to a silent autosave model (like Figma), visible toast notifications introduce more UI surface noise and may appear redundant to advanced users. However, for our primary audience—many of whom are new to the tool—clarity outweighs minimalism. I mitigated interruption by keeping the toast brief, non-blocking, and positioned in a low-visibility zone.

4. Balancing Brand Showcase with User Needs: Optimal vs. Custom Denoising Ratios

"In testing, 4 out of 5 users said they preferred sharing their custom result over the system-recommended one."

• Design Rationale:
  ‍To balance brand consistency with user expression, I introduced a toggle feature that allows users to switch between the system-recommended “Optimal” denoising ratio and their personally adjusted “Custom” settings. This design supports two different priorities:

• The company’s goal of promoting algorithmic excellence through the cleanest output.
• The user’s desire to share a version that aligns with their creative intent—be it preserving ambient nuance or vocal warmth.
  By clearly displaying the active ratio and offering switching flexibility, I provide both transparency and autonomy.

• Hypothesis:
  ‍I believe that giving users control over what version gets shared will:

• Increase their trust in the system and willingness to share outputs publicly
• Reduce dissatisfaction caused by mismatched expectations
• Strengthen the product’s credibility among creators who value customization

• Trade-off:
  ‍Compared to forcing a fixed “Optimal” output for all shares, this toggle introduces a more complex UI decision point.
  However, I found that:

• The toggle is simple and lightweight in design
• Users feel more empowered and in control
• Technical implementation requires no algorithmic recalculation, making it a low-risk addition
  I considered an alternative that only allowed “Optimal” sharing, but it limited personal agency and backfired during testing.