Mobile App for Dentistry: Scheduling, Treatment Map, Loyalty

Developing a Mobile App for Your Dental Clinic

Dental clinics lose up to 30% of patients due to cumbersome booking and lack of reminders. A mobile app solves this: online scheduling synced with your EMR, push notifications 24 and 2 hours before appointments, reducing no-shows by 40%. According to a study in the Journal of Medical Internet Research, such reminders cut missed appointments by 40% and save clinics up to $30,000 per year. But building a medical app is not just another interface: it requires handling personal data (152-FZ in Russia), integrating with DICOM images, and passing App Store certification (Section 4.2/5.1). Our team has 5+ years of experience and over 20 completed projects for clinics of all sizes.

A typical scenario: a patient calls the clinic, the receptionist checks availability, calls back—30% never book. An app with online booking and EMR synchronization automates this: the patient picks a doctor and time, receives reminders. To make it work reliably, deep EMR integration, push notification handling (APNs/FCM), and deep linking (Universal Links / App Links) are essential.

Solving EMR Integration

Integration with the Medical Information System (EMR) is key. Popular Russian EMRs include Dental4Windows, 1C:Dentistry, Medesk, CleverMed. Each has its own API or limited methods. If no direct integration exists, we build a custom slot manager: the admin manually exports the schedule, and the app parses the export (CSV/XML) and syncs via webhook. For reliability, we use a task queue (RabbitMQ) and background tasks (WorkManager on Android, Background Tasks on iOS). Push notifications are sent via Firebase Cloud Messaging (FCM) and Apple Push Notification service (APNs) using data messages for prioritized delivery.

Treatment Chart and Images

Interactive tooth chart (WHO two-digit or Viola notation) — implemented via SVG on Canvas API or custom CustomPainter in Flutter. Attaching photos and X-rays: files stored on the server, in-app viewer with zoom (InteractiveViewer in Flutter, react-native-image-zoom-viewer in RN). DICOM image transfer: if the clinic uses digital X-ray, we consider a lightweight DICOM viewer or server-side conversion to JPEG. To save bandwidth and storage, we compress images (JPEG 80% quality) and cache them locally.

Loyalty and Bonus Programs

Bonus points for visits, referral programs — simple logic but requires syncing with the cash register system (e.g., ATOL). We implement a REST API for accrual/redemption and integrate with push notifications to inform about new bonuses.

Flutter vs. React Native: Detailed Comparison

For dentistry, which needs custom UI (tooth chart, animations), Flutter gives an edge in development speed and performance. Flutter outperforms React Native in animation performance by 2x and reduces development time by 20%. React Native works if the clinic already has native modules or the team knows JavaScript. In our projects, we usually use Flutter, but the choice is yours. We can build both Flutter dental apps and React Native dental apps.

Why Data Security Is a Priority?

Data security — a special category of personal data (152-FZ in Russia, GDPR in Europe). Minimum requirements: transport-layer encryption (TLS 1.2+), storage on Russian servers (for Russia-based projects), consent at registration, account deletion capability. We also help with certification and documentation. For Android, configuring ProGuard / R8 is critical — incorrect settings strip classes needed for Hilt DI or Room. On iOS, we follow App Store Review Guidelines Section 5.1 for health data. When setting up ProGuard / R8, keep classes used by Hilt or Room. Add to proguard-rules.pro:

-keep class * extends androidx.room.RoomDatabase
-keep @dagger.hilt.* class *

Otherwise, the app will crash on startup after shrink mode. We guarantee that our configuration is tested and documented. Our team is certified in medical data security (152-FZ, HIPAA).

Process and Timeline (Step-by-Step)

A basic app with online booking — from 8 to 12 weeks. A full-featured patient portal app with treatment chart and images — from 4 to 6 months. Cost ranges from $20,000 for a basic app to $100,000 for a full-featured solution. We offer turnkey mobile app development for dental clinics, including custom CRM for dentistry to manage leads and appointments. We also provide a 3-month warranty and guaranteed on-time delivery.

Commercial Deliverables (What’s Included)

• Documentation: specification, user flow, API specification.
• Source code with comments and README.
• Administrator training for the control panel.
• Technical support for 3 months post-launch.
• Help with app store publishing and certification.
• Access to our secured development environment.

Common Mistakes and How to Avoid Them

• Ignoring App Store Review requirements (Section 4.2 / 5.1): medical apps need Apple’s approval. We prepare documentation in advance.
• Lack of offline mode: patients may have no internet in the clinic. We implement data caching and background sync.
• Incorrect ProGuard / R8 configuration on Android: needed classes for DI are stripped. We use keep rules and test shrink mode.

Contact us for a consultation — we’ll analyze your processes and suggest the optimal solution.

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.