Coaching App Development: From Booking to Payments
Imagine a coach spending 20% of their time manually coordinating session times with clients over messengers. Each session involves back-and-forth messages, reminders, and rescheduling. Clients forget to pay, and the coach loses revenue. A coaching app solves these problems through automation: booking, payments, journal, habit tracker—all in one place. But implementation is trickier than it seems: you need to account for data security, time zones, and flexible payment scenarios. We've built dozens of coaching apps over 5+ years and know how to avoid common pitfalls. In this article, we'll break down key modules: from the wheel of life to push notifications. We'll show how to implement flexible booking with time zone support, and why Stripe often beats Apple's in-app purchases—savings on fees can reach 27%.
Session Booking: A Flexible Availability Editor
Integration with Calendly or a custom booking flow. Our own implementation uses a time_slots table, similar to mentoring platforms. The difference: coaches often work on a strict schedule (e.g., only Tuesdays 10:00–18:00) and need a flexible availability editor.
The coach's availability editor includes a weekly template (days of week + start/end times) plus exceptions. The RecurringSchedule model: dayOfWeek, startTime, endTime. Exceptions (vacations, holidays) are stored as blocked_dates. When booking, we compute available slots for the next N weeks, taking into account booked and blocked periods.
Time zones are mandatory. Coach in Moscow, client in London. All slots are stored in UTC and converted to local time on the client. Use TimeZone.current (iOS) / ZoneId.systemDefault() (Android) to determine the device's zone. Use DateComponentsFormatter for human-readable display like "in 2 hours".
Choosing between Calendly and custom development: Calendly gives a quick start and a ready UI but limits customization and requires API fees. A custom booking flow takes 1–2 weeks of backend development but gives full control over design and logic—for example, you can add custom availability rules or CRM integration. For projects with unique requirements, the second option pays off with flexibility.
Coaching Tools Inside the App
Wheel of Life – a circular chart with 8–12 life areas (career, health, relationships, finances, etc.). The client rates each area on a 1–10 scale. We draw it using Core Graphics / Canvas in Compose: UIBezierPath for sectors on iOS, Path in Compose on Android. Animation on rating changes – withAnimation (SwiftUI) / animateFloatAsState (Compose).
History of wheel of life – show changes over a month/quarter. Two overlaid wheels (current and past) with transparency via UIColor.withAlphaComponent().
Progress Journal – daily/weekly client entries. Markdown or rich text via UITextView with a custom toolbar for bold/italic. Save locally (Core Data / Room) + sync to server. The coach sees entries only if the client explicitly shares them – via a toggle in settings.
Reflective Questions – the coach creates question templates for homework. The client answers in the app. Question + formatted text answer + option to attach a voice note (via AVAudioRecorder).
Habit Tracker – a simple checklist of daily habits. UITableView with UISwitch or Compose Checkbox. Streak – consecutive days, a motivating element. Calendar.current.dateComponents([.day], from:to:) to calculate the streak.
How to Securely Store Consent for Session Recording?
Video session – built-in (100ms, Daily.co) or external link. After session – a field for the coach's notes (key insights, next steps). The client gets a notification that notes are added.
Audio recording (with client consent) – AVCaptureSession with AVCaptureAudioDataOutput. Record to M4A, upload to server. Store consent as a separate consent flag with timestamp in the database.
Audio transcription – SFSpeechRecognizer (iOS, offline on device for supported languages) or OpenAI Whisper API through the server for accuracy and multilingual support.
Why Coaching Apps Often Choose Stripe Over App Store?
Stripe's PaymentSheet for one-time sessions and Stripe Billing for packages. iOS App Store subscriptions (StoreKit 2) only if coaching is sold as "in-app content" – but most coaching apps work through Stripe (web payment form) without IAP. A package of 10 sessions – Product with type: .nonConsumable in StoreKit (used once, not restored on app deletion). Or package as a subscription with a limited usage period.
| Aspect | Stripe (external payments) | App Store / Google Play (IAP) |
|---|---|---|
| Fee | ~2.9% + $0.30 | 15–30% on revenue up to $1M |
| Flexibility | Full control over products | Limited subscription types |
| Reporting | Integrates with any accounting | Only Apple/Google reports |
| User Experience | Web form, context switch | Seamless inside the app |
Stripe is 5–10 times cheaper for typical session sales volumes.
What's Included in the Work
- Technical specification and UI/UX prototype
- Backend development (REST/GraphQL) + client (iOS/Android)
- Payment integration (Stripe / StoreKit)
- Publication on App Store and Google Play
- API and administration documentation (Swift Package Manager for dependencies, Fastlane for CI/CD)
- Access transfer and team training
- 3-month warranty support
Process and Timelines
| Stage | MVP | Full Feature Set |
|---|---|---|
| Booking + profiles + video sessions + push | 5–7 weeks | 2–3 months |
| Wheel of life + journal + habits + reflection + subscriptions | — | 2–3 months |
Cost is calculated after requirements analysis. Contact us for a project evaluation – we'll find the optimal turnkey solution. Get a consultation on your app's architecture – we'll share how to avoid common pitfalls when choosing a tech stack.