DEV Community: A Plus Games Studio

ARKit vs ARCore vs WebXR: Choosing Your AR Stack (2026)

A Plus Games Studio — Tue, 13 Oct 2026 11:11:37 +0000

The four options

ARKit is Apple's native AR framework for iPhone and iPad. ARCore is Google's, primarily for Android. Unity AR Foundation lets one Unity project target both. WebXR delivers AR in a web browser with no install.

The fact that decides most projects

As of September 2026, Safari on iPhone does not support WebXR augmented reality. That single limitation shapes almost every AR decision, because in many markets a large share of the people you want to reach are on iPhone.

It means a browser-only AR experience gives iPhone users either no AR or a reduced fallback. If your audience skews to iPhone, that is a serious constraint on web AR.

Native ARKit

Best accuracy and features on iPhone. Direct access to surface detection, image and object tracking, face tracking, location anchors, and LiDAR-powered scene reconstruction on devices that have LiDAR, such as iPhone 18 Pro. The trade-off: iPhone only, and users must install an app.

Native ARCore

Best choice for Android-first projects, and home to the Geospatial API for location-based AR using Google's visual positioning. The trade-off mirrors ARKit: Android-focused, and an install is required.

Unity AR Foundation

One codebase, both platforms. It wraps ARKit and ARCore, so you get native AR tracking on both while writing most of the app once. For most commercial AR apps that need to work well on iPhone and Android, this is usually the right default. The trade-offs are an app install and the occasional platform-specific feature that needs native work.

WebXR

Maximum reach, zero install — a link or a QR code opens it instantly. Excellent for campaigns, events and quick demos. The trade-off is the iPhone gap described above, plus generally less capability than native.

How to choose

Campaign, event, packaging, "try it in five seconds": WebXR, accepting a reduced iPhone experience or a separate iPhone path.
Commercial app that must be accurate on every phone: Unity AR Foundation.
iPhone-only, needs the deepest Apple features: native ARKit.
Location-based AR at city scale: consider ARCore Geospatial, or ARKit location anchors where they are supported.

The expensive mistake is choosing web AR for reach, discovering in testing that most of the target audience is on iPhone, and rebuilding natively. Decide based on who your users are before anything else.

Common questions

What is the difference between ARKit and ARCore?

ARKit is Apple's native AR framework for iPhone and iPad, and ARCore is Google's, primarily for Android. Each gives the best native AR on its own platform.

Can WebXR AR work on iPhone?

As of September 2026, Safari on iPhone does not support WebXR augmented reality, so browser AR gives iPhone users either no AR or a reduced fallback.

What is Unity AR Foundation?

A Unity framework that wraps ARKit and ARCore so one project can deliver native AR tracking on both iPhone and Android. For most commercial AR apps it is a sensible default.

Should I build my AR experience for web or as an app?

Choose web when instant reach through a link matters most. Choose an app, often built with Unity AR Foundation, when the experience must be accurate on every phone, especially if many users are on iPhone.

Originally published on A Plus Games Studio. I work at A Plus Games Studio, a game and AR/VR studio in Sacramento.

Unity 6 Upgrade Guide (2026): Built-in Pipeline Deprecated

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

If your game still uses the Built-in Render Pipeline, you do not have to panic, but you do need a plan. Unity 6.5, released in June 2026, officially deprecated Built-in. It will keep receiving fixes until at least Unity 6.7 LTS, which Unity expects at the end of 2026, and is then supported for two more years before it is removed. Unity has also said development will concentrate on the Universal Render Pipeline (URP), with HDRP in maintenance mode. For most mobile, PC and XR games, the destination is URP, and the best time to move is between releases, not the month before a launch.

What actually changed in 2026

Built-in Render Pipeline deprecated (Unity 6.5). No new features, fixes until at least 6.7 LTS, then a two-year support window, then removal.
HDRP in maintenance mode. Unity announced in February 2026 that rendering development will focus on URP. HDRP keeps working but stops gaining features.
Conversion tools. Unity 6.5 added a command-line tool for converting Built-in assets to URP, on top of the existing Render Pipeline Converter in the editor.
Higher Android floor. Unity raised the minimum Android API level to 26 (Android 8.0) in the 6.5 cycle.
Releases moved fast. 6.4 arrived in March 2026 with the Entity Component System and Project Auditor built into the editor, 6.5 in June, and 6.6 builds were shipping by October. Unity's forum now tells 6.5 users to move to 6.6 or later.
Havok no longer bundled. From Unity 6.3, Havok Physics is no longer included in Pro, Enterprise or Industry plans. Projects that rely on it need a separate arrangement with Microsoft's Havok team.

Who needs to act, and how soon

Your project	Risk	What we would do
Live game on Unity 2021 or 2022 LTS with Built-in	High over 12–24 months	Plan a Unity 6 LTS upgrade and a URP move as one project, between content updates
Unity 6.0 LTS with Built-in	Medium	Stay on 6.0 LTS for now; convert to URP before you jump to 6.7 LTS
New project starting today	None if you choose well	Start on URP; do not start anything new on Built-in or HDRP
HDRP PC or console game	Low short term	Keep shipping; no new HDRP features are coming, so weigh URP for the next title
Already on URP	Low	Upgrade engine versions on a schedule and test on your lowest target device

A rule of thumb: never combine an engine upgrade, a render pipeline change and a big content update in one release. Each of them can break builds on its own.

What breaks when you move from Built-in to URP

Standard materials convert automatically. The expensive parts are the things Unity cannot convert for you:

Custom shaders. URP has no surface shaders. Hand-written Built-in shaders must be rebuilt in Shader Graph or rewritten as URP HLSL. On stylised games this is usually the biggest line item.
Post-processing. The old Post-Processing Stack v2 is replaced by URP's Volume system. Bloom, colour grading and vignette look slightly different and need re-tuning by an artist.
Camera code. OnRenderImage, GrabPass and command buffers attached to cameras do not work in URP. Effects built on them move to Renderer Features.
Lighting. Lightmaps must be rebaked, light counts per object are limited differently, and shadows need new settings to look and perform the same.
Projectors and old effects. Projectors become Decal Projectors; some legacy image effects have no direct equivalent.
Asset Store packages. Every third-party shader, water, sky or VFX package needs a URP version. Some were abandoned and have to be replaced.

A safe upgrade plan in seven steps

Audit. Run Project Auditor and list every custom shader, camera effect, render callback and third-party package. This list is your real estimate.
Branch. Do the work on a separate branch in version control with a frozen content scope. Unity Version Control no longer charges per seat on its public cloud, so there is no excuse to skip it.
Upgrade the engine first. Move to the target Unity 6 LTS on Built-in, fix compile errors and deprecated APIs, and ship nothing until the game plays exactly as before.
Convert the pipeline. Install URP, run the Render Pipeline Converter, then rebuild custom shaders and camera effects one by one.
Re-light and re-grade. Rebake lighting and have an artist compare screenshots side by side, scene by scene.
Profile on real devices. URP is usually faster on mobile, but only after tuning. Measure frame time on your weakest supported phone or headset, not on a development PC.
Regression test and stage the release. Full QA pass, then a staged rollout so a rendering bug reaches 5% of players, not all of them.

How long it takes

Project type	Typical scope of a Built-in to URP move
Small 2D or simple 3D mobile game, standard materials	About 1–3 weeks including testing
Mid-size 3D game with custom shaders and post-processing	About 4–8 weeks
Large game, many custom shaders, several platforms or XR	Two months or more, planned as its own milestone

These are rough guides, not quotes. The audit in step one turns them into a real number, and it is the step most teams skip.

When not to upgrade yet

If a game is near the end of its life, earns little and will not get major updates, staying on its current LTS until Built-in support ends is a legitimate choice. The same goes for a game shipping in the next few weeks: launch first, upgrade after. What is not a good choice is starting a brand new project on Built-in in 2026.

Where we fit

We upgrade and convert Unity projects for studios that would rather keep their own team on new content. Our senior engineers work inside your repository, start with the audit, and give you a fixed price before the pipeline work begins. See co-development and project rescue and Unity game development, or read what Unity costs in 2026 if licensing is part of the decision.

Sources: CG Channel on Unity 6.5 · Unity: planned breaking changes in 6.5 · Unity plans and pricing changes. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Unity Pricing 2026: Personal, Pro and Enterprise Explained

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Unity is free on the Personal plan until your company passes $200,000 in revenue and funding over the last 12 months. Above that you need Unity Pro at $2,310 per seat per year (or $210 per seat per month). Companies above $25 million in annual revenue need Enterprise, which is custom priced. There is no per-install Runtime Fee: Unity cancelled it in September 2024 for every version, including Unity 6. You pay per seat, not per download.

The plans at a glance

Plan	Who it is for	Price (2026)
Personal	Individuals and companies with up to $200K in revenue and funding	Free; splash screen optional in Unity 6
Pro	Companies above $200K in revenue or funding	$2,310 per seat per year prepaid, or $210 per seat per month
Enterprise	Companies above $25M in annual revenue	Custom; a minimum subscription may apply
Industry	Non-game industrial and enterprise use	Custom; unchanged in the 2026 update

Pro and Enterprise went up 5% on 12 January 2026. Existing subscribers moved to the new price at their first renewal on or after that date. Regional prices can differ because of tax and currency, so check the figure at checkout.

What happened to the Runtime Fee

In 2023 Unity announced a fee per game install, and the backlash was one of the biggest in the industry's history. Unity scaled it back, then cancelled it outright on 12 September 2024, and moved back to the seat-based model. If you read older articles warning about install fees, they are out of date. A hit game on Unity costs the same in licences as a flop with the same team size.

The smaller 2026 changes that still matter

Version control got cheaper. From 1 March 2026, Unity Version Control in the public cloud has no seat charges, the Personal limit of three free seats became unlimited, free storage rose from 5 GB to 25 GB per organisation, and 100 GB of egress per month is free, then $0.10 per GB.
Free build minutes. Build Automation includes monthly free Windows, Mac and Linux minutes on every plan.
Havok is gone from Pro. From Unity 6.3, Havok Physics is no longer included in Pro, Enterprise or Industry. If your game depends on it, budget for a separate Havok licence or plan a move to Unity Physics.

What it costs a real team

Team	Plan	Annual licence cost
Solo developer earning under $200K	Personal	$0
Indie studio of 3 after a funding round above $200K	Pro × 3 seats	$6,930
Studio of 10 developers and artists using the editor	Pro × 10 seats	$23,100
Same studio paying monthly	Pro × 10 seats, monthly	$25,200

Only people who open the Unity editor need a seat. Producers, marketers and most QA testers working with builds do not.

Unity vs Unreal vs Godot on cost

Unreal Engine is free to use for games, then charges a 5% royalty on lifetime gross revenue above $1 million per product, with a reduced rate under Epic's programme for games that also launch on the Epic Games Store. Godot is free and open source under the MIT licence, with no seats or royalties. Unity charges for seats and nothing on revenue.

For a game that earns $3 million over its life, Unreal's standard royalty is 5% of $2 million, or $100,000. Ten Unity Pro seats for three years cost $69,300. A five-person team on Unity for three years pays $34,650. Below $1 million in revenue, Unreal costs nothing, and for teams that have not yet earned or raised $200,000, Unity Personal costs nothing too. The engine fee is rarely the deciding factor; the team's skills, the target platforms and the type of game matter far more. Our comparisons of Unity vs Unreal and Unity vs Godot cover those trade-offs.

If a studio builds your game

When you hire an outside studio, the studio's developers work on their own licences while they build. Before you start, ask two questions in writing: whose licence covers the development, and which plan you will need if your own team takes the project over after handover. A good studio answers both in the proposal. Every project we deliver includes 100% source-code ownership, so the project is yours to open on your own Unity licence.

Bottom line

For most small teams, Unity is either free or a predictable line item of a few thousand dollars a year, and the Runtime Fee scare is over. The bigger 2026 cost risk is technical, not licensing: projects still on the deprecated Built-in Render Pipeline face an upgrade. Our Unity 6 upgrade guide explains how to plan it.

Sources: Unity: changes to plans and pricing · Game Developer on the Runtime Fee cancellation. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

How Much Does an Educational Game Cost to Build? (2026)

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

A focused educational mini-game can start at about $1,000 to $5,000, a curriculum-aligned game with many levels typically costs $30,000 to $80,000, a 3D simulation $80,000 to $150,000, and AR or VR learning experiences from $60,000 upward at market rates. What moves the price most is not the game itself but everything a school or training buyer needs around it: content volume, built-in assessment, teacher dashboards, accessibility, children's privacy compliance and the devices students actually have.

Budgets by type of learning game

Type	Example	Typical cost	Time
Focused mini-game	Times-tables runner, vocabulary match, phonics puzzle	From $999 (our Spark package); market $5K–$30K	4–8 weeks
Curriculum-aligned game	A season of science levels mapped to standards, with progress tracking	$30K–$80K	2–4 months
3D simulation	Virtual lab, engineering sim, safety training	$80K–$150K	3–6 months
AR learning experience	Campus trail, marker-based lessons, 3D models on worksheets	WebAR demo from $999; full apps quoted	4–12 weeks
VR learning experience	Field trips, procedural training, soft-skills role-play	From $2,999 for a focused app; market $60K–$400K+	2–9 months

The first column of prices comes from our current packages; the market ranges come from our game development cost guide. Our Campus Learning Trail and Marker AR Lesson demos show what browser-based AR for schools looks like in practice.

Five things that change the price

1. Content volume

One mechanic with 20 questions is cheap. The same mechanic with 400 questions, three difficulty levels, voice-over and two languages is a content production project. Agree the content plan early and decide who writes it: the subject experts or the studio.

2. Assessment and reporting

Schools and training buyers want proof of learning. Tracking answers, time and mastery per student, and showing it on a teacher or manager dashboard, adds backend and interface work, and it is usually what wins the contract.

3. Children's privacy

If the game is directed at children under 13 in the US, the FTC's amended COPPA rule applies, and full compliance has been required since 22 April 2026. Apple's Kids Category and Google Play's Families policy add their own rules on ads, analytics and parental gates. Collecting as little personal data as possible is the cheapest compliance strategy.

4. Accessibility

US public schools must meet WCAG 2.1 Level AA for web content and apps under the Department of Justice's ADA Title II rule, including tools provided by vendors. The Department moved the deadlines in April 2026 to April 2027 for larger public entities and April 2028 for smaller ones, but districts are already writing it into contracts. Captions, keyboard and switch access, colour-safe palettes and readable text are far cheaper designed in than added later.

5. School hardware and systems

Many classrooms run on Chromebooks and shared tablets, which favours lightweight web builds over app installs; see our guide to web games in 2026. Connecting to learning platforms through standards such as LTI 1.3, SCORM or xAPI, and supporting single sign-on, adds integration and testing time.

What makes a learning game work

Start from the learning objective, then find a mechanic where practising the skill is the gameplay, not a quiz between levels.
Fit the timetable. Sessions of 10 to 15 minutes fit into a lesson; long levels do not.
Give feedback instantly. Players should know why an answer was wrong, not just that it was.
Design for the teacher too. Easy setup, class codes and clear reports decide whether a game gets used twice.
Test with real students in a real classroom before scaling the content.

Motivation in games is not magic; our article on game design as applied neuroscience explains the mechanisms and the ethical lines.

How to start without a big budget

Build one complete lesson first: one mechanic, one topic, assessment working end to end, tested in a classroom. If students learn and teachers want more, funding the rest of the curriculum is an easier decision for everyone. We build educational games, AR learning trails and VR training in Unity and for the web; see AR development, VR development or our guide to AR learning trails.

Sources: Toy Association on the amended COPPA rule · Campus Technology on the ADA Title II extension. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

AI Game Generators in 2026: What They Can and Cannot Build

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

AI game generators in 2026 are excellent at getting you to a first playable idea and at producing parts of a game: concept art, placeholder 3D models, textures, sound effects and boilerplate code. They are not yet able to produce a finished, polished, store-ready game on their own. The hard parts of shipping, game feel, balanced systems, performance on real devices, monetisation and store compliance, still need experienced people. The smart move is to use AI to test ideas cheaply, then build the real thing properly.

The tools worth knowing

Engine assistants: Unity's in-editor AI

Unity retired its Muse tools on 1 October 2025 and replaced them, from Unity 6.2, with generators for sprites, textures, materials, animations and sounds, plus an assistant that answers technical questions, writes code and automates routine editor tasks. It uses a mix of Unity's own and third-party models. These tools live where the game is actually built, which makes them the most practical for real projects.

World models: DeepMind's Genie 3

Genie 3, introduced in August 2025, generates interactive worlds from a text prompt that you can move around in real time at 24 frames per second, remembering what it generated for about a minute. It is a striking research result and useful for imagining a mood or a space. It does not produce game code, rules, saves, multiplayer or anything you can publish.

Platform generators: Roblox Cube

Roblox open-sourced its Cube 3D model in 2025, which generates 3D objects from text, and exposed it to creators in Roblox Studio. It shows where platforms are heading: generation built into the tools creators already use.

Coding assistants

General AI coding assistants write gameplay scripts, editor tools and tests quickly, and are now part of most studios' daily work. They speed up experienced developers far more than they replace them, because someone still has to know what correct, fast, maintainable code looks like.

What AI does well today

Concepting. Dozens of visual directions in an afternoon instead of a week.
Placeholders. Stand-in models, textures and sounds so a prototype can be played before art is final.
Boilerplate code. Menus, save systems, editor tools and tests, reviewed by a developer.
Variations. Item names, flavour text, colour variants and minor props at volume.
Throwaway prototypes. A rough playable version of an idea in days, to decide whether it deserves a budget.

Where AI stops

Game feel. The weight of a jump, the snap of a hit, the timing of a combo. This is hundreds of small tuning decisions made by playing, not prompting.
Systems that hold together. Economies, progression and difficulty curves need design that anticipates how players will exploit them.
Consistency at scale. Generated assets drift in style. A shippable game needs a coherent art direction and assets built to technical budgets.
Performance. Generated models and code are rarely optimised for a mid-range phone or a standalone VR headset.
Shipping. Store submission, privacy rules, age ratings, ads and purchases, crash reporting and updates.
Ownership and disclosure. Check each tool's terms on commercial use, and disclose AI content where stores require it. Steam, for example, asks developers to declare AI-generated content.

From AI prototype to a game you can ship

Prototype the idea with AI. Prove the core loop is fun with generated placeholders. Keep it cheap and disposable.
Write down what worked. A short design document turns the prototype into decisions. Our game design document guide shows what to include.
Rebuild the foundation properly. Prototype code is usually thrown away. The production version needs clean architecture, real art direction and performance budgets.
Keep AI in the pipeline. Use it for concepting, variations and tooling, with artists and engineers in control of quality.
Test on real devices and real players. Then launch, measure and improve.

What this means for your budget

AI shortens some parts of a project, mainly concepting, early prototyping and routine code, but it does not remove design, engineering, QA or launch work. Expect savings on the early stages rather than a game for the price of a subscription. Our article on what AI changes in a game art budget goes into the numbers, and the cost calculator gives an instant range for a real build.

If you have an AI-made prototype and want to turn it into a real game, that is exactly the kind of project we take on: we review what you have, keep what is good, and give you a fixed price for the production version.

Sources: Unity: Muse retirement notice · CG Channel on Unity AI in 6.2 · Genie (world model) · Roblox: introducing Cube. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Mixed Reality App Development for Meta Quest 3 (2026)

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Mixed reality (MR) on Meta Quest 3 and Quest 3S shows the real world through the headset's colour cameras and places interactive virtual content in it. Developers can now read the shape of the room, anchor content to real surfaces, share that space between players in the same room and, with the user's permission, access the camera feed to recognise objects. That makes MR the most practical form of XR for many business uses, because people stay aware of their surroundings and can use it for longer.

What the platform gives you

Scene understanding

Meta's Mixed Reality Utility Kit (MRUK) provides a model of the user's room: walls, floor, ceiling, furniture and a mesh of surfaces. Your app can place a virtual pet on the real sofa, bounce a ball off the real wall or hide a target behind the real table. MRUK also handles raycasts against real geometry, so placement feels physical.

Anchors and shared spaces

Spatial anchors keep content fixed to the same real-world spot between sessions. Shared anchors let several headsets in one room agree on where things are, which makes colocated multiplayer and group training possible.

Camera access

The Passthrough Camera API gives apps access to the headset's forward cameras on Quest 3 and 3S, after the user grants a camera permission. In Unity it is used through MRUK's PassthroughCameraAccess component. Meta's samples pair it with Unity's on-device inference engine to detect objects and find their position in the room, for example recognising a piece of equipment and showing instructions on it.

Know the limits

Camera speed. When the API launched, Meta quoted up to 1280×960 per camera at 30 frames per second with about 40–60 milliseconds of latency. Fine for recognising objects and reading signs, not for tracking a fast-moving ball.
Privacy. Camera access requires explicit permission and a clear explanation. Design the app to work, in a reduced way, if the user says no.
Lighting and clutter. Scene understanding and recognition work best in reasonably lit, tidy rooms. Test in real homes and workplaces, not just the office.
Battery and heat. Running passthrough, scene mesh and on-device AI together is demanding. Budget performance from day one.

Where mixed reality wins

Use case	Why MR beats full VR here
Games in your living room	Real furniture becomes the level; players stay safe and social
Training on real equipment	Step-by-step guidance overlaid on the actual machine
Retail and product visualisation	See a product at true scale in your own space; see our AR furniture work for the same idea on phones
Fitness and wellbeing	Longer sessions with less discomfort because the room stays visible
Education	Shared 3D models in a real classroom with the teacher still visible

Design rules for MR

Respect the room. Never place content inside furniture or block exits. Use the room model to find clear space.
Make onboarding part of the experience. Room setup and permissions are the moment users drop off. Explain why and keep it short.
Blend, do not cover. Match lighting and shadows to the room so virtual objects look grounded.
Plan for every room size. Content must adapt from a small bedroom to an open office.

Business context in 2026

Meta ended its Quest for Business offering, which changed how companies buy and manage headsets; our article on what that means for enterprise VR covers the alternatives. Google's Android XR platform also supports mixed reality, so building on OpenXR where possible keeps a second platform open.

What an MR project costs

A focused single-scene MR experience starts at $999 and a full application at $2,999 under our current VR and AR packages. Projects with object recognition, colocated multiplayer, custom 3D content or enterprise device management are quoted individually; typical market ranges are in the VR development cost guide.

Sources: Meta: Passthrough Camera API overview · Meta: on-device ML with camera access · UploadVR on the Passthrough Camera API. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Steam Next Fest Guide: Dates, Rules and a Demo That Works

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Steam Next Fest is a week-long Steam event where unreleased games offer free demos to millions of players. The October 2026 edition runs from 19 October to 26 October, starting and ending at 10:00 am Pacific, and Valve plans the next edition for February 2027. Each game can take part only once, ever, so choose your edition carefully and arrive with a polished store page and a demo that hooks players in the first few minutes.

Valve's rules in plain English

One fest per game. Valve allows a title to participate in only one Next Fest.
Store page live. Your Steam store page must be published and public.
Demo playable at the start. A publicly playable demo must be live when the fest begins.
Not a paid prologue. A prologue or chapter one that customers can already buy does not count as a demo.
Release after the fest. The game must launch after the edition ends.
Livestreams are optional. There is no longer an official Steam livestream; developer streams appear in their own tab.

October 2026 timeline

Date	Milestone
31 August	Registration closed (11:59 pm PDT)
14 September	Demo build and store page due for review to join the press preview
28 September	All required items due for review
8 October	Press preview starts (10:00 am PDT)
19 October	Set the demo live before 10:00 am PDT; the fest begins
26 October	Fest ends at 10:00 am PDT

Missed it? The next edition is planned for February 2027. Valve publishes each edition's deadlines in Steamworks, and registration closes weeks before the event, so plan backwards from it.

Store page checklist

Capsule art that reads at thumbnail size. Most players see it small, in a crowded list.
A trailer that shows gameplay in the first seconds. No long logos or slow camera fly-throughs.
A short description that says what you do in the game, not just the setting.
Accurate tags, so Steam shows the game to the right players.
Screenshots of actual play, with the most exciting moment first.
A clear release window and the wishlist button easy to find.

What makes a demo work

Hook in the first five minutes. Start with the most distinctive part of the game, not a long tutorial.
Short and complete. One satisfying slice that ends on a high and a reason to want more.
Stable on minimum spec. A crash or poor frame rate in a demo becomes a lost wishlist and a bad first review of your studio. Test on low-end PCs and Steam Deck if you target it.
Ask for the wishlist. End screens and the main menu should invite players to wishlist and join your community.
Collect feedback. Add a simple in-game feedback link and watch analytics for where players quit.

During the week

Fix serious bugs fast and post short update notes; players notice active developers.
Run a developer livestream if you can; even small streams help players understand the game.
Reach out to streamers and press before the fest, not during it; the press preview exists for this.
Answer comments and Discord questions daily.

After the fest

Read every piece of feedback, fix what blocked players, and keep talking to the people who wishlisted. Decide whether to keep the demo live; many teams do, because it keeps converting visitors. Then set the launch date with the momentum in mind.

Choosing your edition

Pick the fest that sits a few months before your planned release, when the demo is polished but the full game is still being finished, so feedback can shape it. Do not enter early with a rough demo just because a fest is coming; you only get one.

Need a demo built or polished?

We build and polish PC demos in Unity, port mobile games to Steam and handle Steamworks integration. See PC and Steam game development, our guide to porting a mobile game to PC and Steam, and cross-platform game development.

Sources: Steamworks: Steam Next Fest October 2026. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Android XR App Development: A 2026 Guide for Galaxy XR

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Android XR is Google's operating system for headsets and smart glasses, and Samsung Galaxy XR, launched in October 2025, is the first device running it. You can build for it with Google's Jetpack XR SDK, with Unity, Unreal or Godot through the OpenXR standard, or on the web with WebXR. If you already have a Meta Quest game or app in Unity, most of it carries over: the work is input, performance tuning and store submission, not a rewrite.

Why it matters now

For years, standalone VR effectively meant one store. Android XR adds a second major platform backed by Google and Samsung, with the Google Play Store, Android's huge developer base and Gemini built in. Galaxy XR runs on Qualcomm's Snapdragon XR2+ Gen 2 and supports hand and eye tracking. Google has also shown Android XR smart glasses with eyewear partners, so skills built for the headset are likely to carry over to lighter devices. For brands and studios, that means a second audience for the same XR investment.

The four ways to build

Path	Best for	Notes
Jetpack XR SDK	Android app teams adding spatial features	Compose for XR for spatial UI, SceneCore for 3D, ARCore for Jetpack XR for world understanding
Unity	Games, training sims, ports from Quest	Unity 6 support via the Unity OpenXR: Android XR package and Android XR Extensions for Unity
Unreal, Godot or native OpenXR	Teams already on those engines	Android XR implements OpenXR with vendor extensions
WebXR	Marketing experiences and quick demos	Runs in the browser, no store submission

Ordinary Android apps from Google Play can also run on Galaxy XR as floating 2D panels without changes. That is a useful baseline, but it is not an XR experience.

Porting a Meta Quest project with Unity

Because both platforms support OpenXR, a Unity project built on the XR Interaction Toolkit and OpenXR ports cleanly. Projects built heavily on Meta's own SDK features need more work. Google's launch materials quote partners bringing existing titles over in about a week, which is realistic for well-structured projects and optimistic for older ones. The checklist:

Unity version and packages. Use a current Unity 6 release with the Unity OpenXR: Android XR package. Google recommends URP and the Vulkan graphics API.
Replace platform-specific code. Swap Meta-only features such as their avatars, platform services and passthrough APIs for OpenXR or Android XR equivalents, behind an abstraction so one codebase serves both stores.
Input. Galaxy XR is built around hand and eye tracking, with controllers optional. Every interaction must work without a controller.
Performance. Profile on the device. Display resolution and refresh targets differ from Quest, so frame budgets and render scale need retuning.
Store and policy. Publish through Google Play with XR-specific listing assets, comfort information and age rating.

Testing without a headset

Android Studio includes an Android XR Emulator for checking layouts, spatial UI and basic flows. It is good for daily development but no substitute for a device: comfort, frame pacing, hand-tracking reliability and text legibility must be tested on real hardware with real people.

What to build first

Ports of existing Quest content , the fastest way to reach a new audience.
Spatial productivity and training , where hand tracking and Android integration shine. Our guide to VR training ROI covers the business case.
Mixed reality experiences that blend virtual objects into the room, the same design patterns covered in our Quest 3 mixed reality guide.
Branded showcases for launches, events and retail.

Costs

A focused single-scene VR experience starts at $999 and a full VR application at $2,999 on our current VR and AR packages, with larger games and training platforms quoted individually. A port of an existing, well-structured Unity Quest project is usually much cheaper than a new build. Typical market ranges for bigger immersive projects are in our VR development cost guide.

Sources: Android Developers Blog: apps on Galaxy XR · Android: develop with Unity for Android XR · Android XR developer site. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Cross-Platform Game Development in 2026: A Practical Guide

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Build the game once in an engine that targets every platform you want, usually Unity for mobile plus PC, and design input, UI and saving for all of them from day one. Each extra platform then adds tuning, testing and store work rather than a second game. What gets expensive is retrofitting: a mobile game designed only for touch and portrait, or a PC game with UI that cannot shrink to a phone, needs real redesign later.

Why cross-platform is the default now

Industry analysis in 2026 keeps pointing the same way: players expect their progress and purchases to move with them between phone, PC and console, and platform-exclusive launches are becoming rare. Releasing on more platforms also spreads risk. A game that underperforms on mobile may find its audience on Steam, and a free web version can feed both.

Step 1: pick an engine that goes everywhere

Unity builds for iOS, Android, Windows, macOS, Linux, the web, consoles and XR from one project, which is why it remains the most common choice for mobile-plus-PC games. Unreal is strong for high-end PC and console and workable on mobile with more optimisation effort. Our comparisons of Unity vs Unreal and Unity vs Godot cover the trade-offs. Console releases additionally require approval from each platform holder.

Step 2: design input for every device

Abstract actions, not buttons. Code "jump" and "aim", then map them to touch, mouse and keyboard and controller. Unity's Input System is built for this.
Design touch controls deliberately. Virtual sticks, gestures and aim assist are game design, not a port job.
Support controllers everywhere. Many mobile and web players use them, and Steam players expect it.

Step 3: UI that scales

The same menu must work on a 6-inch phone held at arm's length and a 27-inch monitor. Use anchored, scalable layouts, minimum touch-target sizes, safe areas for notches and foldables, and a separate layout pass for very different screen shapes. Our guide to designing for foldable screens shows how odd aspect ratios break assumptions.

Step 4: cross-progression and accounts

Carrying progress between platforms needs a player account and a backend that stores saves, inventory and purchases, with sign-in options that work on every store. Decide early which data is shared, how conflicts are resolved when two devices save at once, and how purchases appear on every platform.

Step 5: know the store payment rules

Apple and Google generally require their own in-app purchase systems for digital items bought inside mobile games, while Steam and your website have their own rules. Court rulings and new laws, such as the 2025 US ruling in Epic v. Apple that opened the door to linking out to web checkouts (a case still before the courts in 2026), keep changing what is allowed, and the rules differ by country. Design your store so payment providers can vary by platform, and check current policies before launch.

Step 6: test on a real device matrix

Platform	Minimum test coverage
Android	A low-end, a mid-range and a flagship phone, plus a tablet
iOS	The oldest supported iPhone, a current iPhone and an iPad
PC / Steam	Minimum-spec hardware, integrated graphics, Steam Deck if you target it
Web	Chrome, Safari and Firefox on desktop, plus mobile browsers

Step 7: stage the releases

Launching everywhere at once multiplies risk. Many studios soft-launch on one platform, fix what players find, then roll out. A free web version or a Steam demo during Steam Next Fest can build an audience before the main launch.

What each extra platform costs

If the game is designed for several platforms from the start, each additional platform mostly adds input and UI work, performance tuning, platform services (achievements, cloud saves, store integration), certification and QA. That is a fraction of the original build, not a second one. Porting a game that was never designed for it costs more; our guide to porting a mobile game to PC and Steam breaks down that work. For a quick estimate of a multi-platform build, use the cost calculator.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Web Games in 2026: Is Browser Game Development Worth It?

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Yes, for the right game. Browser games load in seconds with no install, which makes them perfect for casual, puzzle, idle, io-style and short-session games, and a powerful way to get a game in front of players before spending on app store marketing. Poki, one of the largest web game platforms, reports more than 100 million monthly players. The catch is money per player: portal ad revenue is modest, so web works best as part of a plan, either as a low-cost launch market or as a funnel into mobile and Steam.

What the 2026 data says

Poki's State of Web Gaming study, published in June 2026, surveyed 400 developers and 2,000 regular web players in the US and UK. A few findings stand out:

62% of players have downloaded or bought a game after first discovering it on the web.
53% of developers plan to port a mobile game to the browser within 12 months.
37% of web gamers play several times a day, typically in 11–20 minute sessions.
36% of developers say there is not enough revenue in web gaming yet, while 47% see it as a new revenue driver.

Read that as: players are there and engaged, discovery is cheap, and the business model needs thought.

Where web games are played

Portals such as Poki and CrazyGames bring traffic and handle ads. Terms differ: some prefer exclusivity, while CrazyGames does not require it.
Your own website , where you keep all revenue but must bring your own players. Good for branded games and marketing.
Platform channels such as video platforms, messaging apps and chat communities that host instant games. Each has its own SDK, review process and orientation or size rules.

How web games make money

Ad revenue share. Rewarded and interstitial ads served by the portal, split with the developer.
In-game purchases. Increasingly supported on portals and your own site.
Funnel to mobile and PC. Use the free web version to build an audience, then sell the full game on Steam or convert players to a mobile app.
Branded games. A company pays for the game as marketing, so it does not need to earn from ads at all. Our guide to gamification for brands covers this model.

Which technology to choose

Option	Strengths	Watch out for
Unity Web	One codebase for web, mobile and PC; full 3D	Larger downloads; needs careful optimisation for phones
Phaser	Lightweight, fast-loading 2D	Web only; a separate build for app stores
PlayCanvas	Browser-first 3D with small builds	Smaller talent pool
Godot	Free and open source, light 2D	Check web export limits for your scripting language

Unity keeps improving its web platform; Unity 6.5 made WebAssembly 2023 the default target. If you also want mobile and Steam versions, Unity is usually the efficient choice. For a tiny, instant-loading casual game for portals only, a lightweight HTML5 engine wins. Our guide to cross-platform game development explains how one game reaches every screen.

The rules that make or break a web game

Load fast. Players leave in seconds. Keep the first download small and stream the rest.
Play on phones. A large share of web play happens on mobile browsers. Touch controls and portrait or landscape support matter.
Hook in the first minute. No long tutorials or menus before the fun starts.
Save progress. Players return several times a day; losing progress loses them.
Respect the platform. Use each portal's SDK for ads and data, and follow its quality and content rules.

What a web game costs

A focused casual or hyper-casual web game sits in the same range as a simple mobile game: our current Spark package starts from $999, and the typical market range for hyper-casual and simple 2D games is $5,000–$30,000. A web port of an existing Unity mobile game is usually far cheaper than a new build, because most of the work is performance, input and portal integration. See the hyper-casual development service and the cost guide for more detail.

Sources: Poki: 2026 State of Web Gaming · CG Channel on Unity 6.5. Checked October 12, 2026.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

Gamification for Brands: Branded Games, Formats and Costs

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

Gamification works for brands when the game itself carries the message: you play the product, not just look at a logo. The formats that perform best are short, mobile-first and instantly playable from a link or QR code: instant-win games, branded mini-games, quizzes, web AR experiences and loyalty mechanics. A focused branded web game or WebAR experience can be built from about $1,000; larger campaigns with prizes, data capture and multiple markets are quoted per project.

Formats that work

Format	Best for	Typical build
Instant-win / spin-to-win	Retail promotions, launches, email capture	Web game with prize logic and admin panel
Branded mini-game	Product launches, awareness, social sharing	A short web or mobile game built around the product
Quiz or personality test	Product recommendation, lead generation	Web experience linked to product catalogue
WebAR experience	Packaging, posters, try-before-you-buy	Browser AR from a QR code, no app needed
Loyalty gamification	Retention in apps and programmes	Points, streaks, badges and challenges in an existing app
Event and in-store games	Trade shows, pop-ups, flagship stores	Touchscreen, motion or VR game with a leaderboard
Platform brand worlds	Reaching young audiences where they play	Experiences inside platforms such as Roblox or Fortnite

What separates a good branded game from a forgettable one

The product is the mechanic. A sports drink game about timing and energy, a furniture game about fitting pieces into a room. If you can swap the logo and nothing changes, the game is not doing marketing work.
Playable in seconds. No install, no account before play. A link or QR code straight into the game.
Short and replayable. 30 seconds to three minutes per round, with a reason to try again: a better score, a leaderboard, a daily prize.
A clear next step. A coupon, a product page, a store locator or a sign-up, offered at the moment of success.
Built for sharing. Scores and results designed to be posted.

What to measure

Plays and completion rate: how many people start and finish a round.
Time with the brand: total minutes played, compared with the seconds a typical ad gets.
Opt-ins and leads: email or loyalty sign-ups, and cost per lead against your paid social.
Redemption: how many prizes or coupons are used in store or online.
Return visits and shares.

Agree these numbers before building, and make sure analytics are in from day one, not added after launch.

Legal basics for prize games

This is general information, not legal advice; run any prize promotion past a lawyer in each market. In the US, a promotion that combines a prize, chance and a required purchase is generally an illegal lottery, which is why sweepstakes offer a free way to enter ("no purchase necessary"). Contests decided by skill follow different rules. New York and Florida require registration and bonding for chance-based promotions with total prizes above $5,000. Every promotion needs official rules. If you collect personal data, privacy laws such as California's CCPA or the EU's GDPR apply, and if the game could attract children under 13, COPPA does too.

What it costs

Campaign	Typical starting point
WebAR experience or focused branded web game	From $999 (our Spark package)
Full branded mobile or web game with custom art, leaderboard and analytics	From $2,999 (our Launch package)
Multi-market prize campaign with admin tools, data capture and localisation	Quoted per project
Event game with custom hardware or VR	Quoted per project

Prices are from our current launch packages and VR and AR packages. For product visualisation specifically, our AR furniture and retail service covers WebAR on product pages.

Getting started

Start with the business goal, not the game idea: more sign-ups, more store visits, a product understood. Then pick the simplest format that moves that number and test it in one market before rolling it out. Send us the brief and we will suggest two or three formats with costs.

Related: AR development · AR for retail · Packages

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.

How to Write a Game Design Document (2026 Template)

A Plus Games Studio — Mon, 12 Oct 2026 00:00:00 +0000

The short answer

A game design document (GDD) explains what the game is, how it plays and what has to be built, clearly enough that a team can build it and a studio can give you a fixed price. In 2026 the best GDDs are short and living: a one-page summary on top, then focused sections on the core loop, mechanics, progression, content, art direction, technology and, most importantly, what the first version will and will not include.

Start with a one-page summary

If someone reads only one page, it should tell them:

The pitch in one or two sentences.
Genre and platforms: for example, a casual puzzle game for iOS and Android, later Steam.
Audience: who plays it, how often, for how long.
The hook: the one thing that makes it different.
Comparable games: two or three titles players would recognise, and how yours differs.
Business model: premium, ads, in-app purchases or a mix. Our ads vs in-app purchases guide helps here.

The sections that matter

Core loop

What the player does every 30 seconds, every session and every week. Draw it as a cycle: play a level, earn coins, upgrade, unlock harder levels. If you cannot draw the loop, the design is not ready.

Mechanics and controls

Each mechanic with its rules, and how it is controlled on every platform: touch, mouse and keyboard, controller. Include edge cases: what happens when the player does something unexpected.

Progression and economy

How difficulty rises, what players unlock and when, which currencies exist, how they are earned and spent. Put the numbers in a spreadsheet and link it; prose hides balance problems.

Content list

Every level, character, item, enemy, map and mode in the first release, as a countable list. This is what turns a description into an estimate.

Art and audio direction

Mood boards, reference images and a few words on style, camera and colour. Note the technical constraints: the art style must run on your weakest target device.

UI and screen flow

A diagram of every screen from launch to gameplay to store to settings, with rough wireframes for the important ones.

Technical plan

Engine, platforms, online features (accounts, multiplayer, leaderboards), backend, analytics, ads and purchase providers, and any third-party services. For a Unity project, note the render pipeline; new projects should start on URP, as our Unity 6 upgrade guide explains.

MVP scope and cut list

The most valuable page in the document. Write what the first playable release includes, and just as clearly, what it does not. "Multiplayer: not in MVP" saves more money than any other sentence you will write.

Milestones and risks

The order of work, from prototype to launch, and the three or four things most likely to go wrong, with a plan for each.

A copyable outline

One-page summary: pitch, genre, platforms, audience, hook, comparable games, business model
Core loop diagram (moment, session, long term)
Mechanics and rules, with controls per platform
Progression, difficulty and economy (link the balance spreadsheet)
Content list for the first release
Art direction: references, style, camera, technical limits
Audio direction
UI flow diagram and key wireframes
Technical plan: engine, platforms, backend, analytics, monetisation providers
MVP scope and explicit cut list
Milestones
Risks and mitigations
Open questions and decisions log

Mistakes that make GDDs useless

Writing a novel. Long lore and no rules. Keep story to what affects gameplay.
Wishes instead of decisions."Maybe multiplayer later" is not a decision. Decide, or put it in open questions.
No numbers."Upgrades get more expensive" cannot be built or tested. Give the curve.
Freezing it. A GDD that is never updated after the prototype becomes fiction. Keep a decisions log.
Skipping the cut list. Every feature looks essential until you price it.

Tools

Any shared document tool works. Most teams use a document for the text, a spreadsheet for the numbers and a whiteboard tool for loops and screen flow. AI assistants are useful for turning notes into a first draft and spotting gaps, but the design decisions have to be yours; our look at AI game generators explains where AI helps.

From document to quote

A GDD with a content list and an MVP cut list is exactly what a studio needs to give you an accurate fixed price instead of a guess. Send yours to us and you'll get a detailed scope, milestone plan and fixed price within 48 hours. If you only have an idea, we can help turn it into a document first; read our guide to choosing a game development studio before you send it anywhere.

Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.