FindMotos

FindMotos

FindMotos

A bilingual vehicle marketplace tailored for the Egyptian market.

A bilingual vehicle marketplace tailored for the Egyptian market.

A bilingual vehicle marketplace tailored for the Egyptian market.

Summary

Summary

Project Overview

Project Overview

FancyMeds (previously Qyral) is a U.S.-based telehealth platform and licensed distributor of GLP-1 weight-management medication (Semaglutide and Tirzepatide) through partner pharmacies operating nationwide. The business required a complete brand repositioning and a redesigned digital experience to make the treatment process feel clear, trustworthy, and approachable for everyday patients.

Problem Statement

Problem Statement

Several gaps was identified in existing local vehicle-listing apps:

  • Cluttered interfaces and non-intuitive navigation slowed down browsing.

  • Poor filtering and sorting made it difficult for users to find relevant listings.

  • Lack of proper Arabic interface support (RTL layouts, alignment, typographic calibration).

  • Limited trust signals, outdated visuals, and inconsistent UI patterns reduced user confidence.

  • Users struggled to contact sellers quickly due to unclear CTA hierarchy.

Additionally, the app needed to be delivered quickly, within a defined budget, while meeting modern usability and accessibility standards.

Client

Client

Private

Services

Services

User Research

Wireframing

Visual Brand Direction

Design System Development

UX/UI Design

A/Bn Testing

Goal

Goal

The main objective was to create a simple, fast, and conversion-oriented mobile app designed for the Egyptian market. The project focused on:

  • Building an intuitive browsing and posting experience

  • Supporting Arabic and English interfaces (RTL & LTR)

  • Improving listing discovery through powerful filters and sorting

  • Providing clear, high-contrast UI with strong visual guidance

  • Ensuring quick access to seller contact options

  • Establishing a scalable design system for future web expansion

My role

My role

As the UX/UI Designer, I led the entire product creation process. I Conducted UX research and competitive audit, I mapped user journeys and defined ideal task flows, designed wireframes and multi-variant screen concepts (A/B/n), I’ve also built a complete Design System with usage guidelines. Simple brand logo was also created (the client wanted text logo only). Along with creating mockups, the design system was being updated. After performing usability studies, I’ve continued with the app design improvements. At last, I’ve prepared interactive prototypes and handed off assets to development. Throughout the entire process I’ve stayed in touch with the Client, offerign UX consulting and rapid iteration.

Impact

Impact

The final product delivered:

  • A modern, clean, and culturally appropriate mobile app for vehicle buyers and sellers in Egypt

  • A streamlined filtering, searching, and listing experience

  • Clear bilingual support, including RTL-optimized layouts

  • Strong usability improvements through better semantics, contrast, icons, and visual hierarchy

  • A scalable foundation for future features and a desktop platform

  • A polished UI that increased trust and reduced cognitive effort across the app

Design process

STEP I

STEP I

Kickoff & Brand Exploration

Kickoff & Brand Exploration

The project began with in-depth discussions with the client to clarify business goals, content structure, and expected timeline.

I created the first draft of the FindMotos logo — a minimal automotive-inspired symbol.

The logo was however rejected, as the client wanted to keep the brand identity strictly typographic for the first release (using the name “FindMotos” only).

The project began with in-depth discussions with the client to clarify business goals, content structure, and expected timeline.

I created the first draft of the FindMotos logo — a minimal automotive-inspired symbol.

The logo was however rejected, as the client wanted to keep the brand identity strictly typographic for the first release (using the name “FindMotos” only).

Key elements:

Key elements:

  • target audience characteristics

  • initial feature priorities

  • platform constraints

  • success metrics

  • target audience characteristics

  • initial feature priorities

  • platform constraints

  • success metrics

STEP II

STEP II

UX Foundations: Research, Personas, User Flows, Wireframes

UX Foundations: Research, Personas, User Flows, Wireframes

Based on local market expectations and patterns from popular Egyptian marketplaces, I developed a solid UX foundation. This included Personas representing both Arabic- and English-speaking users, user flows for searching, filtering, posting, and contacting sellers, wireframes mapping key screens with minimal complexity and local behavior insights (e.g., strong preference for direct phone contact)
The focus was on ensuring fast task completion, predictable navigation, and clarity in dense content (vehicle data).

Based on local market expectations and patterns from popular Egyptian marketplaces, I developed a solid UX foundation. This included Personas representing both Arabic- and English-speaking users, user flows for searching, filtering, posting, and contacting sellers, wireframes mapping key screens with minimal complexity and local behavior insights (e.g., strong preference for direct phone contact)
The focus was on ensuring fast task completion, predictable navigation, and clarity in dense content (vehicle data).

Key elements:

Key elements:

  • Competitive audit of local & international marketplace apps

  • Defined bilingual user personas (Arabic & English speakers)

  • Created user journey maps for buyers & sellers

  • Designed user flows for core actions: search, filter, add listing, contact seller

  • Developed low-fidelity wireframes to validate structure

  • Established app foundations for a smooth, predictable mobile experience

  • Competitive audit of local & international marketplace apps

  • Defined bilingual user personas (Arabic & English speakers)

  • Created user journey maps for buyers & sellers

  • Designed user flows for core actions: search, filter, add listing, contact seller

  • Developed low-fidelity wireframes to validate structure

  • Established app foundations for a smooth, predictable mobile experience

User flow charts

User flow charts

User personas

User personas

Wireframes examples

Wireframes examples

STEP III

STEP III

Design System, First Mockups & Micro-Prototypes

Design System, First Mockups & Micro-Prototypes

Once wireframes were approved, I’ve created extended Design System including visual styles, typography, spacing systems, iconography and others. Next step was designing the first high-fidelity mockups and microprototypes, in order to validate dropdown behaviors, filtering transitions, gallery interactions, scrolling rules and sticky bars and bottom sheet interactions
These quick prototypes ensured early functionality validation before building full flows.

Once wireframes were approved, I’ve created extended Design System including visual styles, typography, spacing systems, iconography and others. Next step was designing the first high-fidelity mockups and microprototypes, in order to validate dropdown behaviors, filtering transitions, gallery interactions, scrolling rules and sticky bars and bottom sheet interactions
These quick prototypes ensured early functionality validation before building full flows.

Key elements:

Key elements:

  • Designed first high-fidelity screens for core flows

  • Created microinteractions prototypes (dropdowns, filters, scroll states)

  • Explored layout styles and typography optimized for both languages

  • Selected color palette with strong contrast and semantic clarity

  • Tested early visual ideas to refine direction

  • Designed first high-fidelity screens for core flows

  • Created microinteractions prototypes (dropdowns, filters, scroll states)

  • Explored layout styles and typography optimized for both languages

  • Selected color palette with strong contrast and semantic clarity

  • Tested early visual ideas to refine direction

Initial mockups examples

Initial mockups examples

Initial prototype

Initial prototype

STEP IV

STEP IV

Multi-Variant A/B/n Testing 

Multi-Variant A/B/n Testing 

To determine the most effective UI, I created three distinct versions of each major screen.
Each variant explored different layout structures, hierarchies, and visual accents. A/B/n testing allowed us to compare readability of vehicle data, scanability of listing cards, clarity of CTA positioning, visual weight distribution and general sense of trust and modernity. The best-performing versions were selected for final refinement.

To determine the most effective UI, I created three distinct versions of each major screen.
Each variant explored different layout structures, hierarchies, and visual accents. A/B/n testing allowed us to compare readability of vehicle data, scanability of listing cards, clarity of CTA positioning, visual weight distribution and general sense of trust and modernity. The best-performing versions were selected for final refinement.

Key elements:

Key elements:

  • Designed 3 variations for all key screens

  • Conducted A/B/n tests to compare structure, readability, and hierarchy

  • Evaluated CTAs, information grouping, and scanning speed

  • Identified most intuitive UI models for local market

  • Selected winning variants for final polish

  • Designed 3 variations for all key screens

  • Conducted A/B/n tests to compare structure, readability, and hierarchy

  • Evaluated CTAs, information grouping, and scanning speed

  • Identified most intuitive UI models for local market

  • Selected winning variants for final polish

ABn Testing Examplary Mockups

ABn Testing Examplary Mockups

STEP V

STEP V

Final UI Polish & RTL Conversion

Final UI Polish & RTL Conversion

Following multiple screen iterations and discussions with the client, the final versions have been approved for implementation.
After finalizing LTR designs, the entire interface was adapted to Arabic RTL.

This required more than flipping layouts — text, icon direction, spacing, and visual hierarchy needed cultural adjustment. The RTL conversion included mirroring layouts, shifting interactive elements to the right side, adjusting arrows & icons, recalibrating vertical rhythm for longer Arabic labels, refining typography for Arabic readability. This phase ensured the Arabic version felt native — not translated.

Following multiple screen iterations and discussions with the client, the final versions have been approved for implementation.
After finalizing LTR designs, the entire interface was adapted to Arabic RTL.

This required more than flipping layouts — text, icon direction, spacing, and visual hierarchy needed cultural adjustment. The RTL conversion included mirroring layouts, shifting interactive elements to the right side, adjusting arrows & icons, recalibrating vertical rhythm for longer Arabic labels, refining typography for Arabic readability. This phase ensured the Arabic version felt native — not translated.

Key elements:

Key elements:

  • Full LTR → RTL conversion

  • Mirrored iconography and layout logic

  • Right-aligned labels and recalibrated typography

  • Adjusted spacing for Arabic text length

  • Improved RTL usability based on cultural patterns

  • Finalized bilingual mockups for development

  • Full LTR → RTL conversion

  • Mirrored iconography and layout logic

  • Right-aligned labels and recalibrated typography

  • Adjusted spacing for Arabic text length

  • Improved RTL usability based on cultural patterns

  • Finalized bilingual mockups for development

Examplary mockups, English versions

Examplary mockups, English versions

Examplary mockups, English versions

Examplary mockups, English versions

Examplary mockups, Arabic versions

Examplary mockups, Arabic versions

STEP VI

STEP VI

Developer Handoff & Future Growth Planning

Developer Handoff & Future Growth Planning

Following multiple screen iterations and discussions with the client, the final versions have been approved for implementation.
After finalizing LTR designs, the entire interface was adapted to Arabic RTL.

This required more than flipping layouts — text, icon direction, spacing, and visual hierarchy needed cultural adjustment. The RTL conversion included mirroring layouts, shifting interactive elements to the right side, adjusting arrows & icons, recalibrating vertical rhythm for longer Arabic labels, refining typography for Arabic readability. This phase ensured the Arabic version felt native — not translated.

Following multiple screen iterations and discussions with the client, the final versions have been approved for implementation.
After finalizing LTR designs, the entire interface was adapted to Arabic RTL.

This required more than flipping layouts — text, icon direction, spacing, and visual hierarchy needed cultural adjustment. The RTL conversion included mirroring layouts, shifting interactive elements to the right side, adjusting arrows & icons, recalibrating vertical rhythm for longer Arabic labels, refining typography for Arabic readability. This phase ensured the Arabic version felt native — not translated.

Key elements:

Key elements:

  • Full LTR → RTL conversion

  • Mirrored iconography and layout logic

  • Right-aligned labels and recalibrated typography

  • Adjusted spacing for Arabic text length

  • Improved RTL usability based on cultural patterns

  • Finalized bilingual mockups for development

  • Full LTR → RTL conversion

  • Mirrored iconography and layout logic

  • Right-aligned labels and recalibrated typography

  • Adjusted spacing for Arabic text length

  • Improved RTL usability based on cultural patterns

  • Finalized bilingual mockups for development

© 2025 Urszula Szumlas | All Rights Reserved

© 2025 Urszula Szumlas | All Rights Reserved

© 2025 Urszula Szumlas | All Rights Reserved

© 2025 Urszula Szumlas | All Rights Reserved

© 2025 Urszula Szumlas | All Rights Reserved