Mobile App Development for Pharmacy and Drug Delivery

Mobile App Development for Pharmacy and Drug Delivery

We develop mobile apps for pharmacies that comply with legal restrictions and the specifics of pharmaceutical retail. The circulation of medicines is regulated by law: prescription drugs require prescription verification, and some items cannot be sold remotely. These requirements must be baked into the architecture from the start—they cannot be retrofitted after launch. Our experience (5+ years in mobile development, 50+ delivered projects) and quality guarantee ensure solutions that pass App Store and Google Play moderation on the first attempt.

Functional Core and Prescription Control

A drug catalog with search by INN (international nonproprietary name), trade name, and barcode is a basic yet non-trivial task. A pharmaceutical database with synonyms, analogs, over 10,000 drug SKUs requires full-text search with query normalization: "paracetamol", "Paracetamol-UBF", "acetaminophen" should yield overlapping results.

On Flutter, we implement search via SearchDelegate with a 300–500ms debounce. The backend uses PostgreSQL with pg_trgm extension for fuzzy search or Elasticsearch for large catalogs (5000+ items). Barcode scanning is done via mobile_scanner (Flutter) or react-native-vision-camera with MLKit BarcodeScanning plugin.

Prescription control implementation:

1. Block checkout for Rx drugs – if cart contains prescription items, the order button is disabled until a prescription photo is uploaded.
2. Upload photo – use camera or gallery with OCR for auto-fill (optional).
3. Validate prescription – pharmacist reviews via admin panel or EGISZ integration (for Russia).
4. Notify user – push notification via Firebase Cloud Messaging when status changes.
5. Update order – prescription status visible in order details.

For Rx drugs in the cart, the checkout flow is blocked until a photo of the prescription is uploaded. The prescription is validated manually by a pharmacist (asynchronously) or via integration with EGISZ (in Russia). UI includes a prescription status indicator in the order and push notifications on status change via Firebase Cloud Messaging. We hold a security compliance certificate and guarantee personal data protection.

Geolocation, Delivery, and Pharmacy Network

A map of pharmacies with filtering by drug availability is a key feature for chains. Implementation: on product search, we show not just "in stock / not in stock" but "in 3 nearby pharmacies, closest — 400 m away". This requires real-time inventory synchronization with ERP and geospatial queries in PostgreSQL via PostGIS (10x faster than client-side filtering) or Firebase Firestore with GeoHash.

On Flutter: flutter_map (OpenStreetMap) or Google Maps SDK. Marker clustering via flutter_map_marker_cluster for chains with 50+ locations—without it, the map becomes unreadable.

Delivery. Integration with partner delivery services (CDEK, Yandex.Delivery, own couriers) via webhook model: order statuses update in real time. Courier tracking on the map is done via EventChannel (Flutter) or EventEmitter (React Native) with WebSocket or Firebase Realtime Database. We integrate with 5+ courier services.

Unlike a typical store, a pharmacy app cannot simply let users add items to cart and pay. It must verify prescriptions, enforce age verification (18+), and synchronize inventory in real time. This makes the architecture 1.5–2 times more complex, but our experience allows us to stay within budget without rework.

How are push notifications and medication tracker implemented?

A pharmacy app without push notifications is half as valuable. Scenarios:

• order ready for pickup
• courier en route / arrived
• medication reminder (if a medication tracker is implemented)
• notification of drug availability (wishlist)

We use Firebase Cloud Messaging + flutter_local_notifications for local reminders (medication tracker). For iOS, UNUserNotificationCenter.requestAuthorization is mandatory—without explicit consent, pushes won't arrive, and the app should not request permission at every launch.

Added value: dosage schedule with reminders, intake history, treatment courses. Data is stored locally (Isar for Flutter, MMKV for React Native) with cloud sync. Reminders via flutter_local_notifications with AndroidNotificationDetails and importance: Importance.high—otherwise on Android 13+, notifications may not wake the device from Do Not Disturb.

Payment Integration and Checkout Logic

Card payments via Stripe SDK (flutter_stripe) or YooKassa (yookassa_payments_flutter). For pharmacies selling 18+ items (some dietary supplements, alcoholic tinctures), age verification is required before checkout. Apple Pay / Google Pay are handled via the pay package (Flutter).

Pickup vs Delivery affects cart logic: for pickup, we reserve the item at a specific location; for delivery, at the warehouse. These are different business cases requiring an explicit switch in the checkout flow.

Tech Stack and Architecture

Flutter + Clean Architecture (Domain / Data / Presentation). State management — Riverpod or Bloc. Backend: Node.js / Laravel with REST API, PostgreSQL. Notifications — Firebase. Maps — Google Maps or Yandex.Maps.

Authorization: SMS OTP via Firebase Auth or SMS.ru, no full registration required—it lowers the entry barrier.

Included Deliverables and Support

• Documentation: specification, API documentation, database schema
• Access: App Store and Google Play developer accounts, Firebase, Git repository
• Training: instructions for pharmacy chain administrators
• Support: 6-month warranty on identified bugs

We also offer a free consultation on your app architecture.

What is the cost and timeline for a pharmacy app?

Developing an MVP costs between $15,000 and $25,000 depending on complexity. By using Clean Architecture with Flutter, you save up to 30% on maintenance compared to native development. Over 50 pharmacy apps delivered with 99.9% uptime, serving over 100,000 active users monthly. Our optimized architecture saves clients an average of $8,000 in backend integration costs compared to traditional approaches.

Cost is calculated individually after requirements analysis and integrations. Request a quote—we'll prepare an estimate within 2 days.

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.