Integrating In-App Purchases for VR Applications

Integrating In-App Purchases for VR Applications

We often face the task of integrating in-app purchases (IAP) for VR applications. Meta Quest, SteamVR, and PCVR impose different requirements on payment systems. A Quest application must use the native Meta IAP SDK — third-party processors are prohibited in the Meta Store. For Steam — Steamworks API. If the project targets both platforms, an abstraction that switches the implementation based on the runtime platform is needed. Starting IAP integration without understanding the target store's requirements is a guaranteed revision.

How to Avoid Mistakes When Testing IAP on Quest?

The Meta Platform SDK (com.meta.xr.sdk.platform) provides IAP via IAP.GetProductsBySKU and IAP.LaunchCheckoutFlow. All SKUs must be set up in advance in the Meta Developer Console under a specific App ID. Without this, calling LaunchCheckoutFlow will return a PURCHASE_NOT_ALLOWED error even in test mode. Testing IAP on Quest: In the Developer Console, add test users in the Test Users section of your organization. Only they can make test purchases without real charges. Without this setting, developers regularly encounter IAP 'not working' — although the issue is the lack of test account permissions. Subscriptions in Meta IAP are a separate product type (SUBSCRIPTION). Subscriptions have trialPeriodDays, billingPeriod, startDate. To check an active subscription, use IAP.GetCurrentEntitlements — returns all active entitlements, including subscriptions. Important: an entitlement does not disappear immediately upon subscription cancellation — it remains active until the end of the paid period. You must check ExpirationTime, not just the existence. Restoring purchases: Meta automatically restores non-consumable purchases when logging in with the same account via IAP.GetViewerPurchases. Consumable purchases (coins, consumables) are not restored — they must be consumed via IAP.ConsumePurchase after granting to the player.

Steamworks and PCVR: Server-Side Verification Is Mandatory

For Steam, we use Steamworks.NET — a C# wrapper over the Steamworks API. Microtransactions through Steam work via SteamUser.GetSteamID + server-side verification via the Steam Web API. Unlike Meta, Steam recommends server-side purchase verification: the client initiates a purchase → Steam returns an OrderID → the game server verifies via ISteamMicroTxn/FinalizeTxn → grants the item. Without server verification, purchases can be faked through memory editing. For VR-only games on Steam without a dedicated server (single-player or P2P), verification is handled via Steam Inventory Service — Steam itself stores inventory items, and client-side cheats do not affect Steam Inventory.

Unity IAP as a Cross-Platform Abstraction

Unity In-App Purchasing (com.unity.purchasing) supports Meta Store via Meta Appstore IAP and Steam via Steam IAP in a single API. IStoreController.InitiatePurchase(product) works identically on both platforms with proper Builder configuration. Unity IAP reduces development time by 30–40% compared to integrating two native SDKs separately. The issue with Unity IAP on Meta Quest: Unity IAP uses Google Play Billing as a base for Android. Quest is also an Android-based platform, and Unity IAP may default to using Google Play Store instead of Meta Store. You must explicitly set StandardPurchasingModule.useFakeStoreAlways = false and add Meta Store via builder.AddStoreConfiguration. Limitation: Unity IAP does not support all native SDK features — for example, Meta-specific subscriptions with trials require additional code outside Unity IAP. If the project requires native features, Unity IAP is used only as a fallback, with Meta SDK as primary.

Why Is Server-Side Verification Mandatory for Pay-to-Win VR Games?

Chargebacks and refunds in Meta Store: a user requests a refund, Meta approves it, but the entitlement in the game is already activated. If the game granted the item upon purchase and does not re-check the entitlement, the player received the item for free. Protection: do not grant expensive items instantly on the client. Pattern: LaunchCheckoutFlow → GetViewerPurchases (check status) → grant through the server with a database record. At each application launch — re-check active entitlements via GetViewerPurchases and reconcile with the server record. On mismatch — block the item. For free-to-play VR games with cosmetic purchases, server verification is often not critical (a stolen skin does not break the economy), but for games with pay-to-win elements or subscriptions, it is mandatory.

What Is Included

• Setup of Meta IAP SDK with correct SKUs in Developer Console
• Integration of Steamworks for microtransactions with server-side verification
• Creation of a cross-platform abstraction via Unity IAP with fallback to native SDKs
• Testing on real devices with test accounts
• Documentation of the IAP system and maintenance instructions
• Post-launch support: purchase monitoring and refund issue resolution

We have implemented IAP for 15+ VR projects over many years. We will assess your project and offer the optimal solution — from simple integration to comprehensive fraud protection. Contact us to discuss the details.

The cost is calculated individually after requirements analysis: platforms, product types, server infrastructure availability.

VR and AR Development

When we first launch a project in a VR headset, most teams face the same thing: technically everything works, but in the headset either motion sickness occurs, or hands 'float' with a delay, or the scene looks jerky at the periphery. These are not bugs in the usual sense — they are a consequence of the fact that VR/AR development requires a different approach to render architecture, interaction, and UX from the very beginning of the project. Our experience: over 7 years in game dev, 15+ completed VR/AR projects for Meta Quest, SteamVR, PSVR2, HoloLens. We work with teams that need not just a prototype but a production‑ready application with a stable frame rate.

Platforms and SDKs

We work with all relevant stacks. We use OpenXR as the base layer wherever possible — it provides cross‑platform compatibility between Meta, Valve Index, HP Reverb and other PC VR devices. On top of OpenXR, we build on the XR Interaction Toolkit (Unity) or VR Expansion Plugin (Unreal). Contact us for a stack assessment tailored to your project.

How to minimize motion sickness in VR locomotion?

Locomotion — the main source of motion sickness for inexperienced VR users. According to research, about 70% of users experience discomfort with improper movement settings Oculus Developer Guidelines. Teleportation — standard navigation method when smooth movement is undesirable.

Components from XR Interaction Toolkit: TeleportationArea, TeleportationAnchor, TeleportationProvider. Basic implementation works out of the box, but for production we refine it in four steps:

1. Setting up XRRayInteractor with a curved ray (Bend Ray) — the teleportation arc looks more natural than a straight ray and is perceived better by users.
2. Adding a valid landing zone — a visual indicator changes color when hovering over an obstacle (red/green).
3. Implementing fade transition — smooth screen fade (black fade) before teleportation reduces disorientation.
4. Rotation snapping — after teleportation we offer snap rotation by 45° or 90° instead of smooth, reducing motion sickness risk.

For projects requiring smooth locomotion (action games, simulators), we use comfort settings: vignetting during movement, reducing FOV during acceleration. Settings are available to the user in the menu — different people have different sensitivity thresholds. The difference between kinematic and physics‑based movement: kinematic gives instant hand following but lets objects pass through walls; physics‑based via Joint provides realistic collisions but requires velocity damping and max joint force tuning. We choose based on the type of interaction.

How to make object grabbing in VR physically realistic?

This is the most underestimated part of VR development. Clients often perceive it as 'just hand animation', but in practice it is a complex system where physical correctness, responsiveness, and comfort conflict.

Grab (grabbing)

XR Interaction Toolkit provides three types of Interactable for grabbing:

• XRGrabInteractable — standard grab, object follows controller via physics joint or direct position/rotation
• XRSimpleInteractable — for objects without physical movement (buttons, levers)
• Custom Interactable by inheriting from XRBaseInteractable

Attach Transform — a frequently ignored detail. Each Interactable must have a properly configured Attach Transform (the point where the hand 'attaches'). Without it, the pistol grip will be at the center of the mesh, not where it is held.

For weapons and tools with two‑handed grab — a separate TwoHandGrab system: leading hand determines position, the second — orientation. XR Interaction Toolkit supports this via XRTwoHandGrabInteractable or custom logic with two Attach Points.

Throw (throwing)

Velocity smoothing is critical for realistic throwing because the Rigidbody.velocity at the moment of controller release reflects instantaneous speed, often incorrect due to tracking discretization. The user makes a quick wrist movement — but the object flies half as fast.

Solution: velocity smoothing over the last N frames (typically 5–10 frames, ~80–160 ms at 60 Hz) before release. XR Interaction Toolkit does this via VelocityEstimator. Additionally, we apply a velocity scaling multiplier — a small speed increase (1.2–1.5×) makes throws subjectively more satisfying. Angular velocity (for objects that should spin in flight) is also averaged similarly.

AR: Plane Tracking and Environment Interaction

AR adds a different class of problems — working with real, unpredictable environment. AR Foundation — a cross‑platform layer on top of ARKit and ARCore. Most basic features (plane detection, raycasting, image tracking, face tracking) are available through a unified API.

Plane Detection

ARPlaneManager detects horizontal and vertical planes. Practical nuances:

• Initialization takes time — the user must look around the room while the system builds a map. An explicit onboarding with instruction 'slowly move the camera across surfaces' is needed.
• Planes are unstable — their boundaries and position are updated as data accumulates. Objects placed on a plane need to be attached via parent to ARPlane, not to world coordinates.
• Plane merging — two detected floor segments may merge into one, moving the anchor. For critical anchors, use ARAnchor instead of direct attachment to the plane.

Image tracking (via ARTrackedImageManager) quality directly depends on the quality of reference images. Images with high detail frequency and contrasting edges (like a QR code but stylish) track more reliably than smooth logos. ARCore Geospatial API — for outdoor AR with real‑world coordinate binding (accuracy up to 10 cm in well‑mapped areas).

Optimization for VR: Frame Rate and Comfort

VR requires stable high frame rate. About 60% of development time in mobile VR goes to optimization, not functionality — retrofit costs twice as much as proper architecture from the first sprint.

Single Pass Instanced Rendering

The main render optimization in VR. Without it, the scene is rendered twice (once per eye), doubling draw calls. Single Pass Instanced renders both eyes in one pass via instancing: geometry is processed once, the shader gets two view/projection matrices through GPU instancing. Enabled in Unity via XR Plug-in Management > Rendering Mode: Single Pass Instanced. Important: custom shaders must support SPI — standard URP/HDRP shaders support it, custom HLSL requires modifications (UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX and related macros). Applying this technique reduces draw calls by 40–50%, making it twice as efficient as naive double rendering.

Foveated Rendering

On Meta Quest, Fixed Foveated Rendering (FFR) is available — reducing resolution at the periphery where visual acuity is lower. Configured via OVRManager or Meta XR SDK:

OVRManager.fixedFoveatedRenderingLevel = OVRManager.FixedFoveatedRenderingLevel.High;
OVRManager.useDynamicFixedFoveatedRendering = true;

Dynamic FFR automatically increases the level when frame rate drops — more convenient than fixed in scenes with variable load.

IPD and Comfort Settings

IPD (Inter‑Pupillary Distance) — affects depth perception. At the programmable level on most devices, only reading IPD is available (OVRPlugin.GetSystemDisplayFrequency), physical adjustment is on the headset. For applications requiring precise positioning (medical simulators, training), we account for IPD in scene scale calculations.

Haptics

Haptic feedback — an underestimated tool. Even a simple vibration response when grabbing an object or hitting significantly increases the sense of presence. On average, integrating haptic patterns takes 30–80 hours per project.

XR Haptics via OpenXR:

var hapticImpulse = new UnityEngine.XR.HapticCapabilities();
InputDevice device = InputDevices.GetDeviceAtXRNode(XRNode.RightHand);
device.SendHapticImpulse(0, amplitude: 0.5f, duration: 0.1f);

For complex patterns (tactile 'texture' of a surface when touched, increasing vibration when drawing a bowstring) we use Meta Haptics Studio — allows designing haptic clips visually. This can reduce time spent on manual haptic tuning by about 30%.

What does VR/AR application development include?

When ordering a turnkey project, we provide the following deliverables:

• Architectural document with stack description, render logic, and interaction system
• Working prototype (MVP) for testing on target device
• Integration of necessary SDKs (Meta XR, OpenXR, AR Foundation, etc.)
• Optimization for target frequencies 72/90/120 Hz with draw call and FPS profiling
• Testing on physical hardware (Quest, SteamVR, HoloLens) with user involvement
• Full documentation for build, deployment, and support
• Training for the client's team (workshop on XR Toolkit)
• Warranty support for 1 month after delivery

What affects cost and timeline?

VR/AR projects are more expensive than regular games of similar scope. Iterations are slower — each fix must be tested in the headset, an emulator does not convey the real experience. Motion sickness forces reworking some conceptual decisions after the first playtest. Optimization takes a significant portion of time — for mobile VR (Quest) up to 60–70% of the cycle. For Quest projects, we start optimization from the first sprint. The cost of basic SDK integration (XR Interaction Toolkit) varies depending on the scope of custom Interactable. Typical budgets for a full Quest project range from $25,000 to $80,000 depending on complexity, number of custom interactions, and depth of optimization. Proper architectural planning from sprint one typically saves 40% on later rework compared to fixing performance bottlenecks retroactively.

Get a consultation on your project — we will assess the task, stack, and timelines. Order turnkey VR/AR application development with a guaranteed stable frame rate.