Problems

1. Unclear state

1.1. Account Subscription/Trial Status:  
It doesn’t display the plan users buy, so users cannot confirm their recent status.

1.2. Users are not sure if the post-noise reduction video is the output of noise reduction or the original video.

User Experience Challenges
‍
Noise reduction effectiveness varies depending on the video. Some files show little difference before and after processing, making it hard for users to perceive its impact.
This may lead users to believe that the product is ineffective, potentially resulting in user loss.

Voice and Background Sound Adjustment
‍
If both voice and background sound are set to the same value, no reduction occurs, which may further reinforce the perception that the product is not working as expected.

Customization & Adjustability
‍
In the APP, the Voice/Noise Ratio Bar is only available in the Custom mode.
On the Web, users can adjust the settings for each default preset.

Since the product is new to the market, users are still exploring its functionality. Some videos naturally have minimal noise, making the effects less noticeable.
Without a clear way to demonstrate the feature’s impact, users might misunderstand its effectiveness.

Users said if a large number of files need to be downloaded, it is preferable to rename the files during the editing process for easier organization after downloading. Renaming the files only at the time of downloading would require individually checking each file, which is more cumbersome.
‍
Currently, it can only be modified on the APP.

Inconsistent default icons and premium badges (crown icon) between the APP and the Web.

While users edit the file, they are not sure whether the file will be saved with the currently adjusted background sound and voice ratio or not.

When users complete adjusting the audio and share the link with others, they anticipate the shared page will reflect their real-time noise reduction settings.

However, instead of displaying the user's specific adjustments, we provide a before-and-after comparison showcasing our noise reduction capabilities. This approach allows us to highlight our expertise in noise reduction on this webpage.

When sharing a link, the default setting of the dropdown menu is set up in "private" which doesn't align with the mindset of users who already want to share it with others.

Solution

1. Make the usage status clear

‍Option A (Chosen): Disable the purchase button and show a “purchased” status after users buy the product
Option B (Not Chosen): Keep the purchase button active regardless of buying status, and notify users only after clicking

Why A over B?

• Clearer status feedback: Disabling the button provides immediate visual feedback that the product has already been purchased, reducing confusion.
• Reduces unnecessary interactions: Prevents users from clicking a button that would result in an error or redundant flow.
• Aligns with common UI patterns: Most SaaS platforms disable action buttons for purchased or unavailable items to communicate system state effectively.

Collaboration & Constraints

• Discussion with PM and engineers: PM emphasized the importance of reducing customer service inquiries caused by unclear purchase status. Engineers confirmed that checking the purchase record in real-time and updating the UI state dynamically was technically feasible.

Validation

• This pattern was validated by comparing with UX benchmarks from subscription-based services (e.g., Adobe, Zoom).
• Post-release feedback showed a noticeable drop in “accidental re-purchase” attempts and helped reduce user support tickets regarding purchase status.

Option A (Chosen): Remove the play button from the thumbnail
Option B (Not Chosen): Keep the play button to allow quick preview of the video/audio

Why A over B?

• Avoid confusion: Users might mistakenly believe the play button previews the noise-reduced version. However, it actually plays the original, which can lead to misunderstanding about whether noise reduction has been applied.
• Clearer process communication: Status labels such as “Processing” or “Edit link” are more effective in indicating the current state of the file than a play icon.

Collaboration & Constraints

PMs raised concerns that confusion around the play button could reduce user trust in the product’s effectiveness. The technique is feasible.

Validation

Ppost-launch feedback indicated a decrease in support tickets and user confusion regarding the noise reduction status.

Enhance real-time noise reduction visualization

Final Design ChoiceEach preset filter (e.g., "Clear," "Natural," "Background Focus") displays a gray slider representing the fixed ratio of voice to background sound. Although the slider appears inactive (gray), users can still drag it.If the user adjusts the slider, the system will automatically switch to the "Custom" filter, indicating that they have left the preset and entered a personalized configuration. This balances clarity, flexibility, and user control.

We chose this design to maintain transparency, offer flexible interaction, and reduce the risk of users misjudging the product’s effectiveness.

Collaboration with PM/engineers or constraints:

PM feedback: Strongly supported the design. It helps prevent users from wrongly assuming the product doesn’t work just because they can’t hear an obvious difference in their file.
‍Engineering feedback: Confirmed that monitoring slider interaction and auto-switching to the "Custom" button is straightforward to implement within current timelines and codebase.

Technical / Business Constraints:

Business: Some users were misunderstanding the product’s denoising capability when their uploaded files had minimal voice/background contrast. This design helps us visually prove that each filter is indeed different, even if the auditory difference is subtle.
‍
Technical: Implementing a gray, still-interactive slider with an auto-switch trigger is lightweight and fits well with existing architecture.

Validation:

In cases where users couldn’t hear a major difference, they still recognized the visual change, which helped them realize that the issue was likely with their input file—not with the product itself.
This design aligns with key UX principles:
‍Visibility of System Status – Users can see which filter and ratio they’re using.
‍User Control and Freedom – Users are free to explore and modify settings without rigid constraints.
‍Progressive Disclosure – Simpler options first, more control when needed.

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

We added a real-time autosave toast notification that appears before editing begins, clearly communicating to users that the system has an autosave feature—inspired by Google Docs and Canva, but with improved visibility.
Additionally, when autosave fails (e.g., due to connection loss), we show a "disconnected" toast to alert users that editing will be disabled.

We chose this approach because our product is new, and unlike mature platforms (e.g., Figma), we cannot rely on user familiarity. Instead, we proactively reinforce product trust by clearly showing when autosave is working.

Collaboration with PM and Engineering

PM feedback: Supported the idea that early-stage products need stronger reassurance mechanisms. PM emphasized the importance of onboarding confidence and visibility into system behaviors.
‍Engineering feedback: Confirmed that the toast logic was straightforward to implement. Toast triggers were event-based (on connection + on edit start), and would not introduce performance issues.

Technical / Timeline / Business Constraints

Technical: Implementing autosave itself was already part of the core logic. The toast system was lightweight and used the same toast component for reuse.
Business: As a new tool in the market, building trust through clear system status is crucial. We cannot assume that users know autosave is present unless we visibly confirm it.

Validation

UX benchmark reference:
Google Docs and Canva show proactive system feedback.
Figma only shows a toast when autosave fails or changes are unsaved—this works for experienced users but may create uncertainty for new ones.

This decision supports Nielsen Norman Group’s usability heuristic: “Visibility of system status”—users should always know what the system is doing in the background, especially in autosave-critical environments.

Allow users to switch between the optimal and customized denoising ratio, and display the current ratio status to meet both company and user expectations while enhancing output efficiency.

We chose Option A to balance simplicity and control, and to help users understand, trust, and confidently share their processed results.

Collaboration with PM and Engineering

PM feedback: Supported the dual-track approach—fast publishing for casual users, and adjustable settings for power users. It aligns with the goal of improving overall creation speed while still offering depth when needed.

‍Engineering feedback: Technically feasible within the current system. The toggle logic and ratio value display were simple front-end tasks. Changing the default sharing setting required only a minor config update.

Technical  / Business Constraints

Technical: The toggle and ratio display are UI-based, reading pre-set or user-defined values—no need for complex recalculations. Public sharing default is a config-level change.

Business: The optimal ratio ensures a consistent outcome, aligning with brand standards.
‍Customized mode empowers prosumers, increasing perceived control.
‍Defaulting to public sharing increases exposure, and encourages virality through ease of sharing.

Validation

During internal testing, users clearly understood the difference between “optimal” and “custom” modes and appreciated seeing the ratio update when toggling.Users described the one-click public sharing flow as "fast and frictionless," making them more willing to share output.The feature supports UX best practices:
Visibility of System Status – Users know what ratio is being applied.
Recognition over Recall – Users don’t need to memorize their last choice—they see it directly on screen.

Result