Designed the Batch Upload feature on the Meituan Livestream Assistant website, improving efficiency and streamlining workflows.
Meituan
2 Weeks
UXUI Designer
MasterGO
BACKGROUND
When streamers hosted lucky draws with physical prizes, they had to mail the prizes and enter tracking numbers on the Meituan Livestream Assistant website so winners could track their deliveries. However, each number had to be entered individually, with the interface refreshing after every submission. This process was complicated, inefficient, and error-prone, since a single livestream could involve dozens or even hundreds of prizes.
CHALLENGES
Usability
Ensure the workflow is simple and intuitive for streamers.
Accuracy
Reduce mis-uploads through clear guidance and a thoughtfully designed process.
Error
Provide clear feedback and actionable next steps for invalid or missing tracking numbers.
History
Give streamers access to previous uploads for quick review.
USER FLOW
To balance ease of use with effective error prevention and handling, I explored two user flows and selected the better approach.
The first option was simple and easy to follow, but had major drawbacks: long review times for large files, no way to re-upload if the wrong file was submitted, and difficulty predicting errors since file format and information were checked together. The second flow was slightly more complex but reduced review time, allowed re-uploads before confirmation, and made it easier for users to anticipate and correct errors by checking file format and information separately. Therefore, I chose the second flow.
HIGH FIDELITY
KEY TAKEAWAY
In this project, I designed a new feature based on real user pain points to solve the inefficiency of tracking number uploads. The solution reduced manual input time by 80% and significantly improved the user experience with the Meituan Livestream Assistant website. After launch, 70% of streamers adopted it.
Good UX is not only about making a flow simple but also about ensuring users can complete their tasks as intended through a frictionless, error-free journey. In this project, I chose the second user flow even though it was more complex than the first, because it worked better at preventing errors and supporting error handling, ultimately creating an efficient and reliable happy path.