Solution: i integrated gamification elements to make user interaction more engaging and motivating. For example, during registration, a small game responded to user actions—progress depended on their steps and reset if they went back.
Problem: it was necessary to engage users accustomed to traditional paper-based request processing and make the experience more appealing.
User Engagement
Solution: i developed a flexible, block-based interface structure to facilitate the easy addition of new features. For adaptability, I used a fluid layout, ensuring future scalability and usability.
Problem: while designing the MVP, I needed to account for the product’s expansion into an ecosystem, which required a scalable page structure.
System Scalability
Solution: i mapped out user accounts and their interactions, considering role hierarchy and points of intersection. I developed status change flows, request processing, and notification systems to visually represent process logic.
Problem: it was necessary to design scenarios for different roles: clients (private and business), technicians, administrators, and the in-store application. Each role had its own functions, and actions in one account affected others, complicating the interaction logic.
Interaction Logic
Solution: i analyzed the differences between LTR and RTL interfaces (using Wolt, Yango, and other services as examples), developed adaptation guidelines, and created a developer guide that included universal components.
Problem: until now, I had only designed LTR interfaces, and I needed to understand how to adapt the design for RTL versions, considering mirrored elements, component size optimization, and the impact of text direction on interface perception.
Support for Language Versions (RTL & LTR)
Key Challenges and Solutions