Muhammed Shibli

Case study

ID Rooms — Hotel Booking App

Hotel booking with Google Maps discovery and Distance Matrix-powered 'how far is it really' search.

The problem

Hotel booking lives or dies on one question: "where exactly is this, relative to me?" A list of hotels sorted by nothing useful is how users bounce. ID Rooms needed discovery that treats location as the primary feature — not a map bolted onto a list — plus the full booking lifecycle behind it.

What I built

A Flutter booking app where the map is the interface.

  • Map-first discovery. Hotels render on Google Maps with live pricing; users browse the city, not a list. List view exists for the list-minded, but both views share one source of truth.
  • Real distances, not straight lines. The straight-line distance to a hotel is a lie — a hotel 800m away across a river might be a 4km drive. I integrated the Distance Matrix API so search results show actual travel distance and time from the user's location or a chosen landmark. That single decision makes search results trustworthy.
  • The booking lifecycle. Room selection with dates and guest counts, availability checks, booking creation and confirmation, and a bookings screen that tracks upcoming and past stays.
  • Store-ready polish. Auth, profile management, push notifications for booking updates, and the Play Store / App Store release process end to end.

Outcome

ID Rooms shipped as a production booking platform where users find hotels by where they actually are and how long it actually takes to reach them — and book without leaving the app.

Need an app with maps, logistics, or booking flows? That's core territory — see mobile app development.

Related reading

Keep going

Want something like this?

Tell me your version of this problem. Fixed quote after one call.

usually replies within a day