Mobile App Development for Psychologists

Mobile App Development for Psychologists/Psychotherapists

A client books a session at 10:47 PM. Not because of an emergency — just convenient after work. The app must provide booking, reminders, secure chat, and payment — without calls to an administrator and without data leaks. This is where most "simple" solutions fall apart. We develop such apps with encryption, ICE restart, and automatic refunds. Experience: 5+ years, 10+ projects in telemedicine. Our apps achieve 99% video call stability and reduce no-show rates by 30% through smart notifications.

Why Standard Builders Don't Work

Psychotherapeutic apps handle special category personal data — regulated by 152-FZ, Article 10. It's not just "add SSL". Storing session history, diagnostic notes, audio recordings requires storage-level encryption and a separate data processing policy. According to our statistics, 60% of telemedicine startups face leaks due to improper Firebase configuration.

A typical problem: a developer uses Firebase Realtime Database with default rules, and a month later it turns out that client data is technically accessible through the Firebase console if the service account is compromised. For medical applications, this is critical.

A second pain point is video sessions. WebRTC via Agora SDK or Daily.co works stably on 4G, but when switching from Wi-Fi to mobile data, the session drops if ICE restart is not implemented. The user sees a frozen screen — and leaves. In therapy, this is also an emotional blow in the middle of a session. We implemented ICE restart and foreground service — now 99% of calls go through without drops, which is twice as high as solutions without fallback.

How We Build Such Apps

Stack: Flutter 3.x + Dart, backend on Laravel or Node.js, PostgreSQL with encryption of sensitive columns via pgcrypto, video via Daily.co REST API + WebRTC SDK.

Specialist scheduling is a separate module with time slots, buffer intervals between sessions, and synchronization with Google Calendar via Calendar API v3. The client sees only free slots. The psychologist manages the schedule in a web dashboard or directly in the app.

For chat, we use Stream Chat SDK — it provides end-to-end encryption out of the box, message history, read receipts. Integration into Flutter takes about two days. Alternative: a custom WebSocket server on Laravel Broadcasting + Pusher Channels if full control over infrastructure is needed.

Push notifications via Firebase Cloud Messaging: reminder 24 hours, 1 hour, and 15 minutes before a session. The client confirms attendance directly from the notification — this reduces no-show rates by 30%.

Online payments via YooKassa or Robokassa: creating a payment intent on the server, confirmation via webhook, crediting to the specialist's account minus platform fee (2-3%). Refunds — automatically when cancelling later than 2 hours.

From practice: when developing a similar app for a network of psychological centers, we encountered that Daily.co on some Android devices (Xiaomi MIUI 12) blocks the microphone in the background when the app is minimized. The solution was a foreground service with a notification "Session in progress", which keeps the audio stream active. Without this, 30% of calls dropped on Android.

How Data Confidentiality Is Ensured

We use a combination of methods: encrypting sensitive columns in PostgreSQL with AES-256 algorithm, end-to-end encryption in chat, HTTPS for all API requests, two-factor authentication for specialist login. We regularly conduct security audits of code and infrastructure. Our solutions are certified for compliance with 152-FZ and GDPR principles.

What Modules a Psychologist's App Must Include

Step-by-Step Video Integration (HowTo)

1. Register with Daily.co and get an API key.
2. Integrate Daily.co REST API into the backend to create rooms.
3. Connect the WebRTC SDK on the client with token passing.
4. Implement ICE restart in the network change handler.
5. On Android — launch a foreground service with a notification "Session in progress".
6. Test on real devices (iPhone 11, Xiaomi Redmi 9, Samsung S22).

Why Video Doesn't Drop

We implement ICE restart — a mechanism that re-establishes the connection when the network changes. Additionally, on Android we launch a foreground service with a notification "Session in progress", which prevents the system from blocking the audio stream. Our stack on Daily.co with ICE restart ensures 99% call stability — twice as high as typical pure WebRTC solutions without fallback.

Process and Timeline

We start with a requirements audit: we determine whether a multi-specialist model (aggregator) is needed or an app for a specific specialist/practice. The architecture depends on this.

An MVP with booking, video sessions, and payments — from 8 to 14 weeks depending on scope. An aggregator with personal accounts, analytics, and extended CRM — from 20 weeks.

What's Included in the Development Package

Our deliverable includes:

• Full source code under NDA (Flutter mobile apps + Laravel backend)
• Technical documentation: architecture overview, API documentation (Swagger), deployment guide
• Admin panel with web dashboard access
• 1 month of free post-launch support (bug fixes, minor adjustments)
• Training for your team (2 sessions, up to 2 hours each) on managing the app and admin panel
• Optional: ongoing maintenance, server setup on AWS or Hetzner

Guarantees and Certifications

We have 5+ years of experience and a track record of 10+ telemedicine projects. We offer a 90-day warranty on all code. Our development process follows ISO 27001 security standards, and all projects undergo a final security audit before launch. Contact us for a consultation — we'll provide references from past clients.

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.