#1 Keeping consistency across platforms
Designed for both LTR (English) and RTL (Farsi) languages by mirroring layouts where needed to improve readability and user experience, while ensuring consistency across the web app, admin panel, and website despite directional and numeric challenges.

RTL and LTR languages

To ensure a consistent experience and improve usability, I implemented the Ant Design System and its JavaScript library, customizing components to fully support RTL languages. Below are some of the adapted UI elements from the system:

Appetized UI kit in a glance
#2 Designing for Scalability & Maintainability
The product vision included future expansion into food delivery and retail, so I developed a scalable, adaptable information architecture to support growth from day one.

Digital menu information architecture

Menu builder information architecture
Additionally, I implemented a hybrid component naming method to improve scalability and maintainability.

Hybrid component naming for scalability
#3 Integrating with Existing Admin Panel Backend
Due to time constraints and pre-existing backend and frontend development, the core menu creation flow couldn’t be altered. I enhanced the process by implementing minor but impactful improvements to boost usability without disrupting the system. Here are some of them:
🟢 Enabled adding multiple categories and items to a menu simultaneously, replacing the previous one-by-one process.
🟢 Allowed editing or adding of categories and item details directly during menu editing, which was not possible before.
🟢 Added a dashboard with plan and billing management.

Previous dashboard

Current dashboard with export report feature
🟢 Improved color accessibility to ensure better usability for all users.
🟢 Introduced key features including menu scheduling, image support, QR codes, descriptions, preview mode, multi-language support, and the ability to disable or duplicate each category and item.

Previous menu builder

Current menu builder supports direct editing and adding of categories and items
#4 Working as a Sole Designer
I was the only designer on a team of three developers, a product manager, and a marketer. To maintain design quality, I incorporated some methods to overcome the lack of senior design support.
🟢 Held regular design critique sessions with the team.

Team members' feedback
🟢 Conducted benchmarking by analyzing weaknesses in digital menu competitors, such as cluttered interfaces, limited customization, and poor multi-language support.
Used common design common practices including clear navigation, brand customization, and accessible color schemes to address these gaps and enhance user experience.

Appetized Competitors
🟢 Engaged with UX design communities on Telegram, Discord, and Slack for feedback and support.
#5 Improving Collaboration & reducing time to demo by 20%
As a small but growing team, we needed new processes to save time, boost efficiency, and streamline communication to meet our goals.
Challenges
❓ Vague task definitions, unclear prioritization, and inaccurate time estimates.
❓ Gaps in information flow and verbal communication causing misunderstandings.
❓ Long demo cycles due to the tendency to deliver fully polished features before review.
Solution
Drawing on my experience with Agile framworks, I introduced Scrum practices to improve collaboration. Within one month, we reduced demo time by 20%. The approach included:
✅ Facilitating a team workshop to identify collaboration issues and brainstorm solutions.
✅ Prioritizing issues by impact and effort.
✅ Starting with small changes and iterating based on feedback.
✅ Holding regular feedback sessions to evolve our Agile process and ensure team involvement.