Developing a Mobile App for Hotel Booking
A hotel booking app is a competitive niche with established players (Booking.com, Ostrovok, Yandex.Travel). Winning in this space with your own app requires specialization: a specific region, corporate travel, or a particular property category. Technical implementation is no simpler than for giants—you need the same inventory system, calendar availability, payment with holds, and booking management.
Integration with Hotel Management Systems (PMS)
The central technical challenge is obtaining current room availability and pricing. Three options:
Channel Manager API. Hotels are connected to a channel manager (TravelLine, Bnovo, Reznext)—a single point for updating inventory. TravelLine provides REST API for availability search and booking. One contract with the channel manager unlocks access to thousands of connected hotels.
Direct PMS Integration. Opera PMS (Oracle), Fidelio, 1C:Hotel—each has its own API or SOAP. Makes sense only when working with a specific hotel chain.
OTA Aggregators. Ostrovok B2B API, Broniruй API, HotelBeds—ready-made aggregators with large inventory, commission-based model. For launch, this is fastest.
// Room availability request via channel manager API
struct AvailabilityRequest: Encodable {
let hotelId: String
let checkIn: String // "2025-06-15"
let checkOut: String // "2025-06-18"
let adults: Int
let children: Int
let currency: String
}
struct RoomType: Decodable {
let id: String
let name: String
let description: String
let capacity: Int
let pricePerNight: Decimal
let cancellationPolicy: CancellationPolicy
let images: [String]
let availableRooms: Int
}
Map and Geolocation Search
Searching for nearby hotels is mandatory. MapKit (iOS) with MKAnnotationView and clustering, or Google Maps SDK. With many objects on map (100+)—clustering via GMSMarkerClusterer (Google) or ClusterKit (MapKit).
On the map, show price "badges" instead of standard markers—custom MKAnnotationView with UILabel for price. Tapping a cluster zooms in. Tapping a marker opens a bottom sheet with the hotel card.
Geosearch: by center coordinates + radius. Backend: PostGIS with ST_DWithin(location, ST_Point(lon, lat)::geography, radius_meters)—fast with spatial indexing.
Date Calendar and Dynamic Pricing
Check-in/check-out date selection is one of the most problematic UI elements in hotel apps. Standard DatePicker won't work: you need a custom range picker with blocked unavailable dates, showing minimum price under each date.
On iOS, custom range date picker via UICollectionView with custom layout—cells with range highlighting. On Android—MaterialDatePicker from Material Design 3 with customization via DayViewDecorator.
Dynamic pricing: prices change based on demand and dates. Caching for 30 minutes is reasonable. Before final booking—re-check price via GET /rooms/{id}/price-check?checkin=&checkout=. If price changed—warn the user with new price before payment.
Hold and Payment
Payment scheme depends on hotel policy:
- Full Prepayment—pay immediately when booking
- Payment at Check-in—book without payment, hotel holds the room
-
Partial Prepayment—hold amount via
payment.capture_mode = manualin YooKassa or Stripe
Hold (preauthorization): via YooKassa it's POST /payments with capture: false. After guest check-in—POST /payments/{id}/capture. If cancellation—POST /payments/{id}/cancel. Some OTA aggregators take payment themselves and transfer to hotel—simplifies integration.
Apple Pay and Google Pay are mandatory for conversion. PKPaymentRequest on iOS, PaymentsClient on Android.
Booking Management
"My Bookings" screen: active, past, cancelled. Details: voucher, hotel address with navigation (deep link to 2GIS/Yandex.Maps/Google Maps), contacts. Cancellation with penalty calculation per cancellation policy and current date—logic on backend, not client.
Push notifications: booking confirmation, reminder 3 days before check-in, review request after check-out (after 24 hours).
Reviews
Review system with category ratings: location, cleanliness, staff, value for money. Verification: only users with completed booking can leave review. Moderation before publishing—either automatic (ML spam/abuse classifier) or manual.
Stages and Timeline
| Stage | Timeline |
|---|---|
| Channel manager / OTA API integration | 1–2 weeks |
| Search, map, filtering | 2 weeks |
| Hotel card, gallery, details | 1 week |
| Booking and payment | 1–2 weeks |
| Account, history, reviews | 1 week |
| Testing, iOS + Android build | 1 week |
Total: 8–12 weeks. Pricing is calculated individually after requirements analysis.







