Loading
About the Project

Tourism Designed for Both Sides of the Journey

Ameen is a tourism platform designed for two audiences at once — the traveller looking to book a hotel or tour, and the hotel or tour operator who needs to manage their listings, reservations, and revenue. We handled the complete UI/UX design for both sides of the product.

The Traveller Experience

The customer-facing app lets users discover and book hotels and guided tours across Iraq and internationally. The design prioritises ease — from browsing destinations to completing a booking in as few taps as possible.

  • Hotel booking — search by location, date, and room type with clear availability and pricing
  • Tour booking — browse curated tours with itineraries, inclusions, guide details, and group sizing
  • Iraq & international — the platform covers domestic destinations across Iraq as well as international travel packages

The Provider Dashboard

On the other side of the platform, hotels and tour operators get a dedicated management interface. Every design decision here was made for operators who may not be deeply technical — clarity and speed of task completion were the primary goals.

  • Listing management — create and update hotel rooms, pricing, availability calendars, and tour packages
  • Reservation oversight — view incoming bookings, confirm or reject requests, and track occupancy
  • Revenue visibility — clear financial summaries so operators know exactly what they're earning

The Design Challenge

Designing for two completely different user types — a casual traveller and a hotel manager — within one coherent product required two distinct design languages that still feel like they belong to the same brand. The traveller side is warm and discovery-driven; the dashboard is clean, dense, and task-focused.

  • Hotel Search & Booking
  • Tour Package Booking
  • Domestic & International Destinations
  • Hotel Management Dashboard
  • Tour Operator Management Dashboard
  • Availability Calendar Management
  • Reservation Confirmation & Tracking
  • Revenue & Occupancy Summaries
  • Room & Package Listing Editor
  • Booking History for Travellers
Ameen

How It Was Built

Our process
01 .
Research & User Definition

Conducted separate research sessions for both user types — travellers and operators. Mapped their goals, pain points, and workflows before a single screen was designed. The two audiences have almost nothing in common, so the research phase was essential to avoid building one product that works poorly for both.

02 .
Information Architecture

Structured the platform into two clearly separated experiences — the consumer app and the provider dashboard — with a shared design system underneath. Defined navigation, content hierarchy, and user flows for every major task on both sides.

03 .
Wireframing & Prototyping

Built low-fidelity wireframes for every core flow: hotel search, tour browsing, checkout, booking management, and dashboard reporting. Iterated on the booking flow specifically until it reached the minimum number of steps possible without losing clarity.

04 .
Visual Design & Design System

Applied the final visual language across all screens — creating a component library that covers both the warm, discovery-focused traveller UI and the efficient, information-dense operator dashboard, keeping them visually consistent while serving different purposes.

Ameen preview
Project Insights

Behind the
decisions we made.

Designing for Two Opposite Users

The traveller wants inspiration and simplicity — large imagery, easy filtering, and a frictionless path to booking. The hotel manager wants density and control — tables, calendars, and quick access to data. Serving both within the same product without splitting the brand was the core design problem. The solution was a shared component library with two distinct usage modes: one expressive, one functional.

The Booking Flow Iterations

The hotel and tour booking flows went through six major iterations. The original designs had too many steps — users had to make too many decisions before they could confirm a booking. We progressively collapsed screens, surfaced defaults, and deferred non-essential choices until after the booking was confirmed. The final flow gets a user from search to confirmed booking in four steps.

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Get In TouchStar

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us

Contact Us