AR & VR Development Company in Berlin

Immersive budgets in Berlin are set by headset count and content minutes, in that order. Projects size up as a scoped AR or VR proof of concept at Berlin rates over six to ten weeks, covering one platform target, a content sample, and a hosted demo build, a production WebAR campaign with body or face tracking including BFSG accessibility, DPIA, and analytics, or a full industrial AR programme on HoloLens 2 or Quest 3 with CloudXR rendering and SAP/Siemens Teamcenter integration. Berlin rates sit below Munich and roughly level with Hamburg, but talent depth (ex-Holo-Light, ex-Innoactive, ex-Demodern) is higher than most regional German cities. We give fixed-fee proposals rather than open T und M estimates.

Article 9 DSGVO treats biometric data used to uniquely identify a person, plus health data, as special categories requiring a stricter legal basis than ordinary personal data. In AR and VR that pulls in eye-tracking traces, pupillometry, gait and skeleton data, facial blendshapes used for avatar driving, and any emotion or attention inference. Our discovery phase classifies every captured signal, then designs the pipeline so Article 9 data is processed on-device or inside eu-central-1 under a documented Article 9(2) basis (explicit consent for consumer apps, employment law plus collective agreement for workplace training, or healthcare exemption for clinical use). Each build ships with a DPIA the Berliner Beauftragte für Datenschutz und Informationsfreiheit (BlnBDI) and your internal Datenschutzbeauftragte can sign without redrafting.

The Barrierefreiheitsstärkungsgesetz (BFSG) transposed the European Accessibility Act into German law and took binding effect on 28 June 2025. It covers consumer-facing digital products and services, including AR and VR experiences offered to the public, with limited micro-enterprise exemptions. In practice that means alternative interaction modes for users who cannot complete six-degrees-of-freedom motion, subtitles and audio description for narrative VR, contrast and motion-sickness mitigations, and seated or single-controller pathways. Our delivery template includes a BFSG conformance statement aligned with EN 301 549 and the W3C XR Accessibility User Requirements, plus a tested fallback build. Non-compliant releases face market-surveillance action from the Marktüberwachungsbehörde der Länder.

Yes. We ship assembly guidance, remote expert, and digital-twin maintenance applications on HoloLens 2, Magic Leap 2, and ruggedised Quest 3 for suppliers to BMW Leipzig, Tesla Grünheide, Mercedes-Benz, Siemens, and the Berlin-Brandenburg aerospace cluster around BER. Builds integrate with SAP S/4HANA, Siemens Teamcenter, PTC Windchill, and Aveva digital-twin stacks, with rendering offloaded to AWS eu-central-1 via NVIDIA CloudXR when on-device GPU budget is tight. Every shop-floor deployment runs through a works council (Betriebsrat) consultation under § 87 BetrVG, because cameras and biometric sensors trigger co-determination rights. We deliver the Betriebsvereinbarung draft language alongside the technical build.

Apple Vision Pro launched in Germany in mid-2024, and Berlin enterprises are the early B2B adopters for design review, executive collaboration, and premium retail. We build native visionOS 2 apps in SwiftUI with RealityKit and ARKit for hand and eye tracking, and we use Unity 6 PolySpatial when an existing Quest or PC VR codebase must port across. Vision Pro raises a specific Article 9 question because Optic ID, gaze data, and Persona avatars sit on the biometric/health line; our visionOS template keeps gaze inference fully on-device, never persists raw eye-tracking off the headset, and surfaces a German-language consent flow that meets DSGVO Article 7 and BlnBDI guidance. EnterpriseAPI access is scoped under a signed Apple Developer Enterprise Programme agreement.

Yes. We have built and shipped WebAR virtual try-on for footwear, eyewear, watches, and apparel using 8th Wall, Banuba, and custom Three.js plus MediaPipe pipelines, with body-tracking and facial-mesh inference running either on-device via WebAssembly or inside eu-central-1 under a documented Auftragsverarbeitungsvertrag (DPA). Berlin and Hamburg fashion clients in the Otto Group, Zalando, and About You orbit expect sub-three-second time-to-AR on mid-range Android, full IDFA and TCF v2.2 consent handling, and a BFSG accessible fallback for users who decline camera access. Conversion lift instrumentation feeds existing GA4, Adobe Analytics, and Snowplow stacks running on EU-only infrastructure.

Regulation (EU) 2024/1689 (the EU AI Act) entered into force in August 2024 with phased applicability through 2026 and 2027. For AR and VR, three triggers matter: emotion recognition in workplace or education contexts is restricted or prohibited under Article 5; biometric categorisation and real-time biometric identification in public spaces are restricted; and any system used in safety components, employment decisions, or critical infrastructure training may be high-risk under Annex III. Our discovery phase runs a Codazz EU AI Act classification on every AI feature inside the headset, scopes Annex III obligations (risk management, data governance, technical documentation, human oversight, accuracy and robustness, post-market monitoring) into the build, and produces the conformity documentation a notified body or the BNetzA national authority can review.

Yes. We have scoped VR pipelines for chronic-pain rehabilitation, surgical planning, exposure therapy for anxiety disorders, and stroke motor rehabilitation, designed against Charité, Vivantes, and Berlin Institute of Health research-IT requirements. Where the software qualifies as a medical device under MDR (Regulation (EU) 2017/745), we work to Class I or Class IIa with a CE marking strategy, ISO 13485 quality management, IEC 62304 software lifecycle, and ISO 14971 risk management. DiGA (Digitale Gesundheitsanwendung) reimbursement applications to the BfArM are scoped separately when a clinical-evidence pathway is in place. Patient-identifying data stays inside eu-central-1 or Azure Germany West Central under a §203 StGB-aware processing agreement.