Developing a Mobile AR App for Marketing

Our AR app development for mobile AR applications in AR marketing leverages image tracking, face filters, ARKit, ARCore, WebAR, and 8th Wall for high AR engagement with progressive loading.

Imagine a brand launching a limited-edition sneaker collection. The user scans a QR code on the box. The camera opens. A 3D sneaker appears above the box—spinning, glowing, with sparks flying around. Sharing to Instagram Stories drives virality and brand awareness. We’ve implemented such cases for 15+ brands. Success depends on technical details. If the model loads longer than 3 seconds or tracking breaks, the user closes the app forever.

That’s why we spend 30% of our time tuning reference images: we adjust contrast, convert to grayscale, and test tracking under different lighting conditions. Only then do we start developing the immersive scene. In this article, we’ll break down key technical solutions for marketing AR—from image tracking to face filters and WebAR.

How Image Tracking Turns Packaging into an AR Anchor

Most marketing AR cases rely on image tracking: packaging, print ads, billboards, or business cards are recognized as anchors. Content plays over them. On iOS, we use ARImageTrackingConfiguration with ARReferenceImage. The reference image can be loaded from an asset catalog or dynamically from a server. On Android, we use AugmentedImageDatabase from ARCore.

Critical parameters for a reference image:

• Minimum physical width: 15 cm (smaller means tracking unstable).
• High contrast, unique texture: a logo on a white background is bad; a bright pattern with details is good.
• ARKit requires specifying physicalWidth in meters when registering, otherwise the content scale will be wrong.

ARKit recommends using ARImageTrackingConfiguration only with high-contrast images. Native apps process tracking 3 times faster than WebAR for complex scenes (based on our tests).

Quick Start Steps for AR Campaign

1. Define your anchor media (packaging, print ad, billboard, etc.)
2. Create or adapt 3D assets (USDZ/glTF, ≤5 MB)
3. Choose native app or WebAR based on performance needs
4. Test image tracking under various lighting conditions
5. Deploy and analyze via Firebase Analytics

Comparison: WebAR vs. Native App

Why Face Filters Require Deep Integration

For branded masks (Snapchat-style), on iOS we use ARFaceTrackingConfiguration. It works only on TrueDepth camera (iPhone X and newer). ARFaceAnchor returns 52 blend shape coefficients (browDown, eyeBlink, mouthSmile, etc.). This allows the mask to respond to smiles, blinks, raised eyebrows—not just a texture but an animated character.

On Android, the counterpart is ML Kit Face Mesh (478 points). Without a depth camera, the binding is less accurate. For production face filters on both platforms, we often use Spark AR (Meta) or Lens Studio (Snapchat) when publishing through their platforms. Alternatively, we use ARCore + custom renderer for standalone apps.

Face Filter SDK Comparison

How We Optimize AR Scene Performance

Marketing AR is an impulsive context. Users have 3 seconds of patience. Therefore:

• USDZ/glTF models ≤ 5 MB for first display, remainder loaded as needed.
• Progressive loading: first a low-poly placeholder, then the full model.
• Background preloading when the app opens using URLSession with .background configuration.
• Animations via .reality files (Reality Composer) or USDZ animation tracks—not separate JSON with keyframes.

AR interaction analytics via Firebase Analytics: ar_session_started, ar_target_detected, ar_content_shared. Marketers need conversion data from AR to sharing, average time in AR, and repeat launches.

What Metrics Guarantee AR Campaign Success?

According to a 2023 study by eMarketer, campaigns with an AR element show 2.5x higher engagement compared to regular ads. AR-to-sharing conversion averages 15% (Firebase data). Payback period: 1 to 3 months with 200% ROI. For a typical $25,000 campaign, that means $50,000 in return.

What Our Work Includes

• Deliverables: Source code (Swift/Kotlin), integration documentation, analytics dashboard access (Firebase), 30-day post-launch support, training for your marketing team.
• Investment: From $12,000 for simple image tracking to $50,000 for full app with multiple scenes. Typical budgets range from $10,000 to $80,000.
• Timelines: Simple image tracking with 3D animation: 3–5 weeks. Face filter with branded mask: 4–6 weeks. Full application with multiple scenarios: 8–14 weeks.

We’ve worked with AR since the first commercial SDKs. We completed 15+ projects for B2B clients. Reach out to discuss your task.

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.

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.