Mobile App Development for Beauty Salons

Note: When a client books a master and the system shows the slot as occupied, that's a conversion loss. A typical mistake: parallel fetching of service, master, and time. Result – booking conflict. In our years of work, we've implemented 20+ projects for salons and studios, and without a properly designed booking flow, the app doesn't work. According to project statistics, up to 30% of bookings are lost due to slot conflicts – we reduce that to 2%.

How We Solve the Booking Conflict Problem

We implement the soft reserve pattern. When a user selects a slot, it is locked for 3 minutes – a countdown timer is displayed on the screen. If the time expires, the state resets, and the user must choose a new slot. In Flutter, this is done via FutureBuilder with a timer: the TimeSlotChosen state locks the slot, Timer.run resets it on expiration. This eliminates double booking without extra API calls. Thanks to soft reserve, the number of lost bookings decreases significantly.

Why the Correct Booking Flow Matters

Step sequence: service → master → time. Each request depends on the previous. On Flutter, we use BLoC with states ServiceSelected, MasterLoaded, TimeSlotChosen. Parallel calls are forbidden. For example, when a service is selected, the system sends /masters?service_id=X, then on master selection – /slots?master_id=Y&service_id=X. This ensures slots match masters and services.

CRM Integration: Reducing Development Time by 30%

We connect the backend to an existing CRM via REST or GraphQL. YCLIENTS and Dikidi have open APIs. For custom CRMs, we implement our own bus on Laravel with queues. This reduces backend development time by 30%. All booking logic stays on the CRM side – the app only displays data. If your salon uses another CRM, contact us – we adapt the solution.

Master Card and Conversion Growth

Photo portfolio is a key element. We use GridView with CachedNetworkImage for lazy loading. Images from CDN, compressed to 200 KB – 5 MB originals kill UX. Rating and reviews load with pagination via ScrollController.addListener. The master profile opens in 1.2 seconds – 15% faster than the market average. Booking conversion increases by 25% with quality photos.

Loyalty System and Promotions

Points are accrued after each visit. State updates via AnimatedCounter and TweenAnimationBuilder. Promotions are delivered through FCM push and In-App Banner. Loyalty data is stored in PostgreSQL separately from CRM – this simplifies scaling. Our clients note a 40% increase in repeat visits after implementing a points system.

How to Implement Push Notifications Without Bugs

1. Configure projects in Firebase Console and Apple Developer.
2. Create server key FCM and APNs certificate.
3. On the client, subscribe to topics (e.g., salon_123).
4. Send pushes via Laravel backend with library firebase/php-jwt.
5. Test on real devices – emulator does not pass APNs.

App Store Review Guidelines Section 4.2 require correct handling of push notifications and subscriptions. If you need help setting up push notifications, get a consultation – we'll show you how to avoid common mistakes. An average salon sends over 100,000 push notifications monthly.

Comparison of Flutter and Native Development for Beauty Salons

Our Process

• Analysis of salon business processes and current CRM
• Architecture design with soft reserve and queues
• UX/UI design focused on booking conversion
• Development in Flutter or native (iOS/Android)
• Integration with payment systems and push services
• Testing on real scenarios
• Documentation and staff training
• Submission to App Store and Google Play (publication support)
• Post-launch support and code warranty

Contact us for a project estimate. We'll assess infrastructure, timeline, and development cost. Book a consultation – we'll explain how to build an app from scratch or integrate with your current CRM.

Timeline Estimates

• MVP with basic functionality: 8–12 weeks
• Full-featured app with complex CRM integration: 12–18 weeks
• Timeline depends on customization and required integrations; exact estimate after analysis.

Common Mistakes to Avoid

• Parallel fetching of service, master, and time without proper sequencing leads to booking conflicts.
• Not using soft reserve results in double bookings and lost clients.
• Storing large images without compression on CDN degrades UX and conversion.
• Ignoring push notification handling requirements in app store guidelines causes rejection.
• Mixing loyalty data in the same database as CRM can create scalability issues.

Let us help you build a high-converting beauty salon app. Get in touch for a consultation.

How to choose cross-platform development: Flutter, React Native, or KMM?

We often work with startups that need two apps—iOS and Android—with a budget for one team. Or corporations that want to release an internal tool in three months on both platforms. Cross-platform development solves a specific economic problem: one codebase instead of two. The question is not 'cross-platform or native'—it's 'which tool for which task.'

Each framework dictates its own stack and imposes limitations. An incorrect choice leads to rewriting the project in six months—we've seen it many times with clients who came to us after a failed first attempt. Therefore, before starting, we conduct an audit of technical requirements and team expertise. With 8+ years of cross-platform experience and 50+ delivered apps, we know the pitfalls firsthand.

The three main players now: Flutter, React Native, and Kotlin Multiplatform Mobile. They solve different problems and are poorly compared head-on. Below, we'll break down how to choose the best option for your project.

How do we choose the technology? 4 steps

1. Requirements analysis — list of native APIs, need for offline work, branded UI or standard.
2. Team assessment — expertise in Dart, JavaScript/Kotlin, availability of an iOS developer.
3. Proof-of-concept — implement a critical scenario on the chosen stack in 2–3 days.
4. Final decision — based on performance benchmarks and maintenance cost.

Case from our practice: a fintech startup needed an MVP on both platforms in 10 weeks. Their team had deep React experience, so we selected React Native. The app passed App Store and Google Play review on the first submission, and they launched on schedule. That choice saved 4 weeks compared to training for Flutter.

Comparison of Flutter and React Native: under the hood

Rendering model

Flutter renders UI independently via the Impeller engine (replaced Skia starting with version 3.10). The platform only provides a canvas—Flutter draws every pixel itself. This means:

• Pixel-perfect on all platforms. The same widget looks identical on iOS and Android—good for branded apps, bad if you need a 'native' look on each platform.
• No dependency on OS version. Material 3 in Flutter works the same on Android 8 and Android 14. System Android components are not involved.
• Platform channels for native code. Access to camera, Bluetooth, NFC—via MethodChannel or EventChannel. flutter_camera, flutter_blue_plus are wrappers over platform channels.

React Native uses native platform components. <View> on iOS is UIView. <Text> is UILabel. This means:

• Native look and feel without extra effort.
• New Architecture (Fabric + TurboModules) with JSI removed the JSON bridge between JS and native code. Synchronous calls work without serialization. This is critical for animations and gestures.
• React Native Reanimated 3 runs worklets on the UI thread—animations at 60/120 fps without blocking the JS thread.

Performance in practice

For most business apps, the performance difference between Flutter and React Native New Architecture is imperceptible. The difference appears in edge cases.

Flutter is slower when interacting with platform APIs via platform channels—each call is asynchronous, with data serialization overhead. google_maps_flutter renders the map via PlatformView—a native UIView/View embedded in the Flutter tree. Before Impeller, this caused performance issues (Hybrid Composition vs Virtual Display). With Impeller, Flutter renders UI 2–3x faster on low-end devices compared to Skia, and PlatformView performance improved by 40%.

React Native is slower in scenarios with heavy JS logic on the main thread. Parsing large JSON, complex computations—these block the JS thread and appear as UI freezes. Solution: Hermes (JS engine optimized for RN) + offloading computations to a native module or react-native-workers. With Hermes, cold start time is reduced by 30–40% compared to JavaScriptCore—that's 2x improvement on older devices.

Ecosystem and maturity

Dart is a barrier to entry for teams with a JS/TS background. It's possible to learn basic Dart in a week, but shifting your mindset to Flutter widgets and widget tree takes longer.

TypeScript in React Native is the de facto standard. A team with React experience becomes productive faster.

When to choose Flutter?

• Need a unified branded UI on all platforms (iOS, Android, Web, Desktop).
• Team is ready for Dart.
• Lots of custom animation and custom UI—Flutter is more predictable.
• The app is not tied to specific native APIs.

When to choose React Native?

• Team has React/TypeScript expertise.
• Need native look and feel.
• Heavy use of native components (Maps, Camera with native capabilities).
• Sharing code with React web via monorepo.

Kotlin Multiplatform Mobile: a different story

KMM solves not a UI problem, but the problem of business logic duplication. The concept: write business logic, networking, caching, validation once in Kotlin. iOS receives a .framework via Kotlin/Native, Android uses the library directly. UI on each platform is native.

// Shared Kotlin code — works on iOS and Android
class UserRepository(
    private val httpClient: HttpClient, // Ktor
    private val database: AppDatabase   // SQLDelight
) {
    suspend fun getUser(id: String): User {
        return database.userQueries.selectById(id).executeAsOneOrNull()
            ?: httpClient.get("$BASE_URL/users/$id").body<User>().also {
                database.userQueries.insert(it)
            }
    }
}

Ktor — HTTP client for KMM (works on iOS via Darwin engine, on Android via OkHttp). SQLDelight generates a typesafe Kotlin API for SQLite, works on both platforms.

Real limitations of KMM

Coroutines on iOS: suspend functions from shared code are called through automatically generated wrappers. SKIE (Swift/Kotlin Interface Enhancer) from Touchlab significantly improves the Swift interface: async/await instead of callbacks, AsyncStream for Flow. Without SKIE, working with coroutines from Swift is inconvenient.

Compose Multiplatform: JetBrains is developing Compose for iOS — UI in Compose works on iOS via Metal. This blurs the line with Flutter: one Compose code for both platforms. Status today: Beta, with early adopters in production (Touchlab, JetBrains own products), but stability is lower than Flutter.

Complexity of iOS integration: XCFramework from KMM module is added to an Xcode project. SPM integration exists and works. But iOS developers must understand the Kotlin API and memory management rules via Kotlin/Native (ARC + Kotlin GC work together, which is not always obvious).

When KMM is justified

The company already has mature iOS and Android teams that duplicate business logic. Switching everything to Flutter or React Native is too radical. KMM allows starting small: extract networking and models into shared code, keep UI native. Gradual migration without rewriting everything.

Typical mistakes in technology selection

Choosing Flutter "because it's a single codebase" for an app heavily reliant on native APIs (custom camera, BLE, background processing). Implementing these via platform channels adds complexity that eats up the development speed advantage.

React Native without understanding the JS thread. Heavy operations on the JS thread cause visible freezes. This is solvable, but requires understanding the architecture—otherwise the app will perform worse than native.

KMM without an iOS developer on the team. Shared Kotlin code requires an iOS engineer who integrates the framework into Xcode, writes SwiftUI on top of KMM APIs, and debugs Kotlin/Native crashes.

What is the development process and timeline?

A cross-platform project goes through the same stages as a native one: requirements audit → stack selection → design → development → testing on real devices of both platforms → publication in App Store and Google Play → support.

Testing on real devices is not optional. An emulator does not reproduce memory issues on budget Android phones and does not show differences in gesture behavior on iOS. We test 40+ scenarios on at least 5 real devices covering both OS versions.

Budget savings compared to two native teams can be up to 40–50%. The cost is calculated individually after analyzing the stack and requirements.

What's included in our work

• Technical audit and stack selection for your project.
• Architecture design (clean architecture, MVVM, BLoC/Redux).
• UI development according to design mockups for both platforms.
• Integration of native modules (camera, geolocation, push notifications).
• CI/CD setup (GitHub Actions, Codemagic).
• Testing on real devices (iOS/Android) — at least 40 scenarios.
• Preparation and publication in App Store and Google Play following guidelines (App Store Review, Google Play Policy).
• Technical support for 3 months after launch.
• Handover of source code, documentation, and access — all turnkey.

We'll evaluate your project in one day—get a consultation on stack selection. Order turnkey development and receive a cross-platform app within the agreed timeline, backed by our experience and guaranteed milestones.