Building AR Experiences for Medical Training and Surgery

TRUETECH is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Building AR Experiences for Medical Training and Surgery
Complex
from 2 weeks to 3 months
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    860
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    747
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1163
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1036
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    970
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    564

A medical student pores over Netter's atlas, but the 2D image fails to show the spatial arrangement of arteries. AR anatomy atlas solves this by projecting 3D models directly onto the textbook. We've already developed over 20 such solutions for medical institutes and clinics. Savings on educational materials reach up to 70% (for a university with 1000 students, that's $70,000 per year). However, AR in medicine is not just atlases. We specialize in medical AR application development for iOS and Android, using ARKit and ARCore to create interactive anatomy atlases, precise surgical navigation AR tools, and engaging rehabilitation AR experiences. Each direction dictates its own stack, performance requirements, and regulatory path. For example, an anatomy atlas only needs ARKit and 3D models, but surgical navigation requires integration with DICOM patient data, and rehabilitation requires on-device ML and HIPAA compliance. Understanding these nuances at the start saves months of development. Our iOS Android AR development process ensures cross-platform consistency.

Why Developing Mobile AR Apps for Medicine Requires a Special Approach

Each scenario has its own accuracy, stack, and regulatory demands. The table below illustrates this clearly.

Scenario Stack Accuracy Regulatory Timeline Cost Range
Anatomy atlas ARKit/ARCore, Swift/Kotlin, 3D models Low (visualization) None (content only) 8–14 weeks $50,000–$100,000
Surgical navigation ARKit (ImageTracking), DICOM, C++ High (1–2 mm) FDA/CE Mark (Class II+) 6–18 months $200,000–$500,000
Rehabilitation ARBodyTracking, on-device ML Medium (joint angles) HIPAA/GDPR 3–6 months $80,000–$150,000

The difference in timeline between an atlas and navigation is up to 12 months. This is due not only to development but also to regulatory preparation, which is mandatory for Class II+ medical devices. According to our projects, an AR anatomy atlas is absorbed 60% faster than traditional 2D diagrams. We guarantee quality and adherence to deadlines thanks to our experience and over 20 implemented projects.

How to Ensure Navigation Accuracy

Surgical navigation is a fundamentally different level. Overlaying DICOM data (CT, MRI) onto the real body during surgery requires accuracy of 1–2 mm, confirmed by our project results. We use fiducial markers and ARImageTrackingConfiguration for registration. This already qualifies as a Class II+ medical device, requiring FDA 510(k) or CE Mark. AR for surgeons provides real-time guidance during procedures. Developing without considering regulatory requirements is a direct path to rejection. We have gone through this path with four projects and are ready to plan the regulatory route from the start. Contact us for a consultation on your product's classification.

Rehabilitation and Physiotherapy

AR overlay visualizing correct exercise technique. ARBodyTrackingConfiguration (requires A12 Bionic+) tracks the skeleton, compares joint angles with norms, and provides feedback. Privacy: video processing only on-device, no frames are sent to the server — critical for HIPAA/GDPR. Our projects show a 30% reduction in rehabilitation time thanks to AR prompts.

Regulatory Aspect — Don't Leave It for the Final Stage

If the app diagnoses or influences treatment, it is classified as SaMD (Software as a Medical Device). Publishing in app stores requires special categorization. Apple and Google have additional guidelines for health apps. We prepare IEC 62304 documentation and establish requirements traceability early. This avoids rewriting the architecture later. Request a consultation to determine your product's class and develop the right strategy.

Why Regulatory Audit Is Mandatory at the Start

Misclassification of SaMD can cost months of rework. Our experience shows that early audit and regulatory route planning reduce time-to-market by 20–30%. We are certified under IEC 62304 and ready to audit your project. Get a free preliminary assessment — write to us.

Step-by-Step Development Process for a Medical AR App
  1. Analysis and regulatory — device classification, documentation requirements.
  2. Prototyping — MVP for one scenario, demo to client.
  3. AR module development — tracking, rendering, physics.
  4. 3D content pipeline — modeling, texturing, optimization for ARKit/ARCore.
  5. QA and medical testing — usability tests with doctors, accuracy verification.
  6. Deployment and support — App Store/Google Play publication, monitoring.

At each stage, we involve physicians or instructors for validation.

What's Included in Our Medical AR Development Service

  • Regulatory documentation (IEC 62304, FDA/CE preparation)
  • Source code and version control access
  • Developer training and handover
  • 6 months of post-launch support and updates
  • 3D model optimization and asset management

Performance and Compatibility

DICOM rendering on mobile is not for weak devices. ITK library via C++ bridging or cornerstone.js in WebView for 2D. For volume rendering — Metal (iOS) / Vulkan (Android) with raycast shaders. On iPhone 14 Pro — acceptable, on budget Android — not, requiring server-side rendering with frame streaming. We tailor the architecture to your budget and target devices.

Device AR Rendering Performance Recommended Scenario
iPhone 13/14 Pro 60 FPS, high detail All scenarios
Mid-range Android (Snapdragon 8xx) 30–45 FPS, medium detail Atlas, rehabilitation
Budget Android 15–25 FPS, low detail Atlas only (with simplified models)

Timelines and Cost

Timelines: educational atlas — 8–14 weeks, cost starting at $50,000; system with DICOM and regulatory — 6–18 months, from $200,000. Cost is calculated individually but typical ranges are provided above. Get a preliminary estimate — write to us, and we'll prepare a plan for your scenario.

With over 7 years of experience in medical AR and 20+ completed projects, we combine deep tech expertise with regulatory know-how. Founded in 2017, we have delivered solutions for top medical institutions.

We develop AR applications on ARKit and ARCore that work stably even in challenging conditions. Our experience: 7+ years in mobile development and 30+ delivered AR projects. Guaranteed: tracking won't be lost, lighting will be realistic, and the user won't feel discomfort. Certified Apple and Google developers.

Why does tracking get lost and how to fix it?

ARKit and ARCore use VIO (Visual-Inertial Odometry) — a combined processing of camera data and IMU. Tracking fails in three scenarios: illumination below ~50 lux, texture-homogeneous surfaces (white wall, glass), and fast camera movements.

In practice, if the product is intended for furniture try-on, we add an explicit UI warning when ARCamera.TrackingState.limited(.insufficientFeatures). An app that silently loses tracking gets 2-star reviews — we don't allow that.

Plane detection is configured via ARWorldTrackingConfiguration.planeDetection = [.horizontal, .vertical]. Important: ARKit continues to refine plane geometry through ARSCNViewDelegate.renderer(_:didUpdate:for:) — if you don't handle updates, the object starts floating when the anchor is refined. Our team solves this at the architecture stage, not during testing.

AR Foundation: cross-platform with nuances

Unity AR Foundation is an abstraction layer over ARKit and ARCore. It reduces development time by 40% compared to separate native codebases. But some features (e.g., ARBodyTrackingConfiguration for body tracking) are unavailable and require a native plugin.

For React Native and Flutter, direct AR Foundation is missing. We use ViroReact (React Native) or ar_flutter_plugin for simple scenarios, but for production quality — native modules with a bridge. Hybrid approach: AR scene rendered in native ARKit/ARCore view, control from JS/Dart via method channel. Included in our standard delivery.

Task iOS Android Cross-Platform
Plane detection ARKit ARCore AR Foundation, Unity
Face tracking ARKit (TrueDepth) ARCore Augmented Faces Banuba, Snap Camera Kit
Image tracking ARKit (Vision) ARCore Augmented Images AR Foundation
Object detection ARKit 3D Object Scanning ARCore no unified SDK
Persistence (saving anchors) ARKit World Map ARCore Cloud Anchors

Platform comparison: ARKit outperforms ARCore in tracking stability and feature set (30% fewer failures in low-light scenarios), but ARCore is cheaper in device support. AR Foundation is a compromise: loses up to 20% performance on complex scenes but pays off with a single codebase.

Try-on: product fitting via AR

Fitting glasses, jewelry, cosmetics — a separate class of tasks. Here, face tracking is needed, not plane detection.

ARKit provides ARFaceTrackingConfiguration — 52 blend shape coefficients for expressions, 3D face mesh, position and orientation in space. Works only on devices with TrueDepth camera (iPhone with Face ID).

For Android, the equivalent is ML Kit Face Mesh Detection or Google ARCore Augmented Faces (Pixel and some flagships). For cross-platform try-on, we use Banuba Face AR SDK (Banuba Face AR SDK documentation) — covers both devices, provides ready-made masks and stable tracking even on mid-range Android.

Try-on quality critically depends on 3D product models. Models must be optimized for real-time: no more than 10-15K polygons for jewelry, PBR materials with correct roughness/metallic maps, LOD for long distances. Within our engagement, we provide ready-made optimization guides.

How to achieve realistic lighting in AR?

ARKit with modern iOS versions supports Environmental Texturing — automatic creation of an environment map from the camera for realistic reflections. Enabled via ARWorldTrackingConfiguration.environmentTexturing = .automatic. Without it, metallic and glass materials look plastic.

ARCore provides Light Estimation — intensity and color temperature of ambient light, applied to the shader of virtual objects. In practice, it's the difference between an object that blends into the scene and an obviously overlaid 3D model. We guarantee that the final image doesn't betray virtuality.

What's included

  • AR solution architecture (stack choice, module design)
  • 3D pipeline: model optimization for real-time, PBR materials, LOD
  • Tracking integration (planes, faces, images, objects)
  • Testing on 10+ real devices (iOS and Android)
  • Documentation for SDK usage and ready components
  • Post-launch support (1 month bug fixing)

Timeline and estimation

Simple AR scene with placing one 3D model on a plane — 1-2 weeks. Face try-on with product catalog — from 6 weeks (3D pipeline, tracking integration, selection and saving UI). Full AR shopping with cloud anchors and multiplayer — from 3 months. We'll estimate your project in 1 day — contact us to discuss your AR idea.