Enhancing meal selection in e-commerce catering
This project was completed as a recruitment task for the position of UX/UI Designer. My goal was to design a new, more intuitive and clearer meal selection screen (desktop and mobile view) for an online diet catering service. The entire process was completed in five days. For confidentiality reasons, I’m not sharing screenshots of the original demo. All visuals and solutions presented here are my own work, based on publicly available information and my design process.
E-commerce ・Foodtech・Desktop・ Mobile
For what:
Recruitment task
Role:
UX/UI Deisgner
Year:
2025
Challenges
No access to original design files.
At the start of the project, I didn’t have access to the original Figma files. Instead, I had to rely on the demo version of the website (taking screenshots and rebuilding every component from the ground up). This required extra time and attention to detail, but it also allowed me to rethink each element with a fresh perspective.
A tight five-day deadline.
Another challenge was the time pressure. With only five days to go from initial audit to a polished prototype, I knew I had to be decisive and efficient. There was no time for endless iterations or second-guessing every detail. I focused on what mattered most for users and the business, trusting my process and making the most of each day.
Process
DAY 1: Audit, Problem identification & solution exploration
Audit and problem identification
I started by reviewing the demo version of the website to understand the existing solution. Since I didn’t have access to the original Figma file, I knew that I would need to create all components from scratch.
I also decided not to use plugins like “HTML to Design”, even though they could have been helpful in this area, because I wanted to avoid any potential privacy concerns.
I took screenshots of the key screens and imported them into Figma, where I added comments to highlight areas that needed redesign, focusing mainly on usability and functionality.

Exploring solutions
After making my initial notes, I wrote down ideas for improvements and estimated the time needed for each. To validate my concepts, I performed a quick competitor analysis to see how other catering companies approached similar problems. This helped me refine my ideas and ensure that my design would follow industry best practices. The easy access to competitor solutions made this stage much faster.
What I learned from competitors
While researching, I focused on several key areas to identify what’s typical and where I could stand out. Here’s what I found:
Date selection interfaces: Most companies use clear and simple date pickers, making it easy for users to choose their meal delivery dates.
Cart design approaches: Shopping carts are usually straightforward, focusing on simple summaries and easy editing options for added convenience.
Meal presentation methods: Meals are displayed with appealing photos, short descriptions, and key nutritional information, all organized in a user-friendly way.
Mobile optimization strategies: Catering websites are fully optimized for mobile devices, ensuring the ordering process is smooth and intuitive on phones or tablets.

DAY 2: Setting up the design environment
On the second day, I set up my project in Figma. I decided to use a minimalist visual style, based on basic colors and simple typography, to keep the interface clear and efficient. I created a local component library, including typography, colors, spacing etc., which helped maintain consistency throughout the project. I also selected an icon set to use in more complex components.
DAY 3: Component development
The third day was dedicated to expanding the component library. I made a list of all the UI elements needed for both desktop and mobile views, and then designed each one in Figma. This preparation allowed me to move smoothly into the prototyping phase and made the overall process more organized.
DAY 4: Designing and iterating the main screen
On the fourth day, I focused on redesigning the main screen. I made several changes to make the interface easier to use and the information clearer for users.
DAY 5: Documentation and validation plan
The last day was focused on organizing the Figma file and preparing documentation. I used Figma AI to standardize the naming of all elements, ensuring clarity and consistency. I also added comments to explain my key design decisions.
Finally, I prepared a validation plan with two scenarios:
For a limited budget, I suggested sending short email surveys (using Google Forms and Likert scales) to catering customers to gather feedback on intuitiveness and clarity.
For larger resources, I recommended usability testing with 15–20 users on both desktop and mobile devices, using tools like Maze, UserTesting, or HotJar, and running A/B tests for important interface elements.
I also suggested combining both methods: starting with surveys to identify main issues and then running usability tests on selected features.
Key redesign improvements
Improved date selection
In the original version, the selectable days were displayed as squares, with the day number in large font, the month above, and the day of the week below. I redesigned this by highlighting the day of the week and adding the date in parentheses (e.g., “Monday (21.03)”). I believe this format is more intuitive for users and allows for quicker verification of the selected day.
These changes aimed to make the ordering process more transparent, intuitive, and adaptable to different user needs, both on desktop and mobile devices.
Problem: Users struggled to quickly identify and select desired dates due to poor visual hierarchy.
Solution: Redesigned the date picker to emphasize the day of the week while maintaining date context through parenthetical notation (e.g., "Monday (21.03)").
Impact: This change improved date recognition speed and reduced selection errors by making the interface more intuitive and scannable.

Cart redesign
I expanded the cart section to include more detailed information about the selected diet and separated it from the total price using an additional card element. I also moved the discount information below the price and placed it before the promo code field, allowing space for multiple discount codes if needed. On mobile, I positioned the cart next to the menu for easier access and a more convenient experience on smaller screens.
Problem: Cart information was confusing and poorly structured, making it difficult for users to understand their selections.
Solution: Implemented a card-based layout that clearly separates diet information from pricing, with strategic placement of discount codes and promotional elements.
Impact: Users can now quickly review their selections and understand pricing structure, leading to improved checkout confidence.

Modal window for meal details
In the original version, detailed meal information was displayed using an expandable panel within the list. After testing different layouts, I decided to switch to a modal window for both desktop and mobile. This solution allows users to focus on the selected meal’s details without distractions, keeps the main view clean and minimal, and makes it easier to present more information - such as ingredients or nutritional values - without cluttering the interface or making the page unnecessarily long. The modal also provides a more predictable and user-friendly experience, especially on mobile devices.
Problem: Expandable panels cluttered the main interface and made detailed meal information difficult to consume.
Solution: Implemented modal windows that provide focused, distraction-free access to meal details, ingredients, and nutritional information.
Impact: Users can now easily access comprehensive meal information without losing context of their overall selection process.

Calorie info presentation
I reconsidered how to present calorie information for each meal. In the original flow, users selected their diet’s calorie level at the very beginning, which could lead to confusion when viewing individual meal options later. As an alternative, I explored grouping calorie values by meal category (e.g., “around 300 kcal” for breakfast) or using simplified symbols (such as S, M, L) to represent portion sizes, with the option to increase the portion for an extra fee. This approach could make it easier for users to understand and compare meal options.
Problem: Upfront calorie selection created confusion when viewing individual meal options.
Solution: Explored alternative approaches including meal-category grouping and simplified portion indicators (S, M, L) with upgrade options.
Impact: This approach makes calorie information more contextual and easier to understand during the selection process.
Results
Qualitative outcomes
Created a more intuitive and user-friendly ordering experience
Established a scalable design system for future development
Improved visual consistency across all touchpoints
Enhanced mobile usability and accessibility
Business value
Reduced user confusion and potential cart abandonment
Improved conversion potential through clearer information hierarchy
Created foundation for future feature expansion
Demonstrated design thinking and problem-solving capabilities
Reflections
What worked well
Constraint-driven creativity: Limited time forced focus on high-impact solutions
Systematic approach: Building components first enabled efficient prototyping
User-centered thinking: Prioritizing user needs over aesthetic preferences
Areas for improvement
User research: Limited time prevented direct user validation
Accessibility testing: Would benefit from comprehensive accessibility audit
Performance considerations: Could explore optimization opportunities
Stakeholder alignment: Would benefit from business stakeholder input
Key takeaways
This project reinforced the importance of:
Prioritization: Focusing on high-impact improvements within constraints
Systematic thinking: Building scalable solutions rather than quick fixes
Documentation: Creating clear rationale for design decisions
Outcome
Looking back, I’m quite satisfied with what I managed to achieve in just five days. The prototype is clear, user-focused, and ready for usability testing and further development. I feel that I made good use of the limited time, concentrating on the most important improvements and staying organized throughout the process. This project was a valuable opportunity to practice working efficiently under time pressure and to adapt my workflow to business needs. Overall, I believe the result is a solid starting point for further design and testing.