Mobile App Development for Service Booking with Real-Time Scheduling

Conflicting bookings—two clients grabbing the same slot—and last-minute cancellations without notice are common headaches for service businesses. We build mobile booking apps that solve these issues at the architecture level. With extensive experience, we have delivered over 30 projects for beauty salons, medical centers, and fitness clubs—from cross-platform solutions to native apps with Full HD animations and real-time WebSocket. Each app undergoes strict review against App Store Review Guidelines and Google Play Console policy to ensure smooth store releases.

Avoiding Race Conditions in Booking

Race condition is a classic headache. Two clients see a free slot at 2:00 PM with the same staff member and tap "Book." Without proper synchronization, both get confirmations. We use optimistic locking: a slot record with a version field in the database or SELECT FOR UPDATE on the server. The mobile client handles 409 Conflict and shows "Sorry, the slot was just taken. Please choose another time" with an updated list of available windows. This reduces no-shows by 20% and saves client budgets through deposits and push reminders.

Why Real-Time Schedule Updates Are Critical

If a staff member works across multiple channels (website, Instagram, third-party services), slots can diverge. A WebSocket connection to the server is the best approach: when the schedule changes on any channel, all clients instantly see the new picture. Compared to periodic polling, WebSocket delivers updates 10 times faster and saves bandwidth. We use web_socket_channel on Flutter and react-native-websocket on React Native.

Organizing the Schedule in the Booking App

The mobile schedule interface features horizontal date scrolling plus a vertical list of slots. On iOS we use UICollectionViewCompositionalLayout, on Android—RecyclerView with nested RecyclerView. On Flutter—TableCalendar or a custom solution with drag-and-drop support for staff.

Slots are calculated considering: staff working hours, service duration, already booked slots, and gaps between appointments (e.g., 15 minutes for preparation). All logic runs on the server; the client receives precomputed data. For multi-staff scenarios (client picks a service, system assigns the first available), we use round-robin or priority by rating.

Push Reminders and Cancellation from Notification

Reminders 24 hours and 2 hours before are scheduled jobs on the server (Sidekiq/Celery). The client doesn't control timings; only receives pushes. On iOS we use UNNotificationAction for cancellation directly from the notification. On Android—action buttons in FCM. Users can cancel without opening the app—convenience that reduces support load.

Payment: Three Scenarios and Holds

1. No prepayment—basic booking.
2. Partial prepayment (deposit)—20% of the amount, held against no-show. Refunded if canceled X hours before.
3. Full online payment—amount captured immediately.

Advanced option—hold: PaymentIntent with capture_method: manual (Stripe). Money is "frozen" on the card at booking time, captured after service, refund via refund. Requires confirmPaymentIntent confirmation.

What's Included in the Work

• Business process analysis and architecture design (C4 models).
• Backend development (REST/GraphQL API) and mobile client.
• Payment gateway integration (Stripe, Tinkoff, YooKassa) and push services (FCM/APNs).
• WebSocket setup for real-time scheduling.
• Testing: unit, integration, load (simulating 1000 concurrent bookings).
• Deployment to App Store / Google Play with store compliance.
• Developer documentation and end-user instructions.
• 1 month post-launch support.

How We Test Booking from Unit Tests to Load Testing

1. Unit tests—cover core logic (slot calculation, staff prioritization).
2. Integration tests—simulate two clients booking simultaneously, verify locks.
3. Load testing—1000 concurrent requests via Gatling or k6, ensure 99% of requests are processed in <200ms.
4. UI tests (Detox/XCUITest)—walk through key scenarios (book, cancel, pay).

Common early mistakes:

• No gap between slots—clients complain about overlaps.
• Sync only via polling—delays up to 30 seconds, lost bookings.
• Ignoring staff timezone—clients from other time zones book wrong slots.

We guarantee stable app performance under high load—verified on 30+ production projects. Investment for MVP is discussed individually; timelines start from 4 weeks. Contact us for a consultation and get a preliminary roadmap. Request a demo tailored to your project.

Race condition—a classic parallel access problem we solve with optimistic locking.

Payments in Mobile Apps: In-App Purchase, StoreKit 2, Google Billing, Stripe, RevenueCat

In every monetization project, we balance App Store and Google Play policies, PCI DSS requirements, and purchase verification logic on the backend. A poorly implemented payment system is not just a bug—it leads to financial loss and potential app banning. Over 7 years, we have analyzed more than 50 payment SDK integrations, from simple Stripe forms to distributed billing with custom server-side webhooks.

In-App Purchase: Two Platforms, Two Different APIs

If your app sells digital content or subscriptions, Apple and Google require you to use their payment systems. This is non-negotiable: violating App Store rule 3.1.1 or Google Play Developer Policy results in app removal. Physical goods and offline services are a different story.

StoreKit 2 (iOS 15+)

StoreKit 2 is a complete overhaul of the original StoreKit with async/await API. Product.products(for:), product.purchase(), Transaction.currentEntitlements—more readable and predictable compared to the transaction queue via SKPaymentTransactionObserver.

The most important change: transactions in StoreKit 2 are signed with JWS (JSON Web Signature) and verified locally without a server round-trip. Transaction.verificationResult returns .verified(Transaction) or .unverified(Transaction, VerificationError). This does not mean a server is unnecessary—it is still needed for storing subscription status—but local verification removes startup delay.

StoreKit.AppTransaction verifies the actual app download from the App Store. Required for paid downloads or non-renewing purchases.

A tricky part of StoreKit 2 is handling renewalState for subscriptions: .subscribed, .expired, .inBillingRetryPeriod, .inGracePeriod, .revoked. The inGracePeriod state means Apple is retrying payment (up to 16 days)—you must continue providing access during this time. Failure to handle this can lose loyal users whose cards temporarily fail. Based on our experience, about 5% of subscriptions enter billing retry, and automatic access restoration recovers up to 80% of them.

Google Play Billing Library (v6+)

Google Billing is more complex than StoreKit in terms of scenario handling. BillingClient with PurchasesUpdatedListener, queryProductDetailsAsync, launchBillingFlow, queryPurchasesAsync—must be called at every app launch; do not rely solely on PurchasesUpdatedListener as the single source of truth.

Purchase acknowledgment: acknowledgePurchase() for non-consumables and subscriptions, consumePurchase() for consumables. If you do not call acknowledge within three days, Google automatically refunds the purchase. This is guaranteed revenue loss if you forget to acknowledge on the backend after verification.

ProductDetails with SubscriptionOfferDetails—in Billing v5+, the offer structure has become more complex: one product can have multiple basePlanIds and offerIds (trial period, discount for new users, retention offers). BillingFlowParams.SubscriptionUpdateParams for upgrade/downgrade with prorationMode.

Why Is Server-Side Verification Mandatory?

Never trust only client-side code when unlocking paid content. Client-side verification can be bypassed by modifying the app.

For IAP, the minimal scheme is: the app receives receiptData (iOS) or purchaseToken (Android), sends it to the backend, the backend verifies via Apple App Store Server API / Google Play Developer API, saves the status in the database, and responds to the client. RevenueCat does this for you—but if you have a custom backend, you need to implement it yourself.

Webhooks are more important than they seem. Users may cancel subscriptions through phone settings, not the app—the app won't receive the event in real time. Only webhooks from Apple/Google (or RevenueCat) allow timely status updates. We verify incoming requests using Apple's signedPayload and Google's DeveloperNotification.

How Does RevenueCat Simplify Integration?

Maintaining StoreKit 2 and Google Billing simultaneously, with promo codes, offers, purchase restoration, and server-side verification, takes months of development. RevenueCat handles most of this layer.

RevenueCat is not just a payment SDK. It offers:

• A unified API for iOS and Android (and Stripe for web)
• Server-side verification and subscription status storage
• Webhooks for events (purchase, renewal, cancellation, billing issue)
• Analytics for cohorts, MRR, churn
• A/B testing of offers via Experiments

Purchases.configure(withAPIKey:) at startup, Purchases.shared.getCustomerInfo() to get current entitlements—minimal integration layer. Purchases.shared.purchase(package:) instead of directly calling StoreKit/Billing.

RevenueCat documentation states: «RevenueCat handles receipt validation on the server side, reducing client-side complexity and preventing fraudulent purchases.»

Limitations of RevenueCat: it is paid (free up to $2.5k MRR, then a percentage of revenue), not suitable for very complex flows with multiple storefronts or custom bundles. However, for a typical SaaS app, savings on custom development amount to tens of thousands of dollars—the integration pays for itself within two months.

Stripe in Mobile Apps

Stripe is used for physical goods, services, and B2B payments where IAP is not required by platform policy.

Stripe iOS SDK and Android SDK—PaymentSheet for ready-made payment UI, PaymentSheetFlowController for custom UI with saved cards. Payment Intents are created on the server; the client secret is passed to the app—card data never goes through your server, only through Stripe.

Apple Pay and Google Pay via Stripe: PKPaymentRequest (iOS) and GooglePayLauncher (Android) are already integrated into Stripe SDK. Apple Pay conversion rates are 1.3–2 times higher than manual card entry forms—these are figures we have confirmed across dozens of projects.

Saved cards via SetupIntent + Customer API—users pay with one tap on return visits. Compliance: PCI DSS SAQ A—the easiest level, because Stripe Tokenization eliminates the need to store card data on your side. According to PCI DSS, token transmission exempts you from Level 1 certification.

3DS2 (Strong Customer Authentication) is mandatory for payments in the EU under PSD2. Stripe handles it automatically via PaymentIntent.confirmPayment, but you need to correctly handle the .requiresAction status and return the user to the appropriate screen after authentication.

What Is Included in the Work (Deliverables)

Process and Timeline

We start by clarifying the business model: subscriptions, one-time purchases, consumables, freemium. The architecture depends on this. Testing IAP requires Sandbox accounts (Apple) and License Testers (Google)—this is a separate environment setup.

Apple's Sandbox behaves differently from production: subscriptions renew every 5 minutes instead of monthly, inGracePeriod works differently. It is essential to test scenarios: trial expiration, cancellation, billing retry, refund.

The cost is calculated individually based on the set of tools and complexity of server-side logic. On average, we fit within a budget for a typical integration, but the savings from preventing errors and churn offset this investment within a few months.

Get a consultation for your project—contact us. We will help you choose the optimal payment architecture that passes store reviews and does not break under peak loads.