A 3D game character is made through concept art, a detailed sculpt, a lighter game-ready model, UVs and textures, a rig, and a set of animations, then set up in the engine. Cost is driven mainly by style (stylised is usually faster than realistic), importance (hero characters cost more than background ones), platform budgets, customisation, and especially the number and complexity of animations. Modular parts, shared skeletons and animation retargeting are the biggest savings on multi-character projects.

The process, step by step

What drives the cost

Animation is often underestimated. A character with fifty animations can cost more in animation than in modelling. List every animation the design needs before asking for quotes, including transitions such as starting and stopping a run, which players notice when they are missing.

Style choices and their trade-offs

Stylised characters, with exaggerated proportions and simpler materials, are usually faster to produce, age well and run efficiently on phones and headsets. Realistic characters need high-detail sculpting, complex skin, hair and cloth materials, and more careful lighting to avoid looking uncanny. Choose the style for the audience and platform first; it decides most of the budget.

Platform budgets

Mobile and standalone VR have far less memory and GPU power than gaming PCs. Characters for those platforms need lighter meshes, smaller textures and fewer bones, and often several levels of detail. Optimisation is skilled work, so budgets for mobile and VR characters are not automatically smaller. Our article on game assets covers performance budgets.

Ways to save

• Modular characters: heads, bodies, outfits and accessories that combine into many variations.
• Shared skeletons: one rig standard across characters so animations can be reused.
• Animation retargeting: Unity's humanoid retargeting and Unreal's IK Retargeter let one animation drive many characters.
• Marketplace bases: purchased base meshes or animation packs, checked for licence terms and style fit.
• Approve early: lock the design at concept and blockout stages, when changes are cheap.

Motion capture or keyframe animation?

Motion capture records real actors and suits realistic movement, sports and large volumes of natural animation. Keyframe animation, created by hand, suits stylised characters, exaggerated action and creatures that cannot be performed by people. Many projects mix both: captured locomotion cleaned up by animators, plus hand-keyed attacks and reactions. Library animations, licensed from marketplaces, can cover generic movement cheaply if the skeleton is compatible.

A character budget checklist

• How many characters, and which are heroes, enemies or background?
• How close does the camera get to each?
• Which platforms, and what are the polygon, texture and bone limits?
• How many outfits, colours and accessories?
• The full animation list, including transitions.
• Does the face need expressions or lip sync?
• Which animations can be shared through retargeting?

Timeline

A single stylised character with a small animation set can be ready in weeks; a cast of realistic hero characters with facial animation takes months. Plan character production in parallel with gameplay, starting with one character that goes all the way through the pipeline to validate style, budgets and rig before producing the rest.

Briefing a character

• Role in the game and how close the camera gets.
• References for style, shape language and colours.
• Technical budget: polygons, textures, bones, platforms.
• Required animations, listed one by one.
• Variants, outfits and customisation.
• File formats and engine set-up expected.

Our game art outsourcing guide covers briefs and feedback in depth.

Getting a quote

Because style, count and animation scope vary so much, we quote characters per project after reviewing the brief. Send us your references and animation list via the quote form, or see 3D game development.

Sources: Unity: animation system overview · Unity: retargeting humanoid animations · Unreal Engine: animation retargeting · Blender manual: armatures · Khronos: glTF. Checked October 20, 2026.

Related: 3D game development · 2D game development · Get a quote

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

Ad mediation uses one SDK to let many ad networks compete for each ad your game shows. Modern setups use in-app bidding, where networks bid in a real-time auction, often alongside a waterfall that calls networks in priority order. The main platforms are AppLovin MAX, Unity LevelPlay and Google AdMob mediation. More competition usually means more revenue per impression, but placement and frequency matter as much as the platform, because ads that annoy players cost more in retention than they earn.

How mediation works

Without mediation, a game shows ads from one network and accepts whatever price it pays. With mediation, the game asks the mediation SDK for an ad; the SDK gathers bids or calls networks through adapters, picks the best offer and shows it. You manage all networks from one dashboard.

Bidding versus waterfall

Most games today use bidding for the main networks and keep a small waterfall for the rest. Support varies by adapter and format; for example, Google's AdMob documentation notes that AppLovin bidding through AdMob does not support banner ads.

The main mediation platforms

Networks also appear inside each other's mediation: Unity documents how Unity Ads bids inside LevelPlay, AppLovin MAX and AdMob or Ad Manager. Choose a platform on SDK quality, reporting, supported networks for your markets, and how well it works with your engine, then test.

Ad formats

Placement and frequency

• Show interstitials only at natural breaks, never mid-action.
• Cap frequency per session and per minute.
• Give players a choice: rewarded ads they opt into perform better and feel fairer.
• Skip ads for new players during onboarding.
• Offer a paid "remove ads" option; some players happily pay to avoid them.

Consent and privacy

In the EEA and UK, personalised ads require consent collected through a consent management platform; Google's User Messaging Platform supports the IAB Transparency and Consent Framework. On iOS, cross-app tracking requires the App Tracking Transparency prompt, and ad networks need their SKAdNetwork identifiers in your app. Children's games have stricter rules; see our kids game rules guide.

Testing

• Use test ad units and register test devices; clicking real ads in testing can get an account suspended.
• Use each platform's mediation debugger or test suite to check every adapter loads.
• Test on slow connections and low-end devices.

Measuring success

Watch ad revenue per daily active user, impressions per user, fill rate and eCPM by network, and above all the effect on retention. A change that lifts ad revenue by 10% but lowers day-seven retention can lose money over a player's lifetime. Run A/B tests on frequency and placements. Our mobile KPIs guide explains the metrics.

A setup checklist

1. Pick the mediation platform and list the networks you will add for your top markets.
2. Integrate the mediation SDK and the adapters, following each adapter's version requirements.
3. Set up consent for the EEA and UK and the ATT prompt for iOS before the first ad request.
4. Add SKAdNetwork identifiers and app-ads.txt on your developer website so buyers can verify your inventory.
5. Create ad units per placement so each one can be measured and tuned separately.
6. Test every network with test ads, then launch to a small share of players first.

The app-ads.txt file, published on the developer website listed in your store page, tells advertisers which networks are authorised to sell your inventory; missing or wrong entries can reduce demand.

Ads, purchases or both?

Most casual games combine ads with in-app purchases. Our article on ads vs IAP vs hybrid helps decide the balance, and Unreal monetisation covers Unreal-specific options.

Getting help

We set up mediation, consent and analytics in Unity and Unreal mobile games and tune placements after launch. See hyper-casual games or request a quote.

Sources: Unity: in-app bidding with Unity Ads · AppLovin: MAX integration · Google AdMob: mediation with AppLovin · Google: User Messaging Platform · Apple: App Tracking Transparency. Checked October 20, 2026.

Related: Hyper-casual games · Mobile game development · Get a quote

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

AI voice is useful in games for placeholders, large volumes of incidental lines, real-time dialogue and accessibility, but principal characters still benefit from human performances. In 2026, the rules matter as much as the technology: the 2025 SAG-AFTRA video game agreement requires informed consent for AI use of performers' voices and sets minimum pay for replicas, Steam requires developers to disclose AI-generated content, and every tool has its own licence terms. Use AI voice with consent, disclosure and legal review.

Where AI voice fits

For AI-driven characters, see our article on AI NPCs.

The 2025 SAG-AFTRA agreement

In 2025, SAG-AFTRA members ratified a new Interactive Media Agreement with 95.04% voting in favour, ending the video game performers' strike. For AI, reports of the deal highlight that it:

• Requires informed consent for each AI use of a performer's voice, likeness and movement, with a reasonably specific description of how a digital replica will be used.
• Lets performers suspend consent for generating new replica material during a strike.
• Sets pay of at least 7.5 times minimum scale when a replicated performer is used for real-time generation, such as an AI chatbot character.

If you work with union performers or with companies that are signatories, these terms apply. Even outside union work, they show what professional practice now expects.

Platform disclosure

Steam asks developers to disclose AI use in the content survey, separating pre-generated content made during development from live-generated content created while the game runs. Live-generated content needs described guardrails to prevent illegal content, much of the disclosure appears on the store page, and players can report problems. Games that do not disclose accurately risk removal. Check each store's current rules before release.

Licensing and rights

• Tool licences: confirm commercial use is allowed, and whether the provider offers any indemnity.
• Training data: prefer tools that are clear about where voice data came from and how voices were licensed.
• Voice cloning: clone a real person's voice only with their written, specific consent and agreed payment.
• Copyright: protection for purely AI-generated material is limited in some countries; the U.S. Copyright Office's guidance explains the current position.

Real-time AI voices need guardrails

When a character speaks lines generated during play, you no longer approve every line before release. That needs content filters on the text before it becomes speech, limits on topics, logging for review, and a way for players to report problems. Steam explicitly asks developers to describe these guardrails for live-generated content. Test with adversarial players who try to make characters say things they should not.

Working with actors and AI together

Many studios now combine both: actors record principal roles, while AI or text-to-speech fills incidental or procedural lines in a clearly different role. Be transparent with performers about how their recordings will be used, keep AI use within what contracts allow, and credit everyone properly. Good relationships with performers are worth more than the savings from cutting corners.

Quality limits to plan for

• Emotional delivery across long scenes can sound flat or inconsistent.
• Pronunciation of invented names and terms needs manual correction.
• Consistency of a character's voice across thousands of lines takes careful tooling.
• Players increasingly notice and comment on synthetic voices, positively or negatively.

A responsible approach

1. Use human actors for principal roles and emotionally important scenes.
2. Use AI voice for placeholders, incidental lines and accessibility where it genuinely helps.
3. Get written, specific consent and agree pay for any use of a real performer's voice.
4. Disclose AI use on stores and in credits where required.
5. Add guardrails and moderation for any live-generated speech.
6. Get legal review of contracts and tool licences before release.

Other jurisdictions

Rules differ by country. Some places give people rights over their voice and likeness under publicity or personality laws, and new AI laws, such as the EU AI Act, include transparency obligations for synthetic content. If your game launches internationally, get advice on the markets that matter most to you.

Budgeting audio

Voice-over is often one of the largest audio and localisation costs, which is why AI voice is tempting. A mixed approach, actors for key roles and carefully licensed AI or text-to-speech for the long tail, can reduce costs without the risks of replacing performers outright. See our guides to game audio and localization.

Working with us

We help teams plan audio pipelines that combine actors, sound design and responsibly used AI tools. See AI game development or request a quote. This article is general information, not legal advice.

Sources: TheWrap: SAG-AFTRA video game deal details · Reuters via AOL: video game actors pass agreement · SAG-AFTRA: interactive media contracts · VGC: Steam AI disclosure · U.S. Copyright Office: copyright and AI. Checked October 20, 2026.

Related: AI game development · Unity game development · Get a quote

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

The most effective anti-cheat for a small multiplayer game is an authoritative server that validates everything players send and never shares information they should not have. Add free or low-cost layers on top: Easy Anti-Cheat or VAC on PC, Google Play Integrity and Apple App Attest on mobile, server-side purchase validation, and player reporting with replays. Spend on heavier tools only for competitive, ranked modes where cheating directly ruins the experience.

Layer 1: never trust the client

If a player's device decides who won, someone will change it. In an authoritative design, clients send inputs, such as "move forward" or "fire", and the server decides the results. This one decision blocks the most common cheats: speed hacks, teleporting, infinite currency and changed damage values.

• Validate movement against maximum speed and collision.
• Enforce cooldowns, ammo and resources on the server.
• Calculate damage and rewards on the server.
• Validate every purchase and reward grant on the server.

Our comparison of Photon, Netcode and Mirror explains which stacks support server authority.

Layer 2: do not leak information

Wallhacks and map hacks work because the client knows things the player should not see. Where practical, only send positions of enemies a player can actually perceive, and never send hidden cards, future loot or other players' private data. This is cheaper to design in early than to retrofit.

Layer 3: sanity checks and rate limits

• Flag impossible stats: accuracy, kill rates or scores far outside normal ranges.
• Rate-limit actions and API calls to slow bots.
• Log match events so suspicious results can be reviewed and replayed.

Layer 4: client-side anti-cheat on PC

Client anti-cheat raises the effort needed to cheat but never replaces server authority. Kernel-level solutions are powerful but raise privacy, compatibility and Steam Deck considerations; weigh them carefully for a small game.

Layer 5: device integrity on mobile

On Android, the Play Integrity API helps your server confirm requests come from your genuine app on a genuine device. On iOS, App Attest does the same for Apple devices. Use them for high-value actions such as ranked results and purchases, and handle failures gracefully, since some legitimate devices fail checks.

Layer 6: purchases

Validate App Store and Google Play receipts on your server before granting premium items. Client-only purchase checks are one of the easiest things to bypass on mobile.

Layer 7: community

• In-game reporting with a reason and the match ID.
• Replays or logs reviewers can check.
• Clear, published rules and a ban policy with appeals.
• Shadow queues that match suspected cheaters with each other, used carefully.

Common cheats and the layer that stops them

Measuring the problem

Before buying tools, measure. Track reports per thousand matches, the share of top leaderboard scores that look impossible, and how quickly cheaters reappear after bans. These numbers tell you whether cheating is a real problem for your players or a fear, and they show whether each new layer actually helps.

What not to waste money on

• Obfuscation as a solution: it slows cheat makers down, but determined ones get through. Treat it as a speed bump.
• Heavy client anti-cheat in casual co-op: if cheating only affects the cheater, the cost and friction may not be worth it.
• Fighting every cheat at once: watch reports and data, then fix what players actually encounter.

Match the protection to the mode

Handling bans fairly

False positives hurt honest players and reviews. Start with temporary restrictions for automated flags, keep permanent bans for confirmed cases reviewed by a person, and offer a simple appeal route. Explain the rules in plain language. Fair, visible enforcement deters cheaters more than secret tools do.

Building it in from the start

We design multiplayer games with server authority and validation from the first prototype, so anti-cheat is cheap rather than a late rewrite. See multiplayer FPS development or our multiplayer cost guide.

Sources: Epic Online Services: Easy Anti-Cheat · Steamworks: anti-cheat · Android: Play Integrity API · Apple: App Attest · Unity: Netcode documentation. Checked October 20, 2026.

Related: Multiplayer FPS development · PC game development · Get a quote

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

Building for Apple Vision Pro is worth it in 2026 when the audience is premium or professional: enterprise training and visualisation, retail and product experiences, high-end entertainment, or a port of an existing Unity XR app. The M5 model launched in October 2025 from $3,499, which keeps the user base small. Developers can build natively with SwiftUI and RealityKit or with Unity and PolySpatial, which requires a paid Unity plan. For mass-market games, Meta Quest and phones still reach far more players.

The hardware in 2026

• The Vision Pro with M5 chip went on sale on 22 October 2025, starting at $3,499, and shipped with visionOS 26. Check Apple's site for current pricing and availability.
• Input: eye tracking and hand gestures as standard, plus support for PlayStation VR2 Sense controllers and game controllers for games that need precision.
• High-resolution passthrough makes mixed reality the default way people use it.

visionOS app types

Native or Unity?

If you already ship on Meta Quest or plan for Android XR, Unity usually makes Vision Pro an extension rather than a separate project.

WebXR on Vision Pro

Since visionOS 2, Safari supports WebXR immersive VR sessions by default, so browser-based VR can reach Vision Pro users without an app. AR sessions (immersive-ar) are not supported, so web-based mixed reality is not an option on Vision Pro today. Our guide to WebXR in 2026 covers browser support across devices.

Where Vision Pro makes sense

• Enterprise training and visualisation: organisations buying a handful of headsets for high-value training or design review.
• Retail and product experiences: showrooms, configurators and premium brand experiences.
• Premium entertainment: immersive films, experiences and games for early adopters.
• Ports: adding Vision Pro support to a successful Quest or mobile AR app.

Where it does not (yet)

Free-to-play or mass-market games that need millions of players. The installed base is small, so revenue potential is limited compared with phones and Meta Quest. For most VR games, Quest remains the first platform; see our VR development cost guide.

Porting an existing XR app

Many Vision Pro projects start as ports. A Unity app already running on Meta Quest or mobile AR can often be brought to visionOS with PolySpatial, but expect work in three areas. Input changes from controllers or touch to eyes and hands, so menus and interactions need redesigning around look-and-pinch. Rendering in the shared space uses RealityKit through PolySpatial, so some custom shaders and effects need rewriting or simplifying. And the app needs to behave well alongside other windows and the user's real room, rather than assuming it owns the whole view.

A short technical assessment of the existing project, listing shaders, plugins and interaction systems, usually shows within days whether a port is straightforward or closer to a rebuild.

Enterprise deployment

For businesses, distribution matters as much as development. Apps can be published on the App Store, distributed privately to an organisation, or managed with device management tools. Plan how headsets will be set up, shared, cleaned and charged, and how content will be updated, because those operational details often decide whether an enterprise pilot becomes a rollout. Our article on enterprise VR training ROI covers building the business case.

Design considerations

• Comfort first: avoid forced movement; use teleport or stationary experiences for most users.
• Design for eyes and hands: large targets, look-and-pinch interactions, clear feedback.
• Respect the user's space: content should sit comfortably in real rooms.
• Sessions are often shorter than on consoles; design for drop-in use.

Testing without many headsets

Apple's visionOS simulator in Xcode covers layout and basic interaction, and Unity projects can be previewed in the editor, but comfort, eye-and-hand input and real rooms can only be judged on a device. Most teams work with one or two headsets and schedule on-device test sessions every week rather than relying on the simulator until the end.

Budget and timeline

A focused Vision Pro experience, such as a product viewer or a single-scene demo, fits our VR and AR packages starting at $999 for a proof of concept and $2,999 for a complete app; multi-scenario training and multiplayer are quoted individually. Porting an existing Unity XR app is usually faster than building from scratch.

Working with us

We build XR apps in Unity for Meta Quest, Android XR and Apple Vision Pro. See VR development or request a quote.

Sources: Apple: Vision Pro · Road to VR: Vision Pro with M5 launch · Apple: visionOS for developers · Unity: PolySpatial · Road to VR: visionOS 2 enables WebXR. Checked October 20, 2026.

Related: VR development · VR & AR packages · AR development

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

Retailers use AR to show products at true scale in the customer's home, let shoppers try on glasses, jewellery, cosmetics, shoes and watches with their phone camera, turn packaging into interactive experiences through QR codes, and add guided or playful experiences in stores. Delivery can be web-based, so no app is needed, through a native app, or through social lenses. The value is measured the same way as any shop feature: A/B tests on conversion, returns and engagement.

The main retail AR formats

Web, app or social?

For product pages, a common pattern is Google's model-viewer: Android shoppers get WebXR or Scene Viewer, and iPhone shoppers get Apple's AR Quick Look with a USDZ model. Try-on usually needs face or body tracking, which works best in a native app or a specialised web SDK. Our article on ARKit vs ARCore vs WebXR explains the trade-offs.

Getting the 3D assets right

• Accurate scale: a fridge must be exactly the size of the fridge.
• Source data: CAD files from manufacturers are ideal; photogrammetry suits organic or textured products.
• Materials: fabrics, metals and glass must look right under real lighting.
• File size: models compressed for fast mobile loading, usually glTF and USDZ.
• Variants: colours and finishes handled efficiently rather than as separate heavy models.

For catalogues of hundreds of products, the asset pipeline costs more than the AR software. See how 3D assets are made.

AR packaging and QR campaigns

Packaging turns every product on a shelf or in a kitchen into a channel: recipes, games, product stories or collectible characters. The experience must load in seconds on any phone and keep working for as long as the product is on sale. Our guide to QR code AR campaigns covers how to plan them.

In-store AR

In physical stores, AR works best when it solves a problem: finding a product, comparing options, seeing a product in action, or making a display memorable. It works worst when it asks shoppers to install an app to see a minor animation. Web-based experiences triggered by signs keep friction low.

Try-on accuracy and trust

Try-on only helps if shoppers trust what they see. Glasses must sit at the right width on the face, cosmetics must match real shades under different lighting, and shoes must appear at the right size. Test with a wide range of faces, skin tones, lighting conditions and phones before launch, and be honest in the interface where the preview is an approximation. A try-on that flatters but misleads increases returns instead of reducing them.

Privacy

Camera-based features process images of shoppers' faces and homes. Keep processing on the device where possible, explain clearly what is and is not stored, and follow the privacy laws of each market. Face data in particular may be treated as sensitive or biometric data in some jurisdictions, so legal review is worthwhile before launching try-on.

Measuring results

• A/B test product pages with and without AR and compare conversion.
• Track return rates for products viewed in AR versus not.
• Measure engagement: share of visitors who start AR and time spent.
• For packaging, track scans per pack, repeat scans and actions taken.

Report results by product category; AR usually helps most where size, fit or appearance cause uncertainty.

Costs

A single AR experience or WebAR demo fits our AR packages from $999, and a complete AR app from $2,999. Catalogue-wide furniture and product programmes are scoped separately; our AR furniture page shows typical pilot ranges, and our AR app cost guide explains the drivers.

Where to start

1. Pick the product category where size, fit or appearance causes the most hesitation or returns.
2. Build AR for your best-selling products in that category.
3. Launch on product pages with web AR and an iPhone fallback.
4. Measure for a few weeks, then expand to more products or try-on.

Try it

See our live browser AR demos and read how AR furniture apps work for the furniture-specific details.

Sources: Apple: AR Quick Look · Google: model-viewer · Google ARCore: Augmented Faces · Apple ARKit: face tracking · Khronos: glTF. Checked October 20, 2026.

Related: AR furniture apps · AR development · VR & AR packages

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

Building a game in Arabic properly means mirroring the interface for right-to-left reading, using a text system that shapes Arabic letters correctly, choosing fonts with full Arabic coverage, handling mixed text with numbers and English, and reviewing content for cultural fit. In Unity 6, UI Toolkit's opt-in Advanced Text Generator supports right-to-left text, while TextMeshPro usually needs a plugin; Unreal Engine supports complex shaping and bidirectional text. Saudi Arabia also requires games to be classified by its media regulator.

Right-to-left UI: what to mirror

Mirroring is easiest when layouts use relative anchoring rather than fixed positions. Retrofitting a finished UI for right-to-left is one of the most expensive localization jobs.

Letter shaping and bidirectional text

Arabic letters take different forms depending on their position in a word, and some pairs join into ligatures. Text rendered without a shaping engine shows disconnected letters, which reads as broken to every Arabic speaker. Sentences that mix Arabic with numbers or English words also need the Unicode bidirectional algorithm, so that each run of text displays in the right order.

Engine support

Check the current documentation for your engine version before choosing, and test real Arabic sentences early, not just single words.

Fonts and typography

• Choose fonts designed for Arabic, such as Noto Sans Arabic, rather than relying on fallbacks.
• Arabic often needs more line height for diacritics and descenders.
• Match the Arabic font's weight and personality to the Latin font so the brand stays consistent.
• Test small sizes on low-resolution phones; thin strokes disappear quickly.

Numbers, dates and currency

Markets differ on digits: some prefer Western digits (0–9), others Eastern Arabic digits. Pick per market and be consistent. Format dates, currency and large numbers with locale-aware functions rather than by hand. Remember that the Islamic (Hijri) calendar matters for events and seasonal content, even when the game uses the Gregorian calendar elsewhere.

Language choice

Modern Standard Arabic is understood across the Arab world and suits menus, tutorials and most game text. Gulf dialect can make marketing, characters and social content feel local, especially for Saudi and UAE audiences. Use native writers with game experience, and give them context for every string.

Cultural review

• Religious symbols and references used respectfully or avoided.
• Gambling-like mechanics such as loot boxes reviewed against local rules and expectations.
• Alcohol, clothing and relationships checked against target market norms.
• Maps, flags and borders reviewed carefully.
• Holidays and events, such as Ramadan and Eid, used for timely content.

Ratings and release in Saudi Arabia

Saudi Arabia requires video games to be classified before release, through the General Authority for Media Regulation (formerly GCAM), which runs the country's age-rating system. Applications can be made by the developer, publisher or a local agent in Arabic or English, and digital distribution does not automatically remove the need for classification. Our Saudi gaming market guide covers the wider market.

Player names, chat and input

Arabic support does not stop at displayed text. Players type names and chat messages in Arabic, so input fields must accept and display right-to-left text correctly, cursors must move the right way, and filters for offensive language must cover Arabic, including common transliterations in Latin letters. Leaderboards and friend lists often mix Arabic and Latin names side by side, which is a good test of the bidirectional text handling.

Bilingual games

Many Gulf players switch between Arabic and English. A language switch in settings that flips the whole interface instantly, without restarting, is appreciated. Design layouts that work in both directions from the start, and keep brand names and some gaming terms in English where that is what players actually use.

Testing Arabic

1. Pseudo-localise early with right-to-left test strings to find layout problems.
2. Test with real Arabic text from native writers, including long words and diacritics.
3. Check mixed text with numbers, player names and English brand names.
4. Run linguistic QA with native speakers in the running build.
5. Test on popular phones in the region, including lower-end Android devices.

Working with us

We build Arabic-first and bilingual games with right-to-left UI from the first sprint. See our Arabic page, Saudi Arabia page and localization guide.

Sources: Unity: Advanced Text Generator · RTLTMPro plugin for TextMeshPro · Unreal Engine: localization overview · Unicode: bidirectional algorithm (UAX #9) · Google Fonts: Noto Sans Arabic · Saudipedia: clearance of electronic games. Checked October 20, 2026.

Related: Arabic game development page · Game development for Saudi Arabia · Game development for the UAE

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

Finland's games industry earned about EUR 2.85 billion in 2024, according to Neogames, with around 270 active studios and roughly 4,300 employees. Most turnover comes from the Helsinki capital region, home to companies such as Supercell, Rovio and Remedy, while Oulu, home to Fingersoft and Oulu Game Lab, and Tampere have active studio scenes of their own. Finnish studios commonly work with external partners for co-development, porting, art and LiveOps when they need extra capacity.

The industry in numbers

Neogames, the Finnish game industry hub, publishes a regular report on the sector. Its report covering 2024 gives these figures:

The report also notes lower investment than in the 2021–2022 boom and a shift by some companies to fiscal years running April to March, so year-on-year comparisons need care. The picture is of a mature industry with a few very large companies and a long tail of smaller studios, many of them founded in the last few years.

Helsinki and the capital region

The capital region, which includes Helsinki and Espoo, hosts the companies that made Finland famous in games: Supercell in Helsinki, Rovio in Espoo, and Remedy Entertainment in Espoo, alongside many smaller studios. It is where most of the industry's revenue, investors and senior talent are concentrated.

Oulu

Oulu, in northern Finland, has a smaller but distinctive scene. It is home to Fingersoft, the studio behind the Hill Climb Racing series, and to Oulu Game Lab, a game development programme at Oulu University of Applied Sciences that trains developers through real projects. The city's technology history, with a strong base in mobile and telecoms engineering, feeds both studios and wider tech companies.

Studios in Oulu, like elsewhere in Finland, often look for external partners when a project needs more hands than a small local team can provide, for example for porting, extra content or art.

Tampere

Tampere combines university game research with a growing community of studios and events. Like Oulu, it is a source of new developers and new companies, many of which work with partners on parts of their production.

How Finnish studios use partners

Our article on co-development explains how two teams work on one codebase, and game porting covers moving games to new platforms.

What Finnish studios look for in a partner

• Engineering quality: code the core team can review and maintain after the partner leaves.
• Clear ownership: contracts that assign all code, art and IP to the studio on payment.
• Transparency: access to the repository, task board and builds at all times.
• Fit with live operations: partners who can work inside an existing release cadence without breaking it.
• Honest estimates: milestone plans with clear assumptions rather than optimistic day rates.

Our guide to choosing a game development studio lists the questions to ask any partner, and why outsourcing partnerships fail covers the warning signs.

Working across time zones

Finland is on Eastern European Time, UTC+2 in winter and UTC+3 in summer. A studio on US Pacific time is ten hours behind, so collaboration works best with a daily overlap window, written handovers at the end of each day, and weekly playable builds. Many Finnish teams are used to this rhythm from working with partners in other regions.

Publishers and partners: knowing the difference

Developers searching for a publisher in Finland should know the difference between roles. A publisher funds, markets and distributes games, usually for a revenue share. A development or co-development partner builds games or parts of games for a fee, and the developer or publisher keeps the IP. A Plus Games Studio is the second kind: we build, port and support games for studios and publishers. Our guides on funding an indie game and pitching to publishers cover the publishing side.

Working with A Plus Games Studio

We work with studios in Finland and across Europe on co-development, porting, art and LiveOps, with milestone pricing and full IP transfer. See our Finland page or co-development services.

Sources: Neogames Finland · Game Dev Reports: Neogames, Finnish game industry in 2025 · Supercell: about · Fingersoft · Oulu University of Applied Sciences. Checked October 20, 2026.

Related: Game development for Finland · Co-development · Outsource game development

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

The biggest trends in mobile gaming for 2026 and 2027 are more open payments (US court rulings now let games link to outside payments on both the App Store and Google Play), hybrid-casual design, games that run on phone and PC with shared progress, AI tools in production, and new screen formats such as foldables and 120Hz displays. Together they reward studios that build strong retention and their own direct relationship with players.

1. Payments are opening up

For years, mobile games had to use the store's billing for digital purchases. That changed in the US:

• Apple: after a federal court order on 30 April 2025 in the Epic v. Apple case, Apple updated its App Store guidelines for the US storefront so apps can include buttons and links to purchase outside the app.
• Google: under the injunction in Epic v. Google, Google Play in the US had to allow alternative billing and external payment links from 29 October 2025.
• Europe: the EU's Digital Markets Act allows alternative app marketplaces and payment options under its own rules.

The practical result is the rise of web shops: publishers sell currency and bundles on their own websites, often with better value for players, and keep more of the revenue. Rules differ by country and change with ongoing litigation, so check the current store terms before designing your payment flow.

2. Hybrid-casual keeps growing

Pure hyper-casual games, cheap to make and dependent on ad revenue, have given way to hybrid-casual: the instant onboarding of a casual game plus progression, collections and events that keep players for weeks. That shifts budgets from volume to quality and LiveOps. Our articles on hyper-casual vs hybrid-casual and hybrid-casual costs go deeper.

3. One game, many screens

Players increasingly expect to start on a phone and continue on a PC or tablet. More mobile games launch on PC, through native builds, Steam or platform programmes, with cross-progression and sometimes cross-play. Planning input, UI and accounts for several devices from the start is far cheaper than porting later; see our cross-platform guide.

4. AI changes production, not the need for teams

AI tools speed up concept art, placeholder assets, code assistance, localisation drafts and testing. They shorten prototyping and some content work, but shipping a polished, stable game still takes experienced people. We cover where the savings are real in AI in the art pipeline and what AI game generators can build.

5. New screens and faster displays

Foldable phones bring near-square layouts that break UI designed for tall screens, and 120Hz displays raise player expectations for smoothness while costing battery. Games need flexible layouts and frame-rate options. See games on foldables and frame rate and player experience.

6. Privacy makes retention the real growth engine

Since Apple's App Tracking Transparency, apps need permission to track users across other companies' apps, which makes ad targeting and measurement less precise. When cheap, precise acquisition gets harder, keeping players matters more: onboarding, events, and regular content updates. Our mobile KPIs guide explains what to track.

7. LiveOps as standard

Successful mobile games behave like services: weekly events, seasonal content, offers and community management. Budgets now plan for months of post-launch work. See launching a live service game and LiveOps outsourcing.

8. Game stores beyond Apple and Google

Court rulings and regulation are also opening room for alternative stores. In the EU, the Digital Markets Act requires designated gatekeepers to allow alternative app marketplaces, and Google has described a programme for third-party US Android app stores on Play following the Epic ruling. For most studios the main stores will still drive the majority of installs, but direct distribution, web shops and alternative stores give publishers more options and more negotiating power than a few years ago.

What this means if you are building a mobile game

Trends to watch, not bet on yet

• Cloud streaming on phones: works for some players and genres, but latency and data costs keep native games dominant.
• AI-generated content at runtime: promising for dialogue and variety, but costs, moderation and consistency are still being worked out; see AI NPCs.
• Mobile AR games: technically mature, but few hits beyond location-based play; brand and retail AR is growing faster.

Build with a team that tracks these changes

We build mobile games in Unity for iOS and Android, plan payment flows and cross-platform support, and run LiveOps after launch. See mobile game development or request a quote.

Sources: Apple: App Store Review Guidelines · TechCrunch: Apple changes US App Store rules (May 2025) · Google Play: US programs after the Epic v. Google ruling · European Commission: Digital Markets Act · Apple: user privacy and data use. Checked October 20, 2026.

Related: Mobile game development · Hyper-casual games · Get a quote

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

Game art outsourcing works best when the studio keeps art direction in-house, chooses a style that fits its budget and platform, and gives artists a brief with references, a style guide and exact technical specifications. Start with a paid test task, work in milestones from concept to final, give consolidated feedback from one person, and check every asset in the engine. Contracts should assign all rights and disclose any AI tool use.

What studios outsource

Volume work, such as props, icons and variations, is the easiest to outsource. Core style-defining work, such as the main character or the first environment, benefits from closer collaboration with the art lead.

Choosing a style

Style is a budget decision as much as an artistic one. Mobile and standalone VR also set tight technical limits; see game assets explained.

Writing a brief artists can use

• References: images with notes on what to take from each, such as colour, shape language or detail level.
• Style guide: palette, proportions, line or edge treatment, lighting, examples of approved assets.
• Technical specs: polygon budget, texture size and maps, scale, pivot points, naming conventions, file formats such as FBX or glTF.
• Engine set-up: which engine, render pipeline and shaders the assets must work with.
• Deliverables: list of assets, variants, and the files expected for each.
• Deadlines and milestones: when each stage is due and who approves it.

The process

1. Paid test task: one representative asset to check style and technical quality.
2. Concept: sketches or paint-overs for approval before modelling.
3. Blockout: rough 3D shapes checked in the engine for scale and silhouette.
4. Final: detail, textures and materials.
5. Integration: assets imported, set up and reviewed in the game.

Approving at each stage avoids the costliest mistake: discovering at the final stage that the shape or scale was wrong from the start.

Feedback that works

• One person consolidates feedback; artists should not receive conflicting notes from several people.
• Be specific: "make the helmet 20% larger and rounder" beats "make it more heroic".
• Use paint-overs and annotated screenshots.
• Agree the number of revision rounds per stage in advance.

Pipelines and quality checks

Assets should go straight into version control and be checked in the engine, not just in rendered images. Check scale, pivots, naming, texture sizes and performance on the target device. A simple checklist per asset type catches most problems before they spread across hundreds of files.

Rights, licences and AI

• The contract should assign all rights in the delivered art to you on payment.
• Artists should list any third-party fonts, textures or brushes and their licences.
• Agree whether AI tools may be used, require disclosure, and make sure the output can be used commercially; copyright treatment of AI-generated material is still evolving, as the U.S. Copyright Office's guidance shows.

Our article on AI in the game art pipeline covers where AI helps and where it does not.

Choosing an art partner

• Portfolio fit: look for work in your style and for your platform, not just beautiful renders.
• In-engine examples: ask to see assets running in Unity or Unreal, ideally on mobile or VR if that is your target.
• Process: clear milestones, approval stages and a named art lead.
• Capacity: can they scale up for content peaks and keep quality consistent?
• References: talk to previous clients about deadlines and communication.

Keeping style consistent across vendors

Large projects sometimes use several art vendors. Consistency then depends on a strong style guide, shared base assets such as material libraries and colour palettes, and a single art lead approving everything. Without these, worlds start to look like they were made by different teams, because they were.

Cost drivers

For character-specific ranges see 3D character modelling costs.

Working with us

Our art team produces 2D and 3D characters, environments, UI, animation and effects, optimised for mobile, PC, VR and AR. See 3D game development or request a quote.

Sources: Unity: importing models · Khronos: glTF · Unreal Engine: physically based materials · U.S. Copyright Office: copyright and AI. Checked October 20, 2026.

Related: 3D game development · 2D game development · Outsource game development

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

Game assets are the files that make up a game's content: 3D models, textures, 2D sprites, animations, user interface art, visual effects, sound and music. Artists create them in tools such as Blender, Maya, Photoshop or Krita, export them in formats like FBX, glTF, PNG and WAV, and the engine imports and optimises them so the game runs within its performance budget. Code makes the game work; assets are what players see and hear.

The main types of game assets

How a 3D asset is made

1. Concept: an artist sketches the character or prop from several angles.
2. Modelling: the shape is built in polygons; detailed assets are often sculpted at high resolution first.
3. Retopology: a lighter, game-ready mesh is built over the sculpt so it renders quickly.
4. UV unwrapping: the surface is flattened so a 2D texture can wrap around it.
5. Texturing: colour and surface detail are painted, often baking detail from the sculpt into a normal map.
6. Rigging and skinning: a skeleton is added and the mesh attached so it can move.
7. Animation: walk, run, attack and idle cycles are keyed or motion-captured.
8. Export and import: the asset is exported, usually as FBX or glTF, and set up in the engine with materials and settings.

Textures and PBR materials

Most modern games use physically based rendering (PBR), where a material is described by several texture maps that tell the engine how light behaves on the surface:

• Base colour (albedo): the surface colour without lighting.
• Normal map: fakes small bumps and grooves without extra polygons.
• Roughness: how sharp or blurry reflections are.
• Metallic: which parts behave like metal.
• Ambient occlusion: soft shadowing in creases.

2D assets

In 2D games, characters are usually either frame-by-frame sprites arranged in sprite sheets or cut into parts and animated with skeletal tools such as Spine. Sprites are packed into texture atlases so the engine can draw many of them at once. Our 2D game development page shows the styles we work in.

Performance budgets

Every asset costs memory and processing time, and the budget depends heavily on the platform: a mid-range phone or a standalone VR headset has far less headroom than a gaming PC. Teams set budgets early for:

Buying assets versus making them

Marketplaces such as the Unity Asset Store and Epic's Fab offer thousands of assets that can save weeks of work, especially for prototypes and background props. The trade-offs are style consistency, since mixing packs often looks mismatched, and licensing, since each item has its own terms. Unique characters and key art are usually worth creating custom. Our article on game art outsourcing explains how to brief artists, and 3D character modelling costs breaks down what custom characters cost.

Assets for VR and AR

Headsets and phones running AR have tight budgets because they render at high frame rates, and in VR twice, once per eye. Real-world scale matters too: a chair must be the size of a real chair. For AR furniture and product apps, models are usually built from the manufacturer's CAD or photographs and checked against real measurements; our article on AR furniture apps explains the process.

Keeping assets organised

Projects with thousands of assets need naming rules, a clear folder structure, version control that handles large binary files, and a record of where every bought or free asset came from and under what licence. Setting these rules on day one saves painful clean-ups later.

Our art team

We produce 2D and 3D assets, characters, environments, UI and effects for mobile, PC, VR and AR, optimised for each platform. See 3D game development or request a quote.

Sources: Unity: importing models · Khronos: glTF · Unity: level of detail · Unreal Engine: physically based materials · Blender. Checked October 20, 2026.

Related: 3D game development · 2D game development · Get a quote

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

For most games in 2026, a managed backend is the right start: Firebase suits small to medium games and async features, PlayFab and Unity Gaming Services offer game-specific systems such as economies and leaderboards, and Nakama is a strong open-source option you can host yourself. Build a custom backend only when rules, scale or cost demand it. Choose on the features you need, how it fits your engine, pricing at your expected player numbers, and how easily you could move your data later.

What a game backend does

The main options

How to choose

• Features: list what the game needs at launch and in the first year; prefer the option that covers most of it out of the box.
• Engine: Unity Gaming Services fits Unity tightly; Firebase, PlayFab and Nakama support several engines.
• Scale and latency: real-time multiplayer needs server hosting close to players; async games are far less demanding.
• Pricing model: estimate monthly costs at 10,000, 100,000 and a million players using each provider's current pricing page.
• Lock-in: check how you would export player data and move if prices or terms change.
• Team skills: a backend your team understands beats a "better" one nobody can debug at 2 a.m.

Typical choices by game type

Security basics

• Never trust the client: validate purchases, rewards and scores on the server.
• Lock database rules so players can read and write only their own data.
• Validate store receipts server-side for valuable purchases.
• Rate-limit sensitive calls to slow down bots and abuse.

See anti-cheat for small multiplayer games for more.

Estimating cost before you commit

Backend pricing is usually based on usage: reads and writes, function calls, storage, bandwidth, active users or server hours, depending on the provider. Before choosing, write down what a typical player does in a day, such as logins, saves, leaderboard reads and purchases, then multiply by expected daily players and plug the numbers into each provider's calculator. Repeat for a launch spike, when featuring or an event can bring many times the normal traffic.

Two habits keep bills predictable: batch small writes into fewer larger ones, and cache data that rarely changes, such as shop configuration, on the device. Many surprise invoices come from a single chatty feature, such as a leaderboard refreshed every second, rather than from player growth.

Planning for change

Wrap backend calls behind your own interfaces in the game code, so switching provider later changes one layer rather than the whole game. Keep a way to export player data. Many games start on a managed service and move parts to custom services only when scale makes it worthwhile.

Also think about regions and regulation early. If you have many players in Europe or the Gulf, check where each provider stores data and whether that matches your privacy commitments. Moving player data between regions after launch is far harder than choosing the right region on day one.

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

The most common game development mistakes are making the scope too big, skipping a playable prototype, playtesting too late, leaving marketing until launch and underestimating polish and bug fixing. Each one is avoidable with the same habits: cut the idea to its smallest fun version, prove the core loop with grey boxes, put the game in front of strangers every few weeks, and plan the launch from the first month.

1. The scope is too big

The classic mistake. A first project planned as an open world with crafting, story and multiplayer rarely ships. Fix: define the smallest version that is still fun, finish it, then grow it with updates.

2. No prototype of the core loop

Teams commission art, write lore and build menus before knowing whether the main action is enjoyable. Fix: build a grey-box prototype first and do not move on until people enjoy it with placeholder shapes. See our game prototyping guide.

3. Adding features instead of finishing

New ideas feel more exciting than the last 20% of the work. Fix: keep a "later" list. Ideas go there unless they fix a problem testers actually had.

4. Playtesting late, or only with friends

Friends are kind, and developers know where everything is. Fix: watch strangers play without helping them, every few weeks, from the prototype onwards. Where they get lost is where the game needs work.

5. Building multiplayer after single-player

Networking changes how almost every system is written. Adding it at the end usually means rebuilding the game. Fix: if the game will be multiplayer, prototype it online from day one. Our article on what a multiplayer FPS costs explains why.

6. Ignoring low-end devices

A game that runs well on the developer's laptop or flagship phone may stutter on the devices most players own. Fix: pick a minimum device early, test on it every week and use the engine's profiler. Unity's documentation recommends profiling on the target device rather than in the editor.

7. No version control

One corrupted file or bad change can cost weeks. Fix: use version control such as Git or Unity Version Control from the first day, with off-site backups.

8. Starting marketing at launch

On Steam, wishlists collected before launch drive release-day visibility, and players cannot buy a game they have never heard of. Fix: publish a store page early, share progress, and build a list of interested players months before release. Our indie marketing guide and Steam wishlists guide show how.

9. Treating launch as the end

Most successful games improve after release with fixes, content and events. Fix: keep budget and people for the first three months after launch. See LiveOps.

10. No analytics

Without data you cannot tell where players quit or what they buy. Fix: add a basic analytics tool before soft launch and track tutorial completion, level progress and retention. Our mobile game KPIs guide lists what to measure.

11. Contracts that do not transfer the code

Some outsourcing agreements leave the source code or rights with the contractor. Fix: make sure the contract assigns all IP and delivers the full source on payment. Our guide on choosing a studio covers the questions to ask.

12. Underestimating polish and bug fixing

The last stretch, from "it works" to "it feels finished", routinely takes as long as the first playable version. Store submission adds its own checks. Fix: plan explicit polish time and read our store submission checklist before you need it.

Warning signs your project is in trouble

• The release date has moved more than once and nobody can say what is left to do.
• There is no build that someone outside the team can play today.
• New features keep arriving while old bugs stay open.
• Nobody has looked at performance on the minimum target device in weeks.
• There is no store page, trailer or community a month before launch.

Any one of these is fixable. Several at once usually mean the scope needs cutting now, before the budget runs out.

A pre-production checklist

Most of the mistakes above are decided before production starts. Before committing a budget, make sure you can answer yes to each of these:

How studios avoid these

Experienced teams use the same safeguards: milestone plans with a playable build at every milestone, weekly builds the client can try, outside testers, and a launch plan from the start. That is how we run projects; see co-development or outsourced game development.

Sources: GDC Vault: conference talks and postmortems · Steamworks: visibility on Steam · Unity: performance profiling tips · Pro Git: about version control. Checked October 20, 2026.

Related: Co-development · Outsource game development · Get a quote

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

The trends to plan for in 2027 are already in motion: open mobile payments and web shops after the 2025 US rulings against Apple and Google, AI in production with disclosure and consent rules, engine migrations such as Unity's move away from the Built-in pipeline, a more diverse XR landscape, growing web and instant-play games, major ownership changes such as the EA take-private, Gulf investment, and stricter children's privacy rules. Teams that plan for these now will spend less and launch faster.

1. Mobile payments open up

After an April 2025 court order, Apple allowed US apps to link to outside purchases, and Google Play had to allow alternative billing and external links in the US from October 2025. Expect more games to add web shops and direct relationships with players in 2027. Plan your payment flows, pricing and analytics for both store and web purchases. See the future of mobile gaming.

2. AI everywhere, with rules

AI tools are now part of most pipelines, from concept art to testing. The rules are catching up: Steam requires AI content disclosure, and the 2025 SAG-AFTRA agreement sets consent and pay terms for performers' digital replicas. In 2027, expect clients and players to ask how AI was used. Keep records of tools and licences and disclose clearly. See AI voice for games and AI in the art pipeline.

3. Engine migrations

Unity 6.5 deprecated the Built-in Render Pipeline, so many Unity games will move to URP over the next few years. Unity also ended its own Multiplay server hosting in March 2026, so online games need portable hosting. Godot 4.6 continues to mature for 2D and smaller 3D projects. Budget migrations deliberately rather than as emergencies; see the Unity 6 upgrade guide and URP shader conversion.

4. XR diversifies

XR is no longer one headset. Meta Quest remains the largest consumer VR platform, Android XR arrived with Samsung Galaxy XR, Apple updated Vision Pro with the M5 chip, and smart glasses opened to developers. In enterprise, Meta ended Quest for Business sales in February 2026, changing how organisations manage devices. Build XR in engines that target several platforms, and design for passthrough and mixed reality. See Android XR and Vision Pro development.

5. Web and instant play

Browser games and instant-play formats keep growing, helped by better web engines and distribution through messaging apps and portals. They suit casual games and brand campaigns that need zero-install reach. See web games in 2026.

6. Ownership and funding shifts

The completion of the PIF-led take-private of Electronic Arts in August 2026 was one of the largest deals in games history, and Gulf investment continues through Saudi Arabia's national gaming strategy. Funding for independent studios remains selective. Expect more co-development, outsourcing and partnership deals as large companies restructure and smaller ones stay lean. See the Saudi gaming market and funding an indie game.

7. Children's privacy tightens

The amended COPPA Rule has applied in full since April 2026, and the stores enforce their own family policies. Games likely to be played by children need privacy-first SDK choices and age-appropriate design from the start. See rules for kids' games.

8. Store technical requirements keep rising

Google Play required API level 36 for new apps and updates from August 2026, and Apple updated its age ratings. Every year brings new requirements, so keep engines and SDKs current and check store rules at the start of each release cycle. See our store submission checklist.

9. Handheld PC play

Handheld gaming PCs, led by Steam Deck, make controller support, readable UI and power-efficient performance standard expectations for PC games. See Steam Deck Verified.

What is not changing

Fundamentals still decide success: a fun core loop proven early, scope a team can finish, polish, performance on real devices, and a launch plan that starts months before release. Trends change the tools and the rules around a game, not the need for it to be good.

What to do now

Planning a 2027 project with us

We build mobile, PC, VR and AR games with these changes planned in from the start. See our quote form or the cost calculator.

Sources: TechCrunch: Apple US App Store rule change · Google Play: US programs after Epic v. Google · Silver Lake: EA acquisition completed · Unity: Multiplay Hosting status · Federal Register: amended COPPA Rule · TheWrap: SAG-AFTRA video game deal. Checked October 20, 2026.

Related: Get a quote · Mobile game development · VR development

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

Game localization adapts a game's text, UI, audio and store presence for other languages and cultures. Prepare the code first (all text in string tables, flexible UI, fonts and right-to-left support), choose languages from market data, translate with native game translators who have context, review cultural content, and test every language in the running build. Cost depends mainly on word count, the number of languages, voice-over and how much testing you do. Late text changes are the most avoidable expense.

Internationalisation: the cheap part done early

• No text in code or images: every string lives in a table with a key.
• Placeholders and plurals: "You have {count} coins" with plural rules per language, for example using ICU message format.
• UI that grows: translations are often much longer than English; buttons and boxes must expand or text must wrap.
• Fonts: include fonts that cover every target script.
• Right-to-left: plan for Arabic and Hebrew layout from the start if they are likely markets.
• Dates, numbers and currency: format by locale, not by hand.

Unity's Localization package and Unreal Engine's Localization Dashboard both handle string tables, locale switching and asset variants.

Choosing languages

Start from data rather than habit: where your store traffic and wishlists come from, which countries your genre does well in, and where your competitors are localised. Steam provides wishlist and traffic data by country. A low-cost test is to localise the store page and screenshots for a candidate language first and watch whether traffic and wishlists from that market rise.

The localization process

1. Freeze text: localise when text is close to final; every later change multiplies across languages.
2. Export with context: each string with notes, screenshots, character limits and who is speaking.
3. Glossary and style guide: names, terms and tone agreed per language.
4. Translation: native-speaking translators with game experience.
5. Cultural review: symbols, gestures, colours, humour and content that may offend or confuse.
6. Integration: import translations and build each language.
7. Linguistic QA: testers play the game in each language, catching truncation, missing strings, wrong context and font problems.

Special scripts

Our guide to Arabic game development covers right-to-left work in depth.

Voice-over

Voice multiplies cost and schedule: casting, studio time and lip-sync per language. Many games localise voice only for the largest markets and use subtitles elsewhere. If you use AI voice, check licensing, consent and union rules carefully; see AI voice for games.

Store pages and ratings

Localise the store description, screenshots with text, trailers' subtitles and keywords. Some markets need separate age ratings or classification; for example, Saudi Arabia requires games to be classified by its media regulator. See our Saudi gaming market guide.

What drives the cost

Localising updates in a live game

Live games add new text with every event and update, so localization becomes a continuous pipeline rather than a one-off project. Successful teams freeze each update's text a fixed number of days before release, send it to translators automatically from the string tables, and run a short LQA pass per language as part of the release checklist. Without that rhythm, events launch in English only, or translated text arrives after the event has ended.

Machine translation and AI

Machine translation and AI tools can produce fast first drafts, especially for large volumes of simple text, but game text is full of names, jokes, character voice and context that automated tools get wrong. Most quality-focused studios use them, if at all, as a draft for professional translators to edit, and still run linguistic QA. For store pages and marketing in key markets, human writers are worth the cost.

Common mistakes

• Building sentences from fragments in code, which breaks in other languages' grammar.
• Text baked into images and textures.
• No context for translators, leading to wrong meanings.
• Skipping LQA, so truncation and missing strings reach players.
• Localising before text is stable.

Working with us

We prepare games for localization from day one, integrate translations and run LQA, including Arabic right-to-left. See our Middle East page or request a quote.

Sources: Unity: Localization package · Unreal Engine: localization overview · ICU: message formatting · Unity: Advanced Text Generator · Steamworks: localization. Checked October 20, 2026.

Related: Game development for the Middle East · Mobile game development · Get a quote

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

A strong publisher pitch shows the game in the first seconds, explains the hook in one sentence, and backs it with a playable vertical slice, a realistic budget and milestones, a team that can deliver and evidence that players care, such as wishlists or playtest results. Keep the deck to around 10–15 slides, target publishers whose catalogue fits your game, and read deal terms carefully before signing.

The deck, slide by slide

The vertical slice

A vertical slice is a short section of the game at near-final quality: art, audio, game feel and UI. It answers the publisher's biggest question, "can this team make the game look and play like the pitch?", better than any slide. Five to fifteen minutes of polished play beats an hour of rough content. Our prototyping guide shows how to get there.

Choosing publishers

• Study their catalogues: do they publish your genre, platform and budget size?
• Look at how they market games similar to yours.
• Check their submission process and follow it exactly.
• Ask developers who worked with them about the experience.

A smaller publisher that loves your genre often does more for your game than a large one that does not.

Budget and milestones

Publishers want to see that you know what the game costs. Break the budget into team, contractors, tools, audio, localisation, QA and contingency, and tie milestones to playable deliverables. Unrealistically low budgets are a red flag, not an advantage. Our cost calculator and cost guide help sanity-check numbers.

Evidence that players care

Numbers reduce risk for publishers: Steam wishlists, demo downloads and playtime, playtest scores, community size and engagement. Valve notes that wishlisters are notified at launch and on discounts, which is why publishers ask about wishlists; see our Steam wishlists guide.

The meeting

1. Open with the hook and gameplay within the first minute.
2. Keep the deck short and leave time for questions.
3. Offer to play the build live or hand it over.
4. Listen: questions reveal what the publisher is worried about.
5. End with a clear next step.

Follow-up

Send the deck, a build link, the trailer and answers to any open questions within a day or two. Keep updates short and occasional; a meaningful milestone, such as a successful demo or festival, is a good reason to get back in touch.

Deal terms to check

Get a lawyer experienced in games to review the contract before signing.

Common pitch mistakes

• Ten slides of story and lore before any gameplay.
• Comparable titles that are huge hits made by much larger teams.
• A budget that is clearly too low for the scope.
• No playable build, or a build that crashes in the meeting.
• Asking for funding without saying what the money will deliver.

Pitching remotely

Many pitches now happen on video calls. Test screen sharing and audio beforehand, have gameplay video ready in case the live build stutters, and send the build link before the call so the publisher can try it. Keep a shorter version of the deck for calls, since attention drops faster on screen than in a room.

If publishers say no

Many good games are rejected for reasons unrelated to quality: portfolio fit, timing or budget. Ask for feedback, improve the slice, and consider other routes such as grants, crowdfunding or self-publishing; see how to fund an indie game.

Getting a pitch-ready build

We build prototypes and vertical slices on fixed milestones, so you can pitch with a playable game. See our quote form or PC game development.

Sources: GDC Vault: pitching and business talks · Steamworks: wishlists · UK Games Fund · Kickstarter: fees. Checked October 20, 2026.

Related: Get a quote · PC game development · Cost calculator

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

Porting a game means adapting it to a new platform: reworking controls and interface, hitting performance targets on new hardware, integrating platform features such as achievements and saves, and passing the platform's rules or certification. Mobile-to-PC and PC-to-Steam-Deck ports are the most common; console ports also require joining each platform holder's developer programme and passing their certification. The effort depends mainly on the engine and how platform-specific the original code is.

What changes when you port

Common porting routes

Mobile to PC and Steam

The most frequent request. Beyond controls and resolution, many mobile games need pacing and monetisation changes for PC players. Our dedicated guide to porting a mobile game to PC and Steam covers it in detail.

PC to Steam Deck

Steam Deck runs most PC games, but a good experience needs controller support, readable text at its screen size and sensible performance settings. Valve's compatibility programme rates games, and our Steam Deck Verified guide explains the criteria.

To consoles

Each platform holder runs its own programme for developers: the Nintendo Developer Portal, PlayStation Partners, and ID@Xbox for independent developers on Xbox. Joining usually involves an application and agreement, after which you get access to development kits, documentation and tools under NDA. Before release, the game must pass the platform's certification against its technical requirements. Check that your engine version and licence support the target console.

The porting process

1. Assessment: review the codebase, engine version, plugins and assets for anything platform-specific.
2. Technical port: get the game building and running on the target.
3. Input and UI: rework controls and interface for the new device.
4. Platform features: achievements, saves, accounts and online services.
5. Optimisation: profile on target hardware and hit frame-rate and memory targets.
6. Certification or review: fix issues until the platform approves the build.
7. Release: store assets, ratings, pricing and launch plan.

What makes a port easy or hard

An engine upgrade is sometimes required before a port. For Unity projects, our Unity 6 upgrade guide covers what that involves.

Business questions before porting

• Does the game's audience exist on the new platform?
• Does the business model fit, for example free-to-play on console versus premium on PC?
• Will you support cross-progression or cross-play, and what do the platforms allow?
• Who will handle post-launch patches on each platform?

Controls and interface in detail

Controls are where ports most often feel cheap. A good port shows the right button prompts for the device in use, switches prompts instantly when the player changes from keyboard to controller, supports remapping, and never requires a mouse in a game played from the sofa. Menus need a clear focus highlight for controller navigation, and every screen must be reachable without touch.

Interfaces designed for phones often have small text and dense layouts. On a TV, text must be readable from several metres away; on Steam Deck, from a small screen held in the hands. Most ports scale UI by device and offer a text size option. Safe areas matter too: some TVs crop the edges of the picture, and phones have notches.

Performance targets by platform

Working with a porting partner

Original developers often hand ports to co-development studios so their core team can keep working on the next update. A good partner starts with an assessment and a fixed plan, keeps the original team informed, and returns code in a state the original team can maintain. Our articles on co-development and cross-platform development go further.

Porting with us

We port Unity games between mobile, PC, Steam and Steam Deck, and plan cross-platform builds from day one. See co-development or PC game development.

Sources: Nintendo Developer Portal · PlayStation Partners · ID@Xbox · Steamworks: Steam Deck · Unity: platform-specific information. Checked October 20, 2026.

Related: Co-development · PC game development · Get a quote

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

Game QA covers functional testing, device compatibility, performance, regression, localization, multiplayer, accessibility and store compliance. Good QA starts at the prototype with smoke tests on every build and full test passes at milestones and before submission, combining manual exploratory testing with automated tests where they pay off. QA is usually priced hourly or per tester, as a fixed price per milestone, or as a monthly retainer for live games, and the main cost drivers are platforms, devices and content size.

Types of testing

When testing happens

1. Prototype: quick checks and playtests to validate the core loop.
2. Every build: a short smoke test so broken builds never reach the team or client.
3. Milestones: full functional and regression passes on the target devices.
4. Before submission: compliance and store checks; see our store submission checklist.
5. After launch: regression on every update, plus investigation of player-reported issues.

Device coverage

Mobile games run on thousands of device and OS combinations. QA teams build a device matrix from analytics or market data: a low-end, mid-range and high-end device per platform, popular models in target markets, and the oldest OS versions supported. Cloud device labs such as Firebase Test Lab and AWS Device Farm add breadth for automated runs, while physical devices remain essential for touch, heat and real performance.

Automation: where it helps

Unity Test Framework and Unreal Engine's Automation System support unit and functional tests, and continuous integration can run them on every commit. Automation saves money on long projects and live games; on short projects, focused manual testing is often more efficient.

What a good bug report contains

• A short, specific title.
• Steps to reproduce, numbered.
• Expected result and actual result.
• Build number, device, OS version and settings.
• Logs, screenshots and a short video.
• Severity (how bad) and priority (how urgent), agreed with the team.

A bug that cannot be reproduced cannot be fixed. Clear reports are the most valuable thing QA produces. Crash reporting tools in the build, such as Firebase Crashlytics on mobile, add stack traces and device data automatically, which turns many "it crashed sometimes" reports into fixable issues.

Severity levels

How QA is priced

The main cost drivers are the number of platforms, the size of the device matrix, the amount of content, multiplayer testing and the number of languages. In our projects, QA is included in the build plan rather than bolted on at the end.

Testing multiplayer and online features

Online games need tests that single-player games do not: matches with full player counts, players joining and leaving mid-match, reconnects after a phone call or network switch, and play on slow or unstable connections. Network simulation tools can add latency and packet loss on purpose, and bots can fill matches for load tests. Server load testing before launch shows whether infrastructure survives the first weekend.

Building a test plan

1. List features and systems, and rank them by risk to players and revenue.
2. Choose devices and platforms from analytics or market data.
3. Write test cases for high-risk areas, such as purchases, saves and progression.
4. Schedule smoke tests per build, full passes per milestone and a release candidate pass.
5. Agree severity definitions and the bug workflow with developers.
6. Review results after each pass and adjust the plan.

Signs QA is under-resourced

• Crash rates jump after updates.
• The same bugs return after being fixed.
• Store reviews mention problems the team did not know about.
• Testing only happens in the final week before release.

Working with us

We test across devices and platforms throughout development and after launch. See mobile game development or request a quote. For accessibility testing, the Game Accessibility Guidelines are a useful checklist.

Sources: Firebase Test Lab · AWS Device Farm · Unity Test Framework · Unreal Engine: Automation System · Game Accessibility Guidelines. Checked October 20, 2026.

Related: Mobile game development · Co-development · Get a quote

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

Store reviewers check that a game works, matches its store listing, respects privacy and payment rules, and has the correct age rating. The most common rejections are crashes or unfinished features, misleading screenshots or descriptions, missing privacy disclosures, purchase problems, and technical requirements such as Google Play's target API level. A focused QA pass against each store's current rules before submission avoids most of them.

What each store reviews

The most common rejection reasons

1. Crashes and unfinished features

Apple's guideline 2.1 asks for complete, tested builds. Crashes on launch, placeholder content, broken links and features that do nothing are the classic rejections. Test on real devices, including older ones.

2. Metadata that does not match the game

Screenshots, videos and descriptions must show the actual game. Promising features that are not there, or using another company's brand, leads to rejection.

3. Privacy

Stores require accurate privacy disclosures: Apple's privacy labels and Google Play's Data safety form must match what the game and its SDKs actually collect. Permission prompts must explain why access is needed. Third-party SDKs, especially ads and analytics, are the usual source of surprises.

4. Purchases

Digital items must follow each store's payment rules for the storefront, purchases must work in review, and non-consumables need a restore option. Loot boxes must show odds where required.

5. Technical requirements

Google Play rejects updates that do not meet the current target API level; Apple requires builds made with recent SDKs. These requirements change every year, so check them at the start of each release cycle, not the day before submission.

6. Age ratings and kids rules

Ratings questionnaires must be answered honestly; games aimed at children have stricter rules on ads, data and links. See our kids game rules guide.

What QA checks before submission

Our guide to game QA testing explains how this fits into a full test plan.

Pre-submission checklist

• Built with the current required SDKs and target API level.
• Tested on real devices, including the minimum supported device.
• Privacy labels and Data safety form updated for every SDK.
• Age rating questionnaire answered for the current version of the rules.
• All purchases tested with sandbox or licence-tester accounts; restore works.
• Store screenshots and videos show the current build.
• A demo account and review notes provided if the game needs login.
• Support URL and privacy policy URL live and correct.

Timing the release

Review times vary and can be longer around holidays and major platform launches. Submit well before your planned date, and use each store's option to release manually after approval so marketing and launch timing stay in your control. On Google Play, staged rollouts let you release an update to a small percentage of users first and halt it if crash rates rise. On the App Store, phased release for automatic updates spreads an update over several days. Both are cheap insurance against a bad build reaching everyone at once.

Keep a release log for every submission: build number, what changed, review notes sent, and the reviewer's response. When a rejection repeats months later, the log saves hours of guessing.

If you are rejected

Read the cited guideline carefully, fix the issue, and reply with a short, clear explanation of what changed. If you believe the reviewer misunderstood, explain politely with steps or a video; both Apple and Google provide ways to respond or appeal. Build time for one resubmission into every launch plan.

Platform-specific guides

For Android specifics, see publishing on Google Play. For PC, see Steam Next Fest and Steam Deck Verified.

Getting help

We handle QA, store submission and resubmissions for clients on iOS, Android and Steam. See mobile game development or request a quote.

Sources: Apple: App Store Review Guidelines · 9to5Mac: Apple's new age rating system · Google Play: target API level requirements · Google Play: Data safety section · Steamworks: review process. Checked October 20, 2026.

Related: Mobile game development · PC game development · Get a quote

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

Gamification works when game mechanics reinforce the real value of an app: progress toward a goal the user cares about, challenges that build competence, and social features that create belonging. Points and badges alone rarely change behaviour for long. Research such as Hamari and colleagues' 2014 review found gamification generally has positive effects, but results depend heavily on the context and the users. Design from motivation, test with A/B experiments, and avoid manipulative patterns.

Start with motivation, not mechanics

Self-determination theory, a widely used model of motivation, describes three basic needs:

• Autonomy: users feel in control of what they do.
• Competence: users feel they are getting better.
• Relatedness: users feel connected to others.

Good game mechanics serve these needs. A progress bar supports competence; choice of challenges supports autonomy; a team goal supports relatedness. Mechanics that undermine them, such as forced streaks or public shaming, backfire.

Mechanics that work

What research says

Hamari, Koivisto and Sarsa reviewed empirical studies of gamification in 2014 and found that most reported positive effects, but that outcomes depended on the context being gamified and on the users. In practice that means copying another app's mechanics rarely works; mechanics need to fit your users and your product's core value, and they need testing.

Common pitfalls

• Pointsification: points and badges that mean nothing, which users quickly ignore.
• Crowding out interest: extrinsic rewards can reduce interest in activities people already enjoyed.
• Streak anxiety: punishing a missed day makes users quit entirely.
• Dark patterns: manipulative timers, guilt messages and hidden costs damage trust and can break store rules or consumer law.
• Game layer over a weak product: gamification amplifies value; it cannot create it.

Examples by app category

How to design it

1. Define the core action that delivers value, such as completing a lesson or a workout.
2. Identify where users drop off and why.
3. Choose one or two mechanics that address that drop-off.
4. Prototype quickly and test with real users.
5. Launch as an A/B test and measure the core action and retention, not just engagement with the game layer.
6. Iterate, and remove mechanics that do not help.

A worked example

Imagine a savings app where many users set a goal and then stop opening the app after the first week. A thoughtful game layer might show the goal as a journey with milestones, celebrate each deposit with a short animation, offer optional weekly challenges such as skipping one takeaway meal, and let friends cheer each other on. A streak of weekly deposits would allow one missed week without resetting. Each mechanic supports a real goal, saving money, rather than distracting from it, and each can be tested separately to see which actually raises deposits.

Notifications done well

Notifications are often the most powerful and most abused part of gamification. Send them when they help the user, such as a reminder before a streak would break or news that a friend completed a challenge, let users choose frequency, and stop sending them to users who never respond. Annoying notifications lead to disabled notifications, and often to deleted apps.

Ethics and accessibility

Design for users' long-term interest, not just time in the app. Avoid guilt, fear of missing out and hidden costs; give users control over notifications and social features; and make celebrations and challenges accessible, following guidelines such as the W3C's WCAG for colour, motion and text. Apps for children need extra care; see rules for kids' apps.

Building the game layer

Simple mechanics such as progress bars and streaks can be built in the app's existing native or web code. Richer game layers, such as mini-games, 3D rewards or interactive characters, are often built in Unity and embedded in the app. Our article on gamification for brands covers campaign-style games, and serious games covers training.

Costs

Adding a few mechanics to an existing app can be a small project; a full game layer with mini-games and rewards is closer to building a small game. Send us your app and goals for a fixed quote, or see Unity app development.

Sources: Hamari, Koivisto & Sarsa (2014): Does gamification work? · Self-Determination Theory · Apple: Human Interface Guidelines · W3C: WCAG accessibility guidelines. Checked October 20, 2026.

Related: Unity app development · Mobile game development · Get a quote

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

Both Godot 4.6 and Unity 6 are strong choices for 2D games. Choose Godot if you want a free, open-source, lightweight engine with an excellent dedicated 2D workflow and no licensing concerns. Choose Unity if you need mature mobile monetisation and analytics SDKs, official console support, a huge asset and tutorial ecosystem, or a larger pool of developers to hire. For most teams the deciding factors are platforms, existing skills and how much ready-made tooling they need.

At a glance

The 2D workflow

Godot's 2D is a first-class engine, not a mode of a 3D engine: positions are in pixels, scenes are built from nodes, and the editor is fast to work in. Godot 4.6, released in January 2026, improved 2D rendering performance through better batching and made TileMapLayer updates more efficient, which helps on older devices.

Unity's 2D runs on its general engine with dedicated packages: the Universal Render Pipeline's 2D renderer with lights and shadows, Tilemap, Sprite Shape for organic terrain, the 2D Animation package for skeletal animation, and an Aseprite importer for pixel artists. It is very capable, but has more settings to understand.

Performance

Both engines run 2D games comfortably on modern phones and PCs when projects are built sensibly. Performance problems in 2D usually come from overdraw, too many separate sprites and materials, or heavy scripts, not from the engine choice. Profile on your minimum device in either engine.

Platforms and consoles

Both export to Windows, macOS, Linux, Android, iOS and the web. Consoles are the biggest practical difference: console SDKs are under NDA, so Godot games usually reach Switch, PlayStation and Xbox through specialised porting partners such as W4 Games, while Unity supports consoles through official platform programmes. If consoles are central to your plan, factor this in early. Our guide to game porting covers console programmes.

Monetisation and services

For free-to-play mobile games, Unity has the advantage: most ad networks, mediation platforms, analytics tools and backends publish official Unity SDKs. In Godot, many of these are available through community plugins or need custom integration. Premium PC games, where monetisation is a store purchase, feel this difference much less. See ad mediation for mobile games.

Licensing and long-term risk

Godot's MIT licence means no fees and no dependence on a company's pricing decisions, which became a priority for many developers after Unity's 2023 pricing controversy. Unity cancelled its runtime fee and remains free on Personal up to $200,000 in revenue and funding. Our Unity pricing guide explains the current plans.

Team and hiring

Unity's much larger developer base makes hiring and outsourcing easier, especially for mobile. Godot's community is smaller but growing quickly, and GDScript is easy to learn for programmers from Python or similar languages. Consider which engine your team already knows; switching costs months of productivity.

Pixel art and animation

Both engines handle pixel art well with the right settings: point filtering, no compression artefacts, and a pixel-perfect camera. Godot's 2D renderer works in pixels by default, which many pixel artists find natural. Unity offers a Pixel Perfect Camera component in URP and imports Aseprite files directly. For skeletal 2D animation, Unity's 2D Animation package and Godot's Skeleton2D both work; Spine is a popular external tool with runtimes for each.

Migrating between them

There is no automatic converter between Unity and Godot. Art, audio and design documents transfer; scenes, scripts and editor tooling must be rebuilt. For a released game, migration rarely pays off unless licensing, platform or performance needs force it. For a new project, the decision is cheap, so make it deliberately at the start.

Which should you choose?

Our view

We build most commercial mobile games in Unity because of its SDK ecosystem, and we respect Godot as an excellent engine for 2D PC and indie projects. For a broader comparison on mobile, see Unity vs Godot for mobile games, or our 2D game development services.

Sources: Godot 4.6 release · Godot: license · Unity: 2D game development · Unity: pricing and plans · W4 Games. Checked October 20, 2026.

Related: 2D game development · Unity game development · Get a quote

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

Indie games are funded through self-funding (often from client work), publisher deals, grants such as the UK Games Fund or Epic MegaGrants, crowdfunding, investors, platform and subscription deals, early access, and tax credits where available. Each trades money for something: revenue share, equity, control or time. Most successful indies combine two or three sources, and all of them need a playable vertical slice, a clear budget and a credible plan.

The options compared

Publishers

A publisher typically pays an advance and provides services such as marketing, QA, localisation and platform relationships. In return it takes a share of revenue, and advances are usually recouped from revenue before the split changes. Read every deal for: revenue split before and after recoupment, IP ownership, milestones and what happens if you miss one, marketing commitments, and rights to sequels and ports. Our guide on pitching to publishers covers the deck.

Grants and public funds

• UK Games Fund: grants and programmes for early-stage UK developers.
• Epic MegaGrants: grants for projects using Unreal Engine or advancing open-source tools; Epic now runs two submission windows a year, and both 2026 windows have closed.
• National and regional programmes: for example Business Finland in Finland, and Creative Europe MEDIA support for European studios.

Check eligibility carefully, apply early, and keep good records; most grants require reporting on how money was spent.

Crowdfunding

Platforms such as Kickstarter run all-or-nothing campaigns: you receive the money only if the goal is reached, minus a platform fee and payment processing fees. A campaign also proves demand to publishers and builds a community, but it needs a strong trailer, an existing audience and careful reward planning; physical rewards can eat the budget.

Investors

Investors buy equity in the studio rather than funding a single game. They expect growth, usually across several titles, so this route suits teams with a studio plan, not a one-off project.

Tax credits

Some countries reduce the cost of development through tax credits. In the UK, the Video Games Expenditure Credit is worth 34% of qualifying expenditure for games certified as British; see our VGEC guide.

What every funder wants to see

1. A playable vertical slice that shows the core loop and target quality.
2. A clear hook that explains why players will care.
3. A realistic budget and milestone plan.
4. Evidence of interest: wishlists, followers, playtest results.
5. A team that can finish, shown through previous shipped work.

Our prototyping guide and Steam wishlists guide help with the first and fourth points.

Early access and demos

Early access lets players buy the game while it is still in development, bringing revenue and feedback earlier. It works for games that are already fun and can improve visibly with regular updates; it backfires when the build is thin or updates stall. A free demo, by contrast, brings no direct revenue but grows wishlists and press interest, which strengthens every other funding route.

Platform and subscription deals

Platform holders and subscription services sometimes fund games or pay guarantees in exchange for exclusivity, timed exclusivity or inclusion in a service at launch. These deals can cover a large part of a budget, but they change how and where the game launches, so weigh the guarantee against lost sales elsewhere and any restrictions on marketing.

Choosing the right mix

• Want full control and can move slowly? Self-fund with client work, plus grants.
• Need marketing muscle and can share revenue? A publisher.
• Have an audience already? Crowdfunding or early access.
• Building a studio, not just a game? Investors.

Red flags in funding offers

• Advances with recoupment terms that include unlimited marketing costs.
• IP transfer to the funder for a modest advance.
• Milestones you cannot realistically meet, with harsh penalties for missing them.
• Pressure to sign quickly without legal review.
• Vague promises of marketing with no committed spend or activities.

Stretching the budget

Whatever the source, money goes further with a small scope, a proven prototype and a partner who quotes fixed milestones. Our cost calculator gives a quick range, and our guide to starting a studio covers the business side.

Sources: UK Games Fund · Epic MegaGrants · Kickstarter: fees · European Commission: Creative Europe MEDIA · Business Finland. Checked October 20, 2026.

Related: Get a quote · Cost calculator · PC game development

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

To learn game development, pick one engine (Unity, Godot or Unreal), complete one official beginner course from start to finish, and then build a ladder of small games: a classic clone, one polished level, a complete small game with menus and saving, and a game jam entry. Finishing projects teaches more than any number of tutorials. Most beginners can finish a first small game within a few months of regular practice.

Step 1: pick one engine and stay with it

The skills transfer, so the choice matters less than sticking with it. Unity has the largest library of tutorials and is the most common engine in mobile, VR and AR job listings; Godot is light and fully open source; Unreal leads in high-end 3D. Switching engines every few weeks is the most common way beginners stall.

Step 2: learn enough programming

You do not need a computer science degree, but you do need the basics: variables, conditions, loops, functions, and how objects talk to each other. Learn them inside the engine rather than separately, because seeing a character move when your code runs is far more motivating than console exercises.

Step 3: climb the project ladder

Each project should be finished, not abandoned at 80%. Finishing is a skill in itself, and it is the one that employers and clients value most.

Step 4: escape tutorial hell

Tutorial hell is watching tutorial after tutorial without being able to build anything alone. The cure is simple: after each tutorial, change something meaningful on your own, such as a new enemy, a new mechanic or a different level. When you get stuck, read the engine documentation before searching for another video.

Step 5: learn the tools around the engine

• Version control: learn Git early so you never lose work.
• Art basics: enough Blender or a 2D tool to make placeholders; see our guide to game assets.
• Design: how to plan a game on paper; see writing a game design document and level design principles.

What to focus on, by role

A simple weekly plan

• Two or three short sessions: follow the course or build the current project.
• One longer session: build something of your own with what you learned.
• Once a week: show your progress to someone and write down one thing to improve.
• Once a month: finish and publish something, however small.

Consistency beats intensity. An hour most days for six months builds more skill than a few long weekends.

Step 6: join jams and communities

Game jams on itch.io run almost every week, and the Global Game Jam happens every year. They force you to finish under a deadline and put your work in front of players. Engine forums and Discord servers are good places to ask questions once you have tried to solve a problem yourself.

How long it takes

With regular practice, most beginners finish a first small game within a few months. Becoming employable usually takes longer and depends on a portfolio of finished projects. Our guide on starting a game development career covers roles, portfolios and getting hired.

Learning with a mentor

If you want to move faster, live help on your own project removes the guesswork. We offer 1-on-1 game development tutoring in Unity, C#, game design, AR and VR, taught by developers who ship games for clients.

Sources: Unity Learn · Godot docs: your first 2D game · Epic Developer Community: Unreal learning · itch.io: game jams · Global Game Jam. Checked October 20, 2026.

Related: Game development tutoring · Unity development · Careers

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

You can make a game for free with a free engine such as Godot, Unity Personal, Unreal Engine or GameMaker's free tier, free creative tools such as Blender, Krita and Audacity, and free publishing on itch.io or the web. Money only becomes necessary if you publish on Steam ($100 per game), Google Play ($25 once) or the App Store ($99 a year), buy assets, or spend on marketing.

Free game engines

For a first project, pick the engine whose tutorials match the game you want to make. We compare them in Unity vs Godot and Unity pricing in 2026.

Free tools for everything else

Free assets, used safely

Many sites offer free art, sound and music, and Unity's Asset Store and Unreal's marketplace include free items. Before using anything, check the licence. Creative Commons licences differ: some allow commercial use with credit, some forbid commercial use, and some forbid changes. Keep a list of every asset, its source and its licence; stores and publishers may ask for it.

Where you can publish for free

• itch.io: free to upload; you choose what share itch.io takes from sales, with a default of 10%.
• Your own website: web builds from Unity, Godot or GameMaker can run in the browser. Our article on web games covers portals and build size.
• Game jams: free events with deadlines are the fastest way to finish a first game and get feedback.

A zero-budget workflow, step by step

1. Install a free engine and create a Git repository for the project on day one.
2. Prototype the core loop with the engine's built-in shapes; no art yet.
3. Block out levels or screens, then playtest with friends of friends.
4. Make or source art in one consistent style: Blender for 3D, Krita or GIMP for 2D, Inkscape for UI.
5. Record and edit sounds in Audacity, and compose or license music.
6. Build for the web or desktop and publish a free demo on itch.io to collect feedback.
7. Only when the game is close to finished, decide whether paid stores are worth the fees.

Free learning resources

• Unity Learn: free official courses from first steps to programming.
• Godot documentation: step-by-step "first 2D game" and "first 3D game" tutorials.
• Epic Developer Community: free Unreal Engine courses and samples.
• Game jams: deadlines and feedback for free. Our learning roadmap puts these in order.

When paying saves you time

Free is the right default while you learn. Paying starts to make sense when time is the bottleneck: a paid asset pack can replace weeks of modelling, a paid plugin can save building a system from scratch, and a contractor can fill a skill gap such as music or animation. The rule of thumb is to pay for things that are not what makes your game unique, and spend your own time on the parts that are.

The costs that appear later

What "free" costs you instead

Free tools cost time. A solo developer learning engine, art and sound at once should expect a small game to take months. That is fine for learning or a passion project. If you have a commercial idea and a deadline, a studio turns time into money the other way round. Our game development cost guide and cost calculator show what that looks like.

Sources: Unity: pricing and plans · Epic Games: Unreal Engine licensing · Godot: license · GameMaker: pricing FAQ · Blender: licence · itch.io: open revenue sharing · Steamworks: Steam Direct fee · Creative Commons: licence types. Checked October 20, 2026.

Related: 2D game development · Game development cost guide · Cost calculator

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

To make a video game, write the idea in one sentence, cut it down to the smallest version that is still fun, pick an engine such as Unity, Godot or Unreal, and build a rough playable prototype of the core loop before making any final art. Then produce the content, playtest with strangers, fix what they struggle with, and publish on a store such as Steam, itch.io, Google Play or the App Store. Most first games fail because the scope is too big, not because the tools are too hard.

Step 1: the idea, in one sentence

If you cannot describe the game in one sentence, it is not ready to build. "A puzzle game where you fold paper to guide light to a target" works. "An open-world RPG with crafting, multiplayer and a branching story" is five games. Write down the core loop: the action the player repeats most, the reward, and why they want to do it again.

Then cut. Take the feature list and remove everything that is not needed for the core loop to be fun. A first game should be finishable in weeks or a few months, not years.

Step 2: choose an engine

An engine handles rendering, physics, input and building for each platform, so you can focus on the game. The main options in 2026:

There is no wrong answer for a first game. Pick the one with the best tutorials for the genre you want to make. Our comparisons of Unity vs Godot and Unity vs Unreal go deeper.

Step 3: prototype the core loop

Build the core loop with cubes, capsules and placeholder sounds. This is called a grey-box prototype. The question it answers is simple: is this fun yet? If moving, jumping or matching tiles is not enjoyable with grey shapes, final art will not save it. Our prototyping guide shows how to test an idea in two weeks.

Step 4: write a short design document

Once the prototype works, write down what the full game is: the loop, the progression, the number of levels or areas, controls, art style and target platforms. One to five pages is enough for a small game. The point is to decide scope before production, not to write a novel. See how to write a game design document.

Step 5: produce art, audio and content

Now replace placeholders with real assets: characters, environments, UI, music and sound effects. Keep a consistent style that matches your skills or budget; simple, coherent art beats detailed art that clashes. Build levels or content in passes: first all of it roughly, then improve the best parts. Our guide to game assets explains what you need and how each type is made.

Step 6: playtest with people who did not make it

Watch people play without helping them. Where they get stuck, bored or confused is where the game needs work. Developers become blind to their own game within weeks, so outside testers are not optional. Test early and often, not once at the end.

Step 7: polish and fix

Polish is what separates a finished game from a prototype: responsive controls, clear feedback when things happen, menus that work, saving, settings, and performance on the weakest device you support. Read our article on game feel for the small details that make a game feel good. Budget real time for bug fixing; it usually takes longer than expected.

Step 8: publish

Plan marketing before launch, not after: a store page, a trailer and a way for interested players to follow the game. Our guides to publishing on Google Play and indie game marketing cover the details.

How long it takes

A small 2D or puzzle game made by one person part time often takes several months. A polished commercial mobile game built by a studio usually takes two to six months; larger 3D or multiplayer games take a year or more. Our article on how long it takes to make a mobile game breaks this down by genre.

When to bring in a studio

If you have a commercial idea, funding and a deadline, a studio can take you from prototype to store. We build games in Unity for mobile, PC and VR, with fixed quotes and full source-code ownership. See mobile game development or get a free quote.

Sources: Unity: pricing and plans · Epic Games: Unreal Engine licensing · Godot: license · GameMaker: pricing FAQ · Steamworks: Steam Direct fee · Google Play: developer account · Apple Developer Program. Checked October 20, 2026.

Related: Mobile game development · 2D game development · Get a quote

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

To start a game development career, choose one role (programming, design, art, audio, QA or production), learn the core tools for it, and build a portfolio of finished, playable work. Apply with a link people can play or view in a minute, and consider routes beyond big studios: QA, mobile and outsourcing studios, freelancing, indie releases and industries such as AR, VR and simulation. Finished work matters more than certificates.

The main roles

Pick one role to lead with. Generalists exist, mostly in small teams and indie studios, but a portfolio that tries to show everything usually shows nothing well.

Build a portfolio that gets interviews

• Finished beats ambitious: three small, polished, complete pieces beat one unfinished epic.
• Make it instant: a playable web build, a 60-second video or an image gallery that loads in seconds.
• Explain your part: in team projects, state exactly what you did.
• Show process: designers show before-and-after iterations; artists show wireframes and texture maps; programmers link readable code.
• Match the job: applying to a mobile studio? Show something that runs well on a phone.

Where portfolio pieces come from

• Game jams: short, deadline-driven projects on itch.io or the Global Game Jam produce finished games and teamwork experience.
• Small releases: a polished small game on itch.io or a store shows you can ship.
• Open source: contributions to engines such as Godot or to tools show programming skill in a real codebase.
• Mods and remakes: rebuilding a mechanic from a known game shows you can analyse and implement.

Routes into the industry

Engine skills are increasingly useful outside games. Companies building AR shopping, VR training or interactive showrooms hire Unity and Unreal developers too; see our work in VR and AR.

Applying and interviewing

1. Lead your CV and email with a link to your best piece, not a list of courses.
2. Tailor each application to the studio's games and platforms.
3. Expect a test task: a small feature, a design exercise or an art brief. Treat it like a portfolio piece.
4. Prepare to talk through a project: what went wrong, what you changed and what you would do differently.

Do you need a degree or certificates?

Degrees in computer science, art or game development help, especially for programming roles and visas, but studios hire on demonstrated skill. Unity's certifications can be a useful extra signal for Unity roles; they do not replace a portfolio. For broader context on related occupations, the U.S. Bureau of Labor Statistics publishes outlook data for software developers and for special effects artists and animators.

Your first 90 days in a new role

• Learn the pipeline: how builds, version control, bug tracking and reviews work on this team.
• Ship something small early: a bug fix or minor feature that reaches players builds trust fast.
• Ask good questions: show what you tried first, then ask.
• Keep a log: note what you shipped each week; it becomes your next portfolio and review material.

Pitfalls to avoid

• Spreading across too many roles at once.
• A portfolio full of tutorial projects with no original work.
• Long unpaid "exposure" projects with no finished result.
• Waiting to feel "ready" instead of applying and learning from the feedback.

Learning with working developers

Our 1-on-1 tutoring covers Unity, C#, game design, AR and VR, with code reviews on your own portfolio projects. If you are already experienced, see our careers page. For learning paths, read how to learn game development.

Sources: Unity certifications · U.S. BLS: special effects artists and animators · U.S. BLS: software developers · itch.io: game jams · GDC Vault. Checked October 20, 2026.

Related: Careers at A Plus Games Studio · Game development tutoring · Unity development

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

To start a game development studio, decide how it will earn money (your own games, client work, or a mix), register a company, and make every founder and contractor sign an IP assignment from day one. Build a small portfolio of shipped work, price projects by milestones, and avoid depending on one client or one big first game. Many lasting studios fund their own games with client work in the early years.

Choose a business model first

The model decides who you hire, how you sell and what your website says. Many studios that now make their own games started with client projects; our article on co-development explains how that work is structured.

Legal setup and IP

• Register a company: separating the business from your personal finances protects you and makes contracts and payments simpler. The right structure depends on your country; in the US, the Small Business Administration has a guide to business structures.
• IP assignment for everyone: founders, employees and contractors should sign agreements that assign the code, art and designs they create to the company. Missing paperwork is the most common reason studio deals fall apart.
• Founder agreement: ownership split, vesting, roles and what happens if someone leaves.
• Client contracts: scope, milestones, payment terms, change requests and who owns the result on payment.
• Accounting: separate bank account, bookkeeping from the first invoice, and advice on tax incentives in your country.

Tools and costs

The first hires

Founding teams usually cover programming and art between them. Hire for the biggest gap that blocks shipping, which is often a second programmer, a 3D artist or a producer once there is more than one project. Use freelancers for occasional needs such as music, trailers or localisation. Our guide to hiring a Unity developer compares the options.

Finding clients

1. Portfolio: two or three shipped projects, even small ones, matter more than anything else.
2. Website: clear services, prices or ranges, and a fast way to get a quote.
3. Directories and platforms: business directories such as Clutch, and freelance platforms for the first projects.
4. Referrals: every happy client is the cheapest lead source; ask for introductions and reviews.
5. Content: useful articles and talks about what you do well bring inbound enquiries over time.

Funding your own games

Options include self-funding from client work, publisher deals, government grants and investors. Several countries run public funds for games; the UK Games Fund is one example. Each route has trade-offs in control and revenue share; our guide on funding an indie game compares them, and how to pitch to a publisher covers the deck.

Pricing client work

Price by milestones with defined deliverables, not open-ended hours. A milestone plan, for example prototype, vertical slice, content complete and launch, protects both sides: the client sees progress, and the studio is paid as it goes. Always include how change requests are priced.

Mistakes that close studios

• No IP paperwork, so investors or buyers walk away.
• One client making up most of the revenue.
• Underpricing to win work, then losing money on every project.
• Betting everything on a large first game.
• No cash buffer for slow months between projects.

A first-year plan

Specialising helps. A studio known for one thing, such as VR training, hyper-casual prototypes or Unity porting, wins work more easily than one that does everything.

Working with an established studio

New studios often partner with experienced teams for overflow work, porting or technology they do not have yet. We work with studios as a co-development partner and on outsourced projects.

Sources: Unity: pricing and plans · Epic Games: Unreal Engine licensing · UK Games Fund · U.S. SBA: choose a business structure · Clutch: game development companies. Checked October 20, 2026.

Related: Co-development · Outsource game development · About the studio

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

Indie game marketing starts months before launch: a clear hook, an early store page, a gameplay-first trailer, a demo for festivals such as Steam Next Fest, and outreach to press and content creators. On Steam, wishlists matter because Valve notifies wishlisters when the game launches and when it is discounted. Self-publishing keeps revenue and control; a publisher trades a share of revenue for funding, marketing and expertise.

Start with the hook

Before any channel, answer: why would a stranger care? The hook is one sentence and one image that show what is different, for example "a cosy farming game where your crops are tiny monsters". If people cannot repeat it after seeing your capsule art and trailer, marketing will struggle no matter how much you spend.

Build the store page early

Your Steam page is your most important marketing asset. Publish it as soon as you have convincing screenshots and a short trailer, often many months before launch. Valve's documentation explains that players who wishlist your game receive emails when it launches and when it goes on sale, which is why wishlists collected before launch are so valuable. Our guide to Steam wishlists covers how to grow them.

• Capsule art: readable at small sizes, communicates genre at a glance.
• Screenshots: real gameplay, varied, no menus.
• Short description: the hook, not lore.
• Tags: accurate genre and feature tags so Steam shows the game to the right players.

Make a trailer that shows the game

Most viewers decide in the first few seconds. Open with gameplay, not logos or slow story set-up. Keep it short, show the core loop clearly, end with the store link and a call to wishlist. Make a 15–30 second cut for social media.

Use festivals and demos

Steam Next Fest, held several times a year, lets players try demos of upcoming games and is one of the biggest visibility moments for indies. Plan your demo to be polished, short and end on a hook. Online showcases and genre festivals offer more chances. Our Steam Next Fest guide has dates and a checklist.

Press and content creators

• Press kit: a page with description, trailer, screenshots, logos, fact sheet and contact.
• Targeted outreach: write to writers and creators who cover your genre, with a short personal note and a key.
• Creators over press: for many indies, streamers and video creators drive more sales than reviews; key distribution services help track who plays.
• Timing: contact creators a few weeks before launch, and again for big updates.

Social and community

Short gameplay clips on social video platforms, a development diary and a Discord server turn curious players into an audience that tells others. Consistency matters more than volume: one good clip a week beats a burst before launch.

A simple timeline

Self-publishing or a publisher?

Read any deal carefully: recoupment, revenue split, IP ownership, and what happens if the publisher stops supporting the game. Our guides on funding and pitching to publishers go further.

Common indie marketing mistakes

• Announcing too late: a store page two weeks before launch cannot gather enough wishlists.
• Marketing the story instead of the play: players buy what they will do, not the lore.
• A demo that is too long or unpolished: it should end while players still want more.
• Mass emails to press: one personal note to the right writer beats a hundred copies.
• Going silent after launch: updates, events and discounts are when many sales happen.

Mobile is different

On mobile, organic discovery is harder and paid user acquisition plays a bigger role, which makes store optimisation and retention critical. See App Store Optimization for games and soft launching a mobile game.

Measuring what works

Track where wishlists, followers and sales come from. Steamworks' UTM link tracking and its traffic reports show which sources send visitors to your store page, and short links on social posts show which clips work. Double down on the two or three channels that actually move numbers, and drop the rest, rather than spreading effort across everything at once.

Getting help

We build store-ready games, trailers-ready builds and demos, and support launches on Steam and mobile. See PC game development or request a quote.

Sources: Steamworks: wishlists · Steamworks: Steam Next Fest · Steamworks: store page · Steamworks: visibility on Steam · GDC Vault: marketing talks. Checked October 20, 2026.

Related: PC game development · Mobile game development · Get a quote

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

Games for children must follow privacy law and store policies. In the US, the FTC's amended COPPA Rule, in force since 23 June 2025 with most compliance required by 22 April 2026, requires verifiable parental consent before collecting personal information from children under 13 and separate consent before sharing it with third parties such as ad networks. Apple's Kids Category limits third-party analytics and ads and requires parental gates, and Google Play's Families policy allows only certified ad SDKs. In the UK, the ICO's Children's Code sets high privacy by default.

The US: the amended COPPA Rule

COPPA applies to services directed to children under 13 and to services that actually know they collect personal information from children. The FTC published amendments in April 2025; they took effect on 23 June 2025, and most obligations applied from 22 April 2026. Key requirements for game teams:

• Verifiable parental consent before collecting personal information, with limited exceptions.
• Separate consent for third-party disclosure, for example sharing data for targeted advertising.
• Data minimisation and retention: collect only what is needed and keep a written retention policy.
• An information security programme to protect children's data.
• A clear privacy notice describing what is collected and why.

Personal information includes persistent identifiers such as device IDs used for ads, not just names and emails. That is why most kids' games avoid behavioural advertising entirely.

Apple's Kids Category

• Apps in the Kids Category should not include third-party analytics or third-party advertising, except in the limited cases Apple's guidelines allow.
• Links out of the app, purchases and other distractions must be behind a parental gate.
• Content must be appropriate for the age band chosen.

Google Play's Families policy

• Developers declare the target audience; if it includes children, the Families policy applies.
• Ads must come only from ad SDKs that have self-certified for Families, and ads must be appropriate for children.
• Data collection must be limited and disclosed in the Data safety form.
• Teacher Approved highlights high-quality apps for kids in Google Play.

The UK Children's Code

The ICO's Children's Code, also called the Age Appropriate Design Code, applies to online services likely to be accessed by children in the UK. Its standards include acting in the child's best interests, high privacy settings by default, switching off geolocation by default, and avoiding nudge techniques that encourage children to share more data or weaken their privacy.

Monetisation for kids

Design guidelines that also help compliance

• No open chat; if social features are needed, use pre-set phrases and moderated content.
• No collection of names, photos or locations unless essential and consented.
• Large touch targets, simple reading level, audio support for pre-readers.
• Avoid timers and streaks that pressure children to keep playing.
• Provide a parents' area with settings and contact information.

Mixed-audience games

Many games are not made for children but are played by them, such as casual puzzle or creature games. If your audience includes children, the stores may treat the game as mixed-audience, and the rules can still apply to younger players. A common approach is a neutral age screen at the start: players who enter an age under 13 get a version without behavioural ads, open chat or data sharing. The FTC's February 2026 policy statement addresses collecting data solely to verify age, under conditions, so check the current guidance before designing the age check.

Do not ask for a birth date in a way that hints at the "right" answer, and do not let players simply go back and change it. Both undermine the purpose of the screen.

A compliance checklist

1. Decide the target audience honestly, including whether children are likely to play.
2. List every SDK and what data it collects; remove anything not needed.
3. Choose a monetisation model that works without behavioural ads.
4. Implement parental gates and, where required, verifiable parental consent.
5. Write the privacy notice, retention policy and security programme.
6. Complete store declarations: target audience, Data safety, privacy labels and age ratings.
7. Get legal review for each market you launch in.

Educational and kids' games with us

We build educational and children's games with privacy-first SDK choices and parental gates. Our article on educational game costs covers budgets, and the store submission checklist covers review. This article is general information, not legal advice.

Sources: Federal Register: amended COPPA Rule (2025) · FTC: children's privacy · Apple: Kids Category guidelines · Google Play: Families policies · ICO: Children's code. Checked October 20, 2026.

Related: Mobile game development · Unity app development · Get a quote

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

To launch a game as a live service you need a core loop that players return to, proven in a soft launch; a content calendar with events and seasons; remote configuration so you can change balance and events without app updates; a backend for accounts, economy and leaderboards; analytics; community and support; and a team budgeted to keep working for months after launch. Without those, a "live service" is just a game that stops updating.

Is live service right for your game?

Live service works when players have a reason to return every day or week: progression, collection, competition, social play. It struggles when the game is a story you finish once, or when the team cannot sustain updates. Before committing, check two things in a soft launch: whether retention holds up past the first week, and whether players engage with whatever the updates will add. Our soft launch guide explains how to measure that.

The content pipeline

A live game is a production line. Plan a calendar before launch:

Build tools so designers can create events from templates. If every event needs a programmer, the calendar will slip.

Remote configuration

App store updates take time to review and players do not all update at once. Remote configuration services such as Unity Remote Config and Firebase Remote Config let you change values on the server, such as difficulty, prices, rewards and event dates, and roll changes out to some players first. Design the game so most of its numbers live in configuration from day one.

Backend services

• Accounts and cloud save: players expect progress to survive a new phone.
• Economy and inventory: currencies, items and purchases recorded on the server, not just on the device.
• Leaderboards and tournaments: for competition and events.
• Messaging: in-game inbox and push notifications for events and rewards.

Providers such as PlayFab, Unity Gaming Services and Firebase cover much of this; see our comparison of game backends.

Analytics and testing

Every decision in a live game should be measured: retention by cohort, event participation, conversion, revenue per user and where players quit. A/B tests compare versions of offers, difficulty or onboarding on real players. Add crash reporting such as Firebase Crashlytics and performance monitoring, because a crash after an update can wipe out an event's revenue. Our KPIs guide lists the core metrics.

Monetisation that feels fair

• Season or battle passes: a free and a paid track of rewards for playing during a season.
• Cosmetics: skins and decorations that do not change balance.
• Bundles and offers: targeted, time-limited value.
• Rewarded ads: optional ads for rewards in casual games.

Players accept spending in games that keep getting better. They turn on games where updates feel like new ways to charge them. Our article on ads, IAP and hybrid monetisation covers the trade-offs.

Community and support

Live games are run with their players. Plan for a Discord or forum, social channels, clear patch notes, an in-game way to contact support, and someone whose job is to listen and report back to the team. Communicating problems quickly and honestly protects ratings when things go wrong.

Operations: being on call

• Monitoring and alerts for servers, payments and crash rates.
• A plan for who responds to incidents, including weekends and event launches.
• Server capacity for peaks such as event starts and featuring.
• Rollback plans for bad updates and bad configuration changes.

The team after launch

The biggest mistake is spending the whole budget before launch. A live game needs designers, artists, engineers, a community manager and someone to read the data, working continuously. Many studios keep a smaller core team and bring in partners for content or LiveOps; see LiveOps outsourcing.

Why live service launches fail

• Not enough content ready: the first event slips, players leave, and the calendar never recovers.
• Every change needs an app update: without remote config, simple balance fixes take a week to reach players.
• Monetisation before trust: aggressive offers in the first days damage reviews.
• No one owns the community: problems go unanswered and ratings fall.

Launch checklist

• Retention in soft launch justifies ongoing investment.
• At least the first two months of content are planned and partly built.
• Remote config, analytics and crash reporting are live and tested.
• Backend handles accounts, economy and purchases on the server.
• Community channels and support are staffed.
• Budget and team are secured for the months after launch.

Working with us

We build live service features into games from the start and run ongoing updates for clients. See mobile game development or co-development.

Sources: Microsoft PlayFab: live service management · Unity: Remote Config · Firebase: Remote Config · Firebase: Crashlytics · GameAnalytics: post-launch analytics. Checked October 20, 2026.

Related: Mobile game development · Co-development · Get a quote

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

Good level design teaches each mechanic safely before testing it, guides players with light, landmarks and sight lines instead of arrows, alternates tension with rest, and keeps spaces readable with consistent rules. Levels are built as simple grey boxes first, playtested by watching real players, and only then dressed with final art.

1. Teach through the level, not a tutorial

Players learn best by doing. Introduce each new mechanic where failure is cheap, then build on it. Nintendo's Koichi Hayashida described a four-step pattern used in Super Mario 3D Land: introduce a mechanic safely, develop it with a little more challenge, add a twist that changes how it works, and conclude with a final test. The same idea works in almost any genre.

2. Guide without arrows

Players follow light, movement, colour and shapes. Designers use these deliberately:

• Light: brighter areas draw the eye toward the path forward.
• Landmarks: a tall tower or distinctive tree visible from far away gives players a goal and helps them orient.
• Sight lines: framing the next objective through a doorway or between rocks.
• Colour language: one colour for interactive or climbable objects, used the same way everywhere.
• Breadcrumbs: pickups or details leading along the path.

If playtesters keep asking where to go, the level is not communicating; adding a marker treats the symptom, not the cause.

3. Pace tension and rest

Constant action is as tiring as constant calm. Alternate fights or challenges with quieter moments for exploration, story or rewards. A safe room before a boss, a view over the next area after a hard climb, or a shop between levels gives players time to breathe and anticipate what comes next.

4. Make spaces readable

Players should understand at a glance what they can do: where they can walk, climb, hide or not go. Keep affordances consistent, such as cover always waist-high and ledges always marked the same way. Final art must respect this; beautiful detail that hides a path or an enemy is a design bug.

5. Build with metrics

Before building levels, measure the character: jump height and distance, run speed, crouch height, weapon ranges. Then build with those numbers, for example gaps that are always clearly jumpable or clearly not. Metrics prevent near-misses that feel unfair and make levels consistent across designers.

The process

1. Sketch: a top-down map with the critical path, key moments and pacing.
2. Grey-box (blockout): build the whole level with simple shapes using tools such as Unity ProBuilder or Unreal's modelling tools.
3. Playtest: watch players without helping; note where they get lost, bored or stuck.
4. Iterate: move, cut and add until the grey box plays well.
5. Art pass: artists dress the level, keeping gameplay readable.
6. Polish: lighting, sound, effects and a final round of testing.

Changing a grey box takes minutes; changing a finished, lit and decorated level takes days. That is why the blockout phase is where most design decisions should be made.

Common mistakes

• An unclear critical path, so players wander instead of play.
• Large empty spaces with nothing to do.
• Difficulty spikes because a mechanic was tested before it was taught.
• Secrets nobody can find, or secrets that are too obvious to feel rewarding.
• Art that hides gameplay information such as ledges, enemies or exits.

Questions to ask in every playtest

• Where did the player stop and look around for what to do next?
• Which mechanic did they try to use before the level had taught it?
• Where did they die or fail more than twice, and did it feel fair to them?
• Which areas did they skip, and was that intended?
• When did they look bored, and when did they lean in?

Record sessions if you can, and resist explaining. Every explanation you give in a playtest is one players will not get at launch.

Level design in mobile and casual games

Puzzle and casual games rely on level design even more than action games, because hundreds of levels must ramp difficulty smoothly. Teams use the same principles with data: analytics show which levels players fail or quit, and those levels are rebalanced. Our guides to puzzle game costs and mobile game KPIs explain how.

Further reading

The Level Design Book, a free online reference, covers process and principles in depth, and the GDC Vault has many talks by level designers. For how layout shapes feel and story, see our articles on game feel and storytelling.

Sources: The Level Design Book · Game Developer: the structure behind Super Mario 3D Land's levels · Unity: ProBuilder · Unreal Engine: modeling mode · GDC Vault. Checked October 20, 2026.

Related: 3D game development · 2D game development · Unity development

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

To build a multiplayer browser game you need web game programming (JavaScript or TypeScript with a framework such as Phaser or Three.js, or an engine with web export such as Unity), real-time networking (WebSockets or WebRTC), a game server that is the authority on the game state (often Node.js with Colyseus or Socket.IO), and skills in hosting, scaling and security. Turn-based games are much easier than fast real-time action, which also needs prediction and lag compensation.

The client: making the game run in a browser

Web games live or die on load time and file size, so asset compression and small initial downloads matter. Our article on web games in 2026 covers build size rules and portals.

Networking: how browsers talk in real time

Most teams start with WebSockets because they are simple and supported everywhere. WebRTC adds complexity, such as connection negotiation, in exchange for lower latency.

The server: one source of truth

In an authoritative server model, players send their inputs and the server decides what actually happens, then sends the result to everyone. This prevents most cheating, because a modified client cannot simply claim it won. Frameworks help:

• Colyseus: an open-source Node.js framework built for multiplayer games, with rooms, matchmaking and automatic state synchronisation.
• Socket.IO: a widely used real-time messaging library on top of WebSockets; you build the game logic yourself.
• Other stacks: Go, C#, Rust or Elixir servers are common when performance or existing skills favour them.

The hard parts

Latency

Players are at different distances from the server. Real-time games use client-side prediction (move your own character immediately), interpolation (smooth other players' movement between updates) and lag compensation (judge hits from the shooter's point of view). These are the most specialised skills in the list.

Rooms and matchmaking

Grouping players into matches, handling people who leave and rejoin, and filling empty slots all need careful logic.

Accounts and persistence

Logins, saved progress, friends and leaderboards need a database and secure authentication. Our comparison of Firebase, PlayFab and custom backends covers the options.

Scaling and hosting

Servers must run close to players and handle peaks. Containers and cloud hosting with auto-scaling are common; costs grow with concurrent players, so measure early.

Security

Never trust the client: validate every input on the server, rate-limit messages and protect against bots. See anti-cheat for small multiplayer games.

Turn-based versus real-time

A turn-based card or board game only needs the server to validate moves and broadcast results, so a small team can build it quickly. Real-time shooters and racing games need prediction, high update rates and careful server placement. If you are new to multiplayer, start turn-based; our guide to turn-based multiplayer games explains the architecture.

Testing

Test with simulated latency and packet loss from the first prototype, use bots to fill matches, and load-test the server before launch. Bugs that only appear with lag are the most common surprise in multiplayer projects.

A typical small-team setup

On small projects one or two developers cover the client and server roles, but someone should own server operations from the first public test.

Skill checklist

• JavaScript or TypeScript, or C# for Unity Web
• A web game framework or engine
• WebSockets, and WebRTC if you need low latency
• Server programming, usually Node.js
• Prediction, interpolation and lag compensation for real-time games
• Databases, authentication and basic security
• Cloud hosting, monitoring and scaling

Costs to expect

The client is often the cheaper half. Server development, testing under real network conditions and ongoing hosting are where multiplayer budgets grow, and hosting cost rises with concurrent players. Plan a closed test with real players early to measure bandwidth and server load before committing to infrastructure. Our article on multiplayer mobile game costs breaks down where the money goes.

Building one with us

We build multiplayer games for web, mobile and PC, from turn-based to online shooters. Send us your idea for a fixed quote.

Sources: MDN: WebSockets API · MDN: WebRTC API · MDN: WebTransport API · Colyseus documentation · Socket.IO documentation · Phaser. Checked October 20, 2026.

Related: Multiplayer FPS development · 2D game development · Get a quote

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

A playable online prototype of a multiplayer mobile game can start around $2,500, a small launchable MVP around $8,000, and large commercial multiplayer games start at $150,000 and can exceed $1,000,000. On top of development, plan for server and backend costs, which may start around $500 a month at launch and can climb past $20,000 a month if a game goes viral. The biggest cost driver is whether the game is real-time action or turn-based.

Price ranges

The first three rows are our published multiplayer FPS packages; the last is the market range from our game development cost guide. Turn-based and casual multiplayer games usually cost less than shooters at each stage.

What drives the cost

Running costs

Multiplayer games keep costing money after launch:

• Networking service: services such as Photon charge by concurrent users; Photon offers a free 100 CCU commercial plan for Fusion and Quantum games, with paid plans above.
• Dedicated servers: competitive games need servers near players; cost scales with concurrent matches.
• Backend: accounts, saves and economy services are usually priced by usage.
• Operations: monitoring, incident response and updates need people, not just machines.

Our cost guide notes that a simple multiplayer backend may cost around $500 a month at launch, but viral success can push cloud bills past $20,000 a month quickly. Design for scaling and keep an eye on usage-heavy features from the first test. Note too that hosting markets change: Unity ended its own Multiplay server hosting in March 2026, so keep servers portable.

Where the money goes in a typical build

The proportions vary by genre, but the pattern holds: multiplayer adds whole categories of work that a single-player game does not have, and some of them never stop after launch.

Single-player first, multiplayer later?

A common money-saving idea is to launch single-player and add multiplayer if the game succeeds. It rarely saves money. Networked games structure their code, data and game rules around the server from the start, so adding multiplayer later usually means rebuilding core systems. A cheaper route is to make multiplayer part of the first prototype, even with two players and placeholder art, so the architecture is right from day one.

Where budgets go wrong

• Building single-player first and adding multiplayer later, which usually means a rebuild.
• Too many modes and maps before one match is fun.
• No server cost estimate at real player numbers.
• Skipping testing under real network conditions until late.
• No budget for the months after launch.

How to start small

1. Cut the idea to one mode that shows what is different.
2. Build an online prototype with placeholder art and a handful of players.
3. Test with real players on real networks, on mid-range phones.
4. Fund the MVP only when the core match is fun and stable.
5. Soft launch, measure retention and server load, then scale content and infrastructure.

Choosing the tech

The networking stack affects both build and running costs. Our comparison of Photon, Unity Netcode and Mirror and our guide to game backends explain the options; turn-based multiplayer covers the cheaper end.

Timelines

An online prototype typically takes three to five weeks and an MVP eight to twelve weeks in our packages. Full commercial multiplayer games usually take many months to more than a year, plus ongoing live operations.

Get a number for your game

Send us your idea and target platforms for a fixed quote, or try the cost calculator for an instant range.

Sources: Photon: pricing · Firebase: pricing · Unity: Multiplay Hosting status · Microsoft: PlayFab documentation. Checked October 20, 2026.

Related: Multiplayer FPS packages · Game development cost guide · Cost calculator

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

A blockchain game records some items or currency on a public blockchain as tokens or NFTs that players hold in a wallet and can trade, while most gameplay runs off-chain like any other game. Store rules differ sharply: Steam does not allow games that issue or allow exchange of crypto or NFTs, Apple allows NFT sales through in-app purchase but NFT ownership may not unlock features, and Google Play allows tokenized assets with disclosure and strict limits. It makes sense when real ownership and trading are the core value, not as an add-on to monetisation.

How blockchain games work

In well-designed games, only ownership and trading touch the blockchain. Movement, combat and everything that needs to be fast stays on normal servers. Putting too much on-chain makes the game slow and expensive to play.

What the major stores allow

These rules shape design. A mobile game that wants to sell items as NFTs must route sales through the store and cannot use NFTs to unlock gameplay on iOS. Many teams therefore build the trading layer on the web and keep the store app conventional.

Risks to plan for

• Legal: depending on design and country, tokens can raise securities, gambling, consumer protection and tax questions. Get legal advice before launch.
• Security: bugs in smart contracts can be exploited and are hard to fix once deployed; independent audits are standard.
• Player friction: wallets, fees and seed phrases put off mainstream players; embedded wallets reduce this.
• Volatility: item and token prices can swing, which affects player trust and the game economy.
• Reputation: many players are sceptical of NFT games; clear communication about what blockchain adds is essential.

When blockchain makes sense

• Trading and ownership are the core fun, for example collectible card or creature games with real secondary markets.
• Items need to move between games or platforms from different companies.
• The audience already uses wallets and wants on-chain ownership.

It rarely makes sense as a way to add revenue to a game that would work just as well without it. A useful test: describe the game to a player who has never heard of blockchain. If the description still sounds fun without the words "token", "NFT" or "earn", the core is sound and blockchain is a feature. If it does not, the project is a financial product with a game attached, which carries very different risks.

How a project is structured

1. Design the game so it is fun without any blockchain feature.
2. Decide which items or currencies go on-chain and why.
3. Choose a chain based on fees, speed, wallet support and audience.
4. Write and independently audit smart contracts.
5. Build the game client and servers as normal, with on-chain actions only where needed.
6. Plan store compliance per platform, and legal review per market.

Choosing a chain

Alternatives to NFTs

If the goal is giving players a sense of ownership, collection and trading, conventional systems often achieve it with less risk: account-bound collections, in-game marketplaces where trades stay inside the game, and cross-progression between platforms. These work on every store, need no wallet and avoid most of the legal questions. Many studios start this way and add on-chain features only if their players ask for them.

Our approach

We build blockchain features where they serve the game and advise honestly when they do not. See blockchain game development, or read about conventional mobile monetisation for comparison.

Sources: Steamworks: onboarding and content rules · Apple: App Store Review Guidelines (3.1.1, 3.1.5) · Google Play: blockchain-based content · 9to5Google: Google Play blockchain policy (2023) · ethereum.org: smart contracts. Checked October 20, 2026.

Related: Blockchain game development · Mobile game development · Get a quote

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

For new Unity multiplayer games in 2026, Photon Fusion 2 is a strong all-round choice with managed cloud relays and built-in prediction, Photon Quantum 3 suits competitive games that need deterministic simulation, Unity Netcode for GameObjects fits teams that want Unity's own stack with Relay, Lobby and Matchmaker, and Mirror is the leading open-source option when you want to host servers yourself. Avoid starting new projects on Photon PUN 2, which is in maintenance mode, and note that Unity ended its own Multiplay server hosting in March 2026, so plan hosting separately.

What changed in 2026

• Photon: PUN 2 and Bolt are in maintenance mode with no new features; Photon recommends Fusion or Quantum for new projects, and offers a free 100 CCU commercial plan for Fusion and Quantum games.
• Unity: Unity concluded direct support for its Multiplay Game Server Hosting service on 31 March 2026 and licensed the software to Rocket Science Group. Netcode for GameObjects, Relay, Lobby, Matchmaker and Distributed Authority continue, and Matchmaker works with third-party hosting providers.

The options at a glance

Pricing models

Photon charges by concurrent users (CCU): there is a free 20 CCU plan for development and non-commercial use and a free 100 CCU commercial plan for Fusion and Quantum games, one per app, with paid plans above that. Unity's services are usage-based. Mirror and FishNet are free libraries, but you pay for servers and the engineering to run them. Always estimate cost at your expected peak concurrent players, not average daily players, and include dedicated server machines where the model needs them.

Authority: who decides what happened

Competitive games with rankings need dedicated servers or deterministic models; casual co-op often works well with client hosting or shared authority. Our article on anti-cheat explains why authority matters.

Choosing by genre

Hosting after Multiplay

Dedicated servers still need a home. Options include Rocket Science Group for former Multiplay customers, other game server hosting providers, and general cloud platforms with container orchestration. The 2026 changes in this market are a reminder to keep hosting replaceable: build servers as standard Linux containers, keep matchmaking logic separate from the host, and avoid provider-specific features where you can.

Questions to answer before choosing

1. How many players per match, and how many concurrent at peak?
2. Does the game need prediction, lag compensation or determinism?
3. Is it competitive with rankings, or casual co-op?
4. Who will run servers, and what is the monthly budget?
5. Which platforms, and do you need cross-play?
6. What does the team already know?

Prediction and lag compensation

In fast games, waiting for the server before showing a player's own movement feels sluggish. Client-side prediction moves your character immediately and corrects it if the server disagrees; lag compensation lets the server judge a shot from the shooter's point of view. Photon Fusion and Quantum include these as core features. With Netcode for GameObjects or Mirror, they are possible but take more of your own engineering, which is worth budgeting for in a shooter.

Migration warnings

Switching networking libraries mid-project usually means rewriting most networked code. If you are on PUN 2 with a live game, there is no rush to move, but new features and Unity version support will not come. Plan a move when you start a sequel or a major version rather than during live operations.

Our experience

We build Unity multiplayer games with Photon, Netcode and Mirror, from co-op games to multiplayer shooters. Our FPS cost guide and multiplayer mobile cost guide show budgets, or request a quote.

Sources: Photon documentation · Photon: pricing · Unity: Netcode documentation · Unity: Multiplay Hosting status · Mirror documentation · FishNet documentation. Checked October 20, 2026.

Related: Multiplayer FPS development · Unity development · Get a quote

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

A QR code AR campaign prints a code that opens a web page, and the page starts an augmented reality experience in the phone's browser, with no app to install. On Android, browsers can run WebXR AR directly; on iPhone, campaigns use Apple's AR Quick Look, App Clips or web AR tools with their own tracking. The keys to success are a short, impressive experience, codes that scan easily, and hosting that keeps working for as long as the printed material exists.

How it works, step by step

1. A shopper scans the QR code with the phone camera.
2. The code opens a URL, ideally a short link you control.
3. A web page loads the 3D content and asks for camera access.
4. The experience starts: an object appears on a surface, a pack comes to life, or a face effect appears.
5. The page offers a next step: learn more, share, buy or play.

Experience types

The iPhone question

Safari on iPhone does not support WebXR augmented reality. Campaigns handle this in three ways:

• AR Quick Look: Apple's built-in viewer for USDZ models, easily triggered through Google's model-viewer; great for "see it in your space", limited for interactivity.
• App Clips: a small part of a native app that opens from a code without a full install, using ARKit.
• Web AR SDKs: commercial tools that do their own camera tracking in the browser on both platforms.

Decide this early, because it shapes what the experience can do on half or more of your audience. Our ARKit vs ARCore vs WebXR guide explains the platforms.

If your campaign uses 8th Wall

8th Wall, a popular commercial WebAR platform, ends hosted projects on 28 February 2027. Any printed code pointing at an 8th Wall project will stop working unless it is migrated. If your QR codes point to a short link you control, migration is just a matter of changing where it redirects. Our 8th Wall migration guide covers the options.

Print and placement rules

• Size for distance: a code on a billboard must be much larger than one on a pack; test at the real scanning distance.
• Contrast and quiet zone: dark code on a light background with clear space around it.
• Short URLs you control: shorter URLs make simpler, more reliable codes, and a redirect lets you change the destination later.
• Tell people what happens: "Scan to see it on your table" works better than a bare code.
• Test widely: older phones, low light, glossy surfaces and curved packs.

Design for the first five seconds

Most people decide within seconds whether to stay. Load something visible immediately, keep the first interaction obvious, and keep total download size small. A beautiful experience that takes twenty seconds to load on mobile data will be abandoned.

A launch checklist

• The code points to a short URL on a domain you own, with a redirect you can change.
• The experience works on recent and older iPhones and Android phones.
• It loads something visible within a few seconds on mobile data.
• There is a clear fallback for phones that cannot run AR, such as a 3D viewer or video.
• Analytics are live and tested before printing.
• Hosting is paid for the expected life of the printed material.

Hosting for the life of the print

Packaging can stay in kitchens for years, and posters in places long after a campaign ends. Budget hosting for the life of the printed material, or at least redirect the code to a useful page when the campaign closes. Broken codes damage the brand more than no code at all.

Measuring the campaign

Costs

A single WebAR experience or demo fits our AR packages from $999, and a complete AR app from $2,999. Costs grow with the number of 3D assets, interactivity, and whether you need an App Clip or native app for iPhone. See our AR app cost guide.

See examples

Our live browser AR demos include poster, marker and model-viewer examples you can scan today. For shopping use cases, see AR in retail.

Sources: ISO/IEC 18004: QR code specification · Apple: AR Quick Look · Google: model-viewer · Apple: App Clips · Google: ARCore and WebXR. Checked October 20, 2026.

Related: AR development · VR & AR packages · Browser AR demos

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

Saudi Arabia is building a games industry on purpose. Its National Gaming and Esports Strategy, launched in 2022 under Vision 2030, targets about 39,000 jobs and roughly SAR 50 billion of GDP contribution by 2030 through around 86 initiatives, and a dedicated authority was announced in 2023. The Public Investment Fund and Savvy Games Group invest globally, and a PIF-led consortium completed its acquisition of Electronic Arts in August 2026. For studios, the openings are Arabic-first games, branded and public-sector projects, VR and AR, and co-development with a fast-growing local scene.

The national strategy

Investment

The Public Investment Fund and its games company, Savvy Games Group, are among the largest investors in games worldwide. The scale became clear in 2026: a consortium led by PIF, with Silver Lake and Affinity Partners, completed its acquisition of Electronic Arts on 4 August 2026, taking the publisher private. For studios, this investment brings attention, partnerships and funding programmes, as well as competition for talent.

Esports and events

Riyadh hosts the Esports World Cup, one of the largest esports events by prize pool and number of titles. Events like this, together with gaming festivals and conferences in the Kingdom, create demand for branded games, activations, broadcast and fan experiences, as well as networking with publishers and investors.

Ratings and release rules

Games released in Saudi Arabia must be classified by the General Authority for Media Regulation, formerly the General Commission for Audiovisual Media (GCAM), which introduced the country's video game age-rating system in 2016. Applications can come from the developer, publisher or a local agent, in Arabic or English, and distribution through digital stores does not automatically remove the need for classification. Plan this into launch schedules.

Where the opportunities are

Our article on hiring a studio in Saudi Arabia or the UAE covers costs and partner selection, and our Saudi VR page covers immersive work in the Kingdom.

Getting the details right

• Language: build Arabic properly from the start; see Arabic game development.
• Culture: review content with local advisers; use seasonal moments such as Ramadan and national days.
• Payments: support the payment methods players in the region use.
• Devices: test on popular phones in the market, not just flagships.
• Working hours: agree an overlap window; the Saudi working week runs Sunday to Thursday.

How international studios work with Saudi clients

1. A discovery call to agree goals, audience and constraints.
2. A fixed-scope proposal with milestones and Arabic and cultural requirements.
3. Remote production with weekly builds and an agreed overlap on Gulf hours.
4. In-person visits for key workshops, events or launches when needed.
5. Handover with full source code and documentation, often with local teams trained to maintain the product.

Players and platforms

Saudi players are active on mobile, console and PC, and mobile is the broadest channel for reaching mass audiences. Competitive and social genres are popular, and events tied to esports and festivals draw large audiences. For brands and public-sector clients, mobile and web games reach the widest audience, while VR and AR suit venues, exhibitions and tourism experiences where devices can be provided on site.

Building local capability

Many Saudi projects include a goal of building local skills, so international partners are increasingly asked to train local teams, document code thoroughly and hand over products that local developers can maintain. Treat this as part of the scope from the start; it is often a deciding factor in partner selection.

Risks to plan for

• Procurement processes for public-sector and giga-project work can take time.
• Requirements can evolve quickly as programmes scale; milestone contracts with change processes help.
• Classification and cultural review must be scheduled, not assumed.

Working with us

We build games, VR and AR for clients in Saudi Arabia, Arabic-ready and delivered remotely on Gulf hours. See our Saudi Arabia page or the Middle East hub.

Sources: Arab News: Crown Prince unveils National Gaming and Esports Strategy · Saudi Vision 2030 · Silver Lake: EA acquisition completed · Saudipedia: clearance of electronic games · Esports World Cup. Checked October 20, 2026.

Related: Game development for Saudi Arabia · VR development in Saudi Arabia · Middle East & GCC hub

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

A serious game for corporate training is a game whose main purpose is learning or behaviour change, such as practising difficult conversations, safety procedures or sales decisions. Effective ones start from measurable learning outcomes, put learners in realistic decisions with consequences and feedback, and report results to the learning system. Formats range from short mobile mini-games to VR simulations; a focused proof of concept can start around $999 and a complete training app around $2,999.

Serious games versus gamification

Both have a place; many programmes use gamification to motivate and serious games to build skills. Our article on gamified apps covers the second approach.

Formats

Designing for learning

1. Start with outcomes: what should people do differently after the training?
2. Find the decisions: list the real choices people face on the job and the common mistakes.
3. Build scenarios: put learners in those decisions with realistic consequences.
4. Give feedback: explain why a choice worked or failed, immediately or in a debrief.
5. Keep it short: sessions of minutes, not hours, with reasons to replay.
6. Test with real employees: if they find it unrealistic, they will not learn from it.

Common design mistakes

• A quiz with a game skin, which teaches nothing new.
• Unrealistic scenarios that experienced staff dismiss.
• Mechanics that reward speed or luck instead of good decisions.
• No debrief, so lessons are not connected to the job.
• Too long to fit into a working day.

Measuring results

The decisions learners make inside a serious game are rich data: they show exactly which situations people struggle with, which often reveals gaps in processes as well as training.

Examples by department

Running a pilot

Start with one department and one skill. Run the game with a pilot group alongside existing training, measure completion, scores and manager-observed behaviour, and interview participants. A four-to-eight-week pilot usually shows whether the format works for your culture before you invest in a full programme.

Involve the people who will deliver the training too. Trainers and managers who understand the game can run debriefs, connect scenarios to real cases on the team, and spot when content needs updating, which is what turns a one-off novelty into lasting practice.

Integrating with your learning system

Corporate learning teams usually need completions and scores in their learning management system. SCORM is the long-established standard for packaging courses; xAPI records more detailed learning activity and works with games, VR and mobile apps. Agree which your system supports before development starts.

Accessibility and devices

Workforces include people with different abilities, devices and connections. Follow accessibility guidance such as the W3C's WCAG for web-based training, support keyboard and screen readers where possible, offer subtitles, and test on the devices employees actually use, including older laptops and phones.

What the evidence suggests

Results depend on design quality. In one widely cited example, PwC's 2019 pilot found VR soft skills training faster than classroom learning and associated with higher learner confidence, though content cost more up front. The common thread in successful programmes is realistic practice with feedback, not the technology itself. Our article on VR training ROI discusses building a business case.

Costs

A focused proof of concept fits our VR and AR packages from $999, and a complete training app from $2,999. Multi-scenario platforms, multiplayer exercises and integrations are quoted individually. For non-XR formats, see our game cost guide and educational game costs.

Working with us

We build serious games and simulations in Unity for web, mobile, PC and VR, with your subject experts setting the content. See Unity app development or VR training for manufacturing.

Sources: PwC: VR soft skills training study · xAPI overview · ADL: SCORM · W3C: WCAG accessibility guidelines. Checked October 20, 2026.

Related: Unity app development · VR & AR packages · VR development

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

Valve rates every tested game Verified, Playable, Unsupported or Unknown on Steam Deck. To be Verified, a game needs full controller support with correct button icons, an on-screen keyboard when text is needed, support for the Deck's default resolution with legible text, no launchers or warnings that break the flow, and full compatibility with Proton, including middleware and anti-cheat. Most games that land on Playable miss on text size, mouse-only menus or launchers, all of which are fixable.

The four ratings

The four criteria

Input

• Full controller support: every part of the game, including menus and settings, works without mouse or keyboard.
• Correct glyphs: button prompts match the Deck's controls, not keyboard keys or another console's buttons.
• On-screen keyboard: when the game asks for text, the keyboard appears automatically.

Display

• Supports the default resolution of 1280×800 or 1280×720.
• Text is legible at the Deck's screen size.
• Default graphics settings give a good experience without tweaking.

Seamlessness

• No compatibility warnings when the game starts.
• Any launcher or account screen can be navigated with the controller.

System support

• The game runs under Proton, Valve's compatibility layer, or ships a working native build.
• Middleware and anti-cheat are supported under Proton.

Common reasons games miss Verified

Engine notes for Unity and Unreal

Both engines run well on Steam Deck through Proton, and many teams ship Windows builds only. In Unity, the Input System package handles controllers, but glyphs and UI focus navigation need deliberate work; the Steamworks SDK exposes the on-screen keyboard and Steam Input. In Unreal, the Common UI plugin helps build controller-friendly menus with focus handling and input-aware prompts. In both, test middleware such as video players, launchers and anti-cheat early, because they are the usual source of Proton problems.

Designing UI for a 7-inch screen

• Increase base text size and test at arm's length, not on a monitor.
• Avoid dense tables and tiny icons; add a text scaling option.
• Make focus states obvious so players always know which button is selected.
• Keep important information away from screen edges.
• Support both 16:10 (1280×800) and 16:9 layouts without cropping.

Using Steam Input

Steam Input lets players remap controls and lets developers support many controllers through one API, including correct glyphs per device. Games that already support Xbox-style controllers often work on Deck with little extra work, but glyphs and menu navigation still need checking.

Performance targets

Steam Deck is a portable PC with limited power and battery. Players generally prefer stable performance over maximum detail. Detecting the Deck and applying a dedicated preset, with a sensible frame-rate cap and lower-cost effects, makes a big difference to both experience and battery life. Our article on frame rate and player experience explains why stability matters most.

Testing

1. Play through the whole game on a Deck, or on a similar setup with a controller only and 1280×800 resolution.
2. Check every menu, settings screen and text field with the controller.
3. Check text legibility at arm's length.
4. Test suspend and resume, a common handheld behaviour.
5. Check offline behaviour if the game has online features.

Online and account features

Games that require an account or online connection need extra care on a handheld. Sign-in screens must work with the controller and on-screen keyboard, the game should handle sleep and wake without losing its connection, and it should explain clearly when it is offline. Players often play on the move, so graceful offline behaviour is part of a good Deck experience.

After fixing issues

Ratings are not permanent. Once you have fixed problems, Valve's Steamworks documentation explains how to request a new compatibility review. Mention Deck improvements in your update notes; Deck owners pay attention.

Why it matters

The badge appears on your store page and in the Deck's own store, and Deck owners often filter for Verified games. A Playable rating is not a disaster, but Verified removes doubt at the moment of purchase. It also signals polish to the wider PC audience.

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

A Steam wishlist is a player saying "tell me about this game". Valve emails wishlisters when the game launches and when it is discounted, so the number of wishlists at launch strongly shapes release-week sales and visibility. Grow wishlists by publishing the store page early, using a strong capsule and gameplay-first trailer, joining Steam Next Fest and other events, working with content creators, and posting regular updates. Track sources with Steamworks reports and UTM links.

How wishlists work

• Players can wishlist upcoming and released games from the store page.
• Valve emails wishlisters when a game launches and when it goes on sale.
• Steamworks reports show wishlist additions, deletions and purchases, including by country.
• Wishlists are a private signal to you; players see only their own lists.

Because launch and discount emails go to everyone on the list, a game with many wishlists starts with built-in demand on its most important days.

Why they matter for visibility

Strong sales and engagement in the first days help Steam show a game to more players through its recommendations and lists. Wishlists convert into those early sales. Valve's visibility documentation explains how the store promotes games based on player interest and activity, which is why a strong first week is so valuable.

The store page comes first

Publish the page as soon as you have convincing visuals. Every month the page is live is a month of wishlists.

Ways to grow wishlists

Measure what works

Steamworks supports UTM link tracking, so you can tag links from each social post, creator or newsletter and see which sources bring traffic to your store page. Combine that with the wishlist reports to see which activities actually add wishlists, then put more effort into those.

A wishlist timeline

Growth is rarely smooth. Most games see spikes around announcements, festivals and creator videos, with quieter weeks in between, which is why regular activity matters more than one big moment.

Common mistakes

• Publishing the store page only weeks before launch.
• Capsule art that is unreadable when small.
• Trailers that open with logos and story instead of gameplay.
• Inaccurate tags that show the game to the wrong players.
• Marketing posts without a clear link and call to wishlist.

At launch

1. Set a launch date and keep it; moving it repeatedly erodes interest.
2. Prepare a launch discount if it fits your pricing plan.
3. Have creators and press coverage ready for launch day.
4. Be active in the community and fix issues quickly.
5. Plan the first update and event so momentum continues.

After launch: wishlists keep working

Wishlists do not stop mattering at launch. Players who did not buy on day one stay on the list, and Valve emails them when the game is discounted. That makes seasonal sales and your own discount events a second launch for many games. Pair discounts with updates or new content so returning visitors find a reason to buy, and keep adding wishlists by releasing updates, joining themed festivals and shipping to new platforms such as Steam Deck.

Wishlists and publishers

Publishers and investors often ask for wishlist numbers because they are evidence of demand. Our guide to pitching to publishers explains how to present them, and indie marketing and publishing covers the wider plan.

Building a game that earns wishlists

We build demos and store-ready builds for Steam, including Steam Deck support. See PC game development or request a quote.

Sources: Steamworks: wishlists · Steamworks: visibility on Steam · Steamworks: Steam Next Fest · Steamworks: store page · Steamworks: UTM analytics. Checked October 20, 2026.

Related: PC game development · Get a quote · Co-development

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

A turn-based multiplayer game sends each player's move to a server, which checks it against the rules, saves it and tells the other players. Choose synchronous play (both players online with turn timers) or asynchronous play (players move whenever they like and get a notification), then build on a backend such as Nakama, Firebase, PlayFab or Apple Game Center. It is the easiest kind of online game to build, because there is no need for lag compensation, but leagues, notifications and fair play still need careful design.

Synchronous or asynchronous?

Many mobile games support both: quick live matches for engaged players and async games for everyone else.

The architecture

1. The client shows the board and lets the player choose a move.
2. The client sends the move, not the resulting state, to the server.
3. The server checks the move is legal and that it is this player's turn.
4. The server stores the move and updates the game state.
5. The server notifies the opponent, by live message or push notification.

Storing the game as an ordered list of moves, rather than only the latest state, makes replays, spectating and dispute checks simple, and makes bugs easier to reproduce.

Backend options

Note that Google Play Games Services ended its turn-based and real-time multiplayer APIs on 31 March 2020, so Android and cross-platform games need one of the other options. Our comparison of Firebase, PlayFab and custom backends goes deeper.

Matchmaking and ratings

Players want fair opponents. Rating systems in the Elo or Glicko family adjust a skill number after each match and pair players with similar ratings. At launch, when few players are online, widen the search range over time so nobody waits too long, and consider bots for the very first matches.

Leagues and seasons

Leagues give players goals beyond single matches. A common structure:

• Divisions: groups of players with similar ratings, such as Bronze to Diamond.
• Seasons: fixed periods, often a few weeks, after which standings reset partly.
• Promotion and relegation: the top players move up, the bottom move down.
• Rewards: cosmetic or currency rewards by final position, which gives a reason to come back.

Leagues need scheduled server jobs to close seasons, calculate standings and grant rewards reliably, so plan them as part of the backend, not as an afterthought.

Timers, forfeits and reconnects

• Set a turn timer, even in async games, so abandoned matches end and the remaining player gets a result.
• Let disconnected players rejoin a synchronous match within a grace period.
• Decide what happens when a player quits: forfeit, bot takeover or a draw.

Fair play

Turn-based games are easier to protect than real-time ones, but still never trust the client. Validate every move on the server, never send information a player should not see (such as the opponent's hand in a card game), and rate-limit requests. Our article on anti-cheat for small games covers the basics.

Design tips

• Keep turns short so async games fit into spare moments.
• Show clearly whose turn it is in every game the player has running.
• Let players play several matches at once in async modes.
• Add lightweight social features such as rematches and friend invites.
• Notifications should be useful, not spammy, and respect system settings.

What it costs and how long it takes

A simple turn-based game with accounts, matchmaking and notifications is one of the most affordable multiplayer projects, because there is no real-time networking to tune. Leagues, chat, economies and cross-platform play add scope. Our guide to multiplayer mobile game costs gives a breakdown, and our browser multiplayer guide covers web versions.

Building one with us

We build turn-based and real-time multiplayer games in Unity for mobile, web and PC, with backend, matchmaking and leagues. See mobile game development or request a quote.

Sources: Heroic Labs: Nakama documentation · Apple: GKTurnBasedMatch · Google Play: multiplayer APIs ended · Firebase: Cloud Functions · Microsoft: PlayFab documentation. Checked October 20, 2026.

Related: Mobile game development · Multiplayer development · Get a quote

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

The UK Video Games Expenditure Credit (VGEC) gives companies a credit of 34% of qualifying expenditure on developing a game that is certified as British through the BFI's cultural test. It replaced Video Games Tax Relief for new games from 1 April 2025, and the old relief ends in April 2027. Relief applies to spending on goods and services used or consumed in the UK, so development done abroad generally does not count. Rules are detailed, so get professional advice before relying on a claim.

Key facts

Who can claim

The credit is claimed by the company responsible for designing, producing and testing the game, through its corporation tax return. The game must be intended for supply to the public and certified as British by the BFI, which assesses cultural content, where work takes place and who works on it. Core expenditure means costs of designing, producing and testing the game, not concept work before development or maintenance after release.

What it means for outsourcing

This is the part UK studios most often ask us about. Because relief is tied to goods and services used or consumed in the UK, development work done by teams outside the UK generally does not count toward the credit. That changes the maths of outsourcing:

• Work inside the claim done abroad loses the credit, so its effective cost is compared with the UK cost minus the credit.
• Work outside the claim still makes sense to outsource: pre-production prototypes, post-launch LiveOps, ports and games that would not qualify for certification anyway.
• Capacity is often the deciding factor: when a UK team cannot hire fast enough, a partner may still be the only way to hit a launch date.

A useful exercise is to split the project into work streams, mark which are inside the claim, and compare the true cost of each option. Our article on in-house vs outsourcing costs gives a framework.

Other UK support

Beyond the credit, the UK Games Fund supports early-stage developers with grants and programmes, and TIGA, the UK games trade association, publishes guidance and advocacy on tax and funding. Our guide to funding an indie game covers grants and publishers.

Practical steps for a claim

1. Check the game can pass the BFI cultural test early, before production starts.
2. Track core expenditure by category and by where it is incurred.
3. Keep contracts showing where subcontracted work is done and at what price.
4. Apply for interim and final British certification through the BFI.
5. Claim through the company tax return with professional support.

A worked example (illustrative)

Imagine a UK studio planning a game where most production happens in the UK, plus three extra pieces of work: an early prototype to pitch to a publisher, a later port to another platform, and live operations for a year after launch. The prototype is pre-production concept work, the port may fall after the game's release, and live operations are post-release maintenance, so all three may sit outside the core expenditure of the claim. Those are natural candidates for a partner, while the main production stays in the UK and keeps its credit. An adviser can confirm exactly where the lines fall for a specific project.

Common misunderstandings

• The credit is not a grant paid up front; it is claimed through the tax return.
• Not every cost counts: pre-production concept work and post-release maintenance are usually outside core expenditure.
• Certification is about more than language or setting; where and by whom work is done also matters.
• Rules changed in 2024 and 2025, so older guides about VGTR and EEA spending can mislead.

How we work with UK studios

We work with UK studios and publishers on prototypes, ports, LiveOps, art and full builds that sit outside or alongside tax-credit claims, and we are happy to plan a split that keeps qualifying work in the UK. See our UK page or co-development services. This article is general information, not tax advice.

Sources: HMRC: Creative Industries Expenditure Credit manual · BFI: about UK creative industry expenditure credits · HM Treasury: response on audio-visual tax reliefs · TIGA: UK games trade association · UK Games Fund. Checked October 20, 2026.

Related: Game development for the UK · Co-development · Outsource game development

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

Unreal Engine 5 is realistic for mobile in 2026 for visually ambitious mid-core and core games, teams that already know Unreal, and projects shared with PC and console. It renders phones through a dedicated mobile path, so desktop showcase features such as Lumen and Nanite are aimed at higher-end hardware rather than typical phones. Plan for scalability tiers, app size, Android target API rules and a narrower choice of monetisation SDKs than Unity; for casual and hyper-casual games, Unity remains the more common choice.

How Unreal renders on phones

Unreal's mobile rendering path uses simplified, performance-oriented versions of many desktop features, with forward and deferred mobile shading options. Epic also documents using the desktop renderer on high-end mobile devices, but most games that need to reach mid-range and older phones build around the mobile path and scale up for powerful devices.

What to expect from UE5 features on mobile

Device targets and scalability

Define low, mid and high device tiers from your market data, and build scalability settings that change resolution, shadows, effects and draw distance per tier. Test on real devices in each tier from the first prototype; thermal throttling on phones can halve performance after a few minutes of play, which simulators do not show.

App size

Unreal builds tend to be larger than equivalent Unity builds, and app stores limit download sizes. On Android, Play Asset Delivery lets you split content into packs downloaded at install, after install or on demand. On iOS, on-demand resources serve a similar purpose. Plan content packaging early; app size affects install conversion.

Android target API rules

Google Play requires new apps and app updates to target Android 16 (API level 36) from 31 August 2026, with extensions available to 1 November 2026. Epic's guidance for Unreal Engine 5.7 recommended target SDK 35, so check that your engine version and toolchain can build for the level Google Play requires before planning a release. See our store submission checklist.

Monetisation and services

Fewer ad networks and analytics providers publish official Unreal SDKs than Unity ones. AppLovin publishes an official MAX plugin for Unreal, Unreal's online subsystems handle in-app purchases, and other services can be integrated natively. Our article on monetising an Unreal mobile game covers the options.

Performance habits that matter on phones

• Profile on device: use Unreal's profiling tools on real phones; editor numbers mislead.
• Control draw calls: merge static meshes, share materials and use instancing.
• Keep materials simple: fewer texture samples and instructions per material.
• Watch post-processing: bloom, depth of field and similar effects cost more on mobile GPUs.
• Budget memory: texture streaming and compression settings per device tier.
• Mind heat: cap frame rate where it makes sense to keep devices cool over long sessions.

iOS considerations

On iPhone and iPad, Unreal uses Metal. Recent devices are powerful, but memory limits still apply and the system closes apps that use too much. Test on the oldest iPhone you plan to support, keep an eye on memory spikes during level loads, and plan downloadable content through on-demand resources when app size grows.

Team skills

Unreal mobile work needs people who understand both the engine and mobile constraints. Blueprints speed up gameplay iteration, but performance-critical systems usually move to C++. If your team already ships Unreal on PC or console, mobile is a smaller step; if the team is new to Unreal, the learning curve adds months.

When Unreal is the right choice

• Mid-core and core games where visual quality is a key selling point, such as shooters and action games.
• Teams with Unreal experience or existing Unreal code and assets.
• Games planned for mobile, PC and console from one codebase.
• Projects using Unreal-specific tools such as MetaHuman or Blueprints-heavy workflows.

When Unity is usually better

• Casual, hyper-casual and puzzle games where app size and SDK breadth matter most.
• Games targeting many low-end Android devices.
• Teams relying heavily on ad mediation and third-party analytics.

Our Unity vs Unreal for mobile comparison goes deeper.

A practical checklist

1. Pick device tiers and the minimum device before production.
2. Prototype the core loop on the minimum device, not in the editor.
3. Decide lighting and geometry approaches without relying on Lumen and Nanite for typical phones.
4. Plan content packaging for app size limits.
5. Confirm engine support for current Android and iOS requirements.
6. Choose monetisation and analytics SDKs with maintained Unreal support.

Working with us

We help teams choose between Unity and Unreal for mobile and build in both. See mobile game development or request a quote.

Sources: Unreal Engine: mobile performance and optimisation · Unreal Engine: desktop renderer on mobile · Unreal Engine 5.7 release notes · Google Play: target API level requirements · Android: Play Asset Delivery · AppLovin: MAX Unreal plugin. Checked October 20, 2026.

Related: Mobile game development · Unity game development · Get a quote

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

Unreal Engine supports in-app purchases on Android and iOS through its online subsystems for Google Play and iOS, so standard purchases need no third-party SDK. For ads, the main options are AppLovin's official MAX plugin for Unreal (for Unreal Engine 5.2 and later), Epic's documented AdMob support on Android, community plugins on Fab, or integrating native ad SDKs yourself. Plan consent and Apple's tracking prompt from the start, and test purchases with store test accounts.

Why monetisation is different in Unreal

Most mobile ad networks and analytics tools ship a Unity SDK first. Unreal has a smaller selection of maintained plugins, so the stack needs choosing deliberately, and sometimes native integration work. Teams that pick Unreal for mobile usually do so for visual quality or existing Unreal skills; see our Unreal Engine 5 on mobile and Unity vs Unreal articles.

In-app purchases

1. Enable the online subsystem for each platform (Google Play on Android, iOS on Apple devices) in the project configuration.
2. Create products in Google Play Console and App Store Connect, noting each product ID and whether it is consumable.
3. Use Unreal's purchase nodes or C++ interfaces to query products, make purchases and handle the success and failure results.
4. Implement restoring non-consumable purchases, which stores expect.
5. For valuable items, validate receipts on your server rather than trusting the device.

Purchases do not work in plain development builds; upload builds to Google Play test tracks with licence testers, and use sandbox accounts on iOS.

Also plan the store side: prices per country, tax handling by the stores, refund behaviour, and what happens to a consumable if the app closes mid-purchase. Unfinished transactions should be completed the next time the game starts, so players never pay without receiving their item. Since US court rulings now allow links to outside payments on both stores, some games also add a web shop; see the future of mobile gaming.

Ads: the options

Mediation lets several ad networks compete for each impression, which usually raises revenue; our guide to ad mediation explains bidding and waterfalls.

Consent and tracking

• EEA and UK: personalised ads need user consent through a consent management platform; Google's User Messaging Platform supports the IAB Transparency and Consent Framework.
• iOS: tracking users across other companies' apps requires the App Tracking Transparency prompt; add SKAdNetwork identifiers for your ad networks in the project settings.
• Children: games for kids have stricter ad rules; see our kids game rules guide.

Which ad formats to use

Common pitfalls

• Plugins lagging behind ad SDK updates, causing store warnings or crashes; check update history before choosing.
• Initialising an SDK twice when mediation already initialises its adapters.
• Forgetting purchase restore or receipt validation.
• Testing ads in production with real ads, which can get the ad account banned; use test ads and test devices.
• No analytics on ad impressions and revenue, so placements cannot be tuned.

A typical Unreal mobile monetisation stack

Lock the stack early and build a small test map that exercises every purchase and ad placement. Running that map on real devices before each release catches most integration problems before players do.

Analytics for monetisation

Track impressions, revenue per placement, purchase funnels and the effect of ads on retention. ARPDAU and LTV, explained in our mobile game KPIs guide, tell you whether a change actually helped.

Getting help

We integrate monetisation in Unity and Unreal mobile games, including mediation, purchases and consent. See mobile game development or request a quote.

Sources: Unreal Engine: Android guides · Unreal Engine: in-app purchases on Android · AppLovin: MAX Unreal plugin · Google: User Messaging Platform · Apple: App Tracking Transparency. Checked October 20, 2026.

Related: Mobile game development · Unity development · Get a quote

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

Video game music is composed as loops, short stingers and layered stems rather than finished songs, so it can repeat without audible joins and change with what the player is doing. Developers implement it with the engine's audio tools or middleware such as FMOD and Wwise, which switch sections, fade layers in and out and duck the music under dialogue and effects. The composer and the audio implementer decide together how the music should react before a note is written.

How game music differs from film music

A film score follows a fixed edit. A game has no fixed timeline: a player might spend thirty seconds or thirty minutes in an area, win or lose a fight at any moment, and pause whenever they like. Music therefore has to:

• Loop cleanly, with no audible gap or click at the loop point.
• Transition gracefully between states, such as exploring and fighting.
• Stay out of the way of sound effects and dialogue, which carry gameplay information.
• Not become tiring after the hundredth repetition, which shapes melody and arrangement choices.

The building blocks

Adaptive music: two main techniques

Vertical layering

The composer writes one piece as several stems that sound good alone and together. The game adds layers as intensity rises, for example percussion when enemies appear and brass when the boss arrives, and removes them as things calm down. Because all stems share tempo and key, changes feel natural.

Horizontal resequencing

The music is split into sections, and the game jumps between them at musical boundaries such as the next bar or beat, often through a short transition. This suits bigger mood changes, like moving from a town theme to a battle theme.

Most games combine both: resequencing for big state changes, layering for intensity within a state.

Implementation: engine audio or middleware

Middleware lets the composer and sound designer build the music behaviour themselves, with programmers only sending a few parameters such as "intensity" or "in combat". Both FMOD and Wwise offer free or low-cost licences for smaller projects; check their current terms for your budget.

Mixing and loudness

Music sits underneath the mix. Sound effects tell players what is happening, and dialogue carries the story, so music usually ducks when they play. For overall loudness, the Sony Audio Standards Working Group recommends about -24 LUFS integrated for console and PC games and about -18 LUFS for mobile, where players often listen through small speakers in noisy places. Always give players separate volume sliders for music, effects and voice.

How composers work on a game

1. Read the design document and play the prototype to understand the tone and pace.
2. Write a short main theme and get it approved before producing the rest.
3. Agree the adaptive plan with the developer: which states exist and how the music reacts.
4. Compose cues as loops and stems, with marked loop points and tempo.
5. Deliver files in the agreed format, usually high-quality WAV stems, plus versions for the trailer.
6. Test in the build and revise; music that works alone may clash with effects in game.

Briefing and hiring a composer

A good brief includes: genre and references (three or four tracks you like and why), the list of cues with rough lengths, which ones must adapt, platform, delivery format, deadline and budget. Be clear about rights. A buyout transfers the music to you; a licence lets you use it while the composer keeps ownership, often with the right to sell the soundtrack. Either is fine if it is written down.

Making game music yourself

If you are learning, free tools are enough to start: LMMS for composing, Audacity for editing, and the free tiers of FMOD or Wwise to practise adaptive music. Begin with one exploration loop and one stinger, put them in a prototype, and play for ten minutes. If the loop annoys you by then, it will annoy players too. Our guide on making a game for free lists other free tools.

Audio in our projects

We plan music and sound from the prototype stage, implement adaptive audio in Unity, and work with composers and sound designers on original scores. See Unity game development or request a quote.

Sources: FMOD Studio · Audiokinetic: Wwise overview · Unity: Audio Mixer · Unreal Engine: MetaSounds · Audiokinetic: loudness measurement · LMMS. Checked October 20, 2026.

Related: Unity game development · Mobile game development · Get a quote

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

The storytelling techniques that work best in games use the player's actions: mechanics that express the theme, environments that imply what happened, choices with visible consequences, and story beats placed between gameplay instead of interrupting it. Tools such as Ink, Yarn Spinner and Twine make branching dialogue manageable, and branch-and-bottleneck structures keep the amount of content under control.

Why game stories are different

In a film, the director controls where you look and when. In a game, the player does. That is the medium's biggest strength, because players feel what happens to them more strongly than what they watch, and its biggest challenge, because they can ignore, skip or break the story at any moment. Good game writing works with that freedom rather than against it.

1. Let the mechanics tell the story

The strongest stories in games come from what the player does. A survival game about scarcity makes you ration food; a game about protecting someone makes you slow down to keep them safe. If the theme is in the verbs, cutscenes only need to frame it. Ask early: what does the player do, and how does that express what the story is about?

2. Environmental storytelling

Places can tell stories without a single line of dialogue: a barricaded door, a table set for a dinner that never happened, a trail of footprints. Harvey Smith and Matthias Worch's GDC 2010 talk "What Happened Here?" describes this as letting players piece together events from what they see. It respects players who want to explore and costs nothing to those who do not.

• Use objects that imply a sequence of events, not just decoration.
• Reward curiosity with small details in corners players have to choose to visit.
• Keep it consistent: every room should belong to the same world and history.

3. Meaningful choices

A choice is meaningful when the player understands what they are choosing and sees a consequence. It does not need to change the ending; a character remembering what you said, or a door that stays closed, is enough. Choices that look important but change nothing teach players to stop caring.

4. Structure that stays in scope

Every branch multiplies writing, voice recording, testing and translation. Branch-and-bottleneck structures, where paths reconverge and choices are remembered as variables, give players agency without doubling the work.

5. Dialogue tools

These tools let writers work in text files that live in version control, while programmers connect them to the game's UI and logic.

6. Pacing

Place story where it does not block play: after a challenge, during travel, at the start of a level. Keep cutscenes short and skippable. Alternate tension and rest, the same way level designers do; see our guide to level design principles.

7. Write for players who skip

Many players skip text. Make sure the essential information survives: objectives in the UI, key facts repeated in a second form, and short lines. Players who want depth can find it in optional dialogue, logs and environments.

8. Write for translation

If the game will be localised, avoid building sentences from fragments in code, leave room for longer languages in the UI, and give translators context for every line. It saves money and mistakes later; see our guide to game localisation.

A quick narrative checklist

Story in small and mobile games

You do not need a novel. A memorable main character, a short scene between chapters, and progress that reveals a little more of the world can make a casual game feel personal. Many successful mobile games use light story to give meaning to progression rather than to deliver plot.

How we approach narrative

We plan story alongside mechanics, prototype branches in text before building them, and implement dialogue systems in Unity. See Unity game development or request a quote.

Sources: GDC Vault: What Happened Here? Environmental storytelling · inkle: Ink scripting language · Yarn Spinner · Twine · GDC Vault. Checked October 20, 2026.

Related: Unity game development · 3D game development · Get a quote

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

VR is used in healthcare training for surgical rehearsal, emergency scenarios, clinical skills, communication training and patient education. Published evidence is strongest for procedural training: a 2020 randomized trial found 75–78% of VR-trained participants completed a tibial nailing procedure versus 25% with a technique guide alone, and a 2021 systematic review found improved procedural times, task completion and accuracy. Studies are often small and varied, so projects should define measurable outcomes and pilot against current training.

Where VR is used

What published studies found

A randomized trial in orthopaedic surgery

Orland and colleagues, in Clinical Orthopaedics and Related Research (2020), randomly assigned participants to learn tibial intramedullary nailing with a technique guide, with VR, or with VR plus the guide. Only 2 of 8 (25%) in the guide-only group completed the procedure, compared with 6 of 8 (75%) in the VR group and 7 of 9 (78%) in the VR-plus-guide group. The sample was small, but the difference was significant.

A systematic review of surgical VR

Mao and colleagues reviewed studies of immersive VR for surgical skills in the Journal of Surgical Research (2021). They reported that high-quality, though heterogeneous, studies showed improved procedural times, task completion and accuracy, positive user ratings and cost-effectiveness.

Beyond healthcare

In corporate training, PwC's 2019 pilot found VR learners trained faster and felt more confident applying what they learned, though content cost more up front. That study was about soft skills, not clinical skills, so treat it as context rather than proof for medical use.

Limits of the evidence

• Small samples: many trials involve tens of participants, not hundreds.
• Heterogeneity: different procedures, devices and measures make results hard to combine.
• Transfer: fewer studies measure performance on real patients or patient outcomes.
• Novelty: enthusiasm for new technology can inflate short-term results.

None of this means VR does not work; it means each programme should measure its own results.

Regulation and privacy

Training and education apps are generally not regulated as medical devices, because they are not used to diagnose or treat patients. The FDA does review AR and VR products that are medical devices, so if a project moves toward diagnosis, treatment or patient-specific planning, check the regulatory position early. Training apps must still respect hospital IT security and privacy rules, especially if they use real patient data or recordings.

Designing a healthcare VR project

1. Involve clinical educators from day one to define the learning outcomes.
2. Choose a procedure or scenario with a clear, measurable skill.
3. Script steps, decision points and common errors with subject experts.
4. Build guided, practice and assessment modes.
5. Pilot against current training and measure the agreed outcomes.
6. Plan hygiene, device management and content updates.

Choosing what to measure

Agree the measures with clinical educators before building, and collect a baseline from current training so results can be compared fairly. Even a small, well-measured pilot is more persuasive to a hospital than a large rollout with no data.

VR, mannequins or both?

VR does not replace physical simulation. Mannequin-based simulation remains essential for hands-on skills such as compressions or airway management, where touch and force matter. VR adds value where scenarios are expensive to stage, rare, or hard to repeat consistently: unusual complications, mass-casualty events, or rehearsing a procedure's sequence many times before a supervised session. Many programmes use VR for preparation and repetition, then physical simulation and supervised practice for hands-on skill.

Practical considerations in hospitals

• Hygiene: wipeable face covers and cleaning routines between users.
• Time: short modules that fit around shifts.
• Space: a safe area for standing scenarios.
• Support: someone on site who can start sessions and fix problems.

Costs

A focused proof of concept, such as one procedure or one scenario, fits our VR packages from $999, and a complete training app starts around $2,999. Multi-scenario platforms, multiplayer team training and integrations are quoted individually. See our VR cost guide for what drives budgets.

Working with us

We build VR training in Unity with clinical educators setting the content and outcomes. See VR development and our article on VR training ROI.

Sources: Orland et al. 2020, Clinical Orthopaedics and Related Research (PMC) · Mao et al. 2021, Journal of Surgical Research · FDA: AR and VR medical devices · PwC: VR soft skills training study. Checked October 20, 2026.

Related: VR development · VR & AR packages · Unity app development

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

Manufacturers use VR to train assembly steps, safety procedures such as lockout/tagout, equipment operation, maintenance and emergency drills, especially where real practice is expensive, dangerous or disruptive to production. Evidence such as PwC's 2019 enterprise pilot found VR learners trained four times faster than classroom learners and felt 275% more confident applying what they learned. A focused proof of concept can start around $999, a complete VR training app around $2,999, and multi-scenario platforms are quoted individually.

Use cases that work

What the evidence says

The most widely cited enterprise study is PwC's 2019 pilot of VR soft skills training for new managers. It found VR learners completed training four times faster than in a classroom and 1.5 times faster than e-learning, and reported being 275% more confident to act on what they learned. PwC also noted that VR content required more up-front investment, so it became more cost-effective at scale. Results for hands-on industrial skills vary by task, which is why a measured pilot matters. Our article on enterprise VR training ROI explains how to build a business case finance teams accept.

How a training scenario is built

1. Choose the procedure: high-risk, high-cost or high-volume training gives the clearest return.
2. Capture the steps: work with experienced operators to write the exact sequence and common mistakes.
3. Build the environment: import equipment from CAD where available, simplified for real-time performance.
4. Script interactions: grab, turn, press and inspect, with feedback on errors.
5. Add modes: guided learning, practice and assessment.
6. Record results: scores, time and errors, optionally sent to a learning management system.
7. Test with trainees: refine until new users can complete it without help.

Hardware and device management

Most industrial VR training now runs on standalone headsets, which need no PC or cables. Planning device management early matters: Meta stopped selling commercial Quest SKUs and closed Horizon Managed Services in February 2026, so organisations need another way to enrol, update and lock down headsets. Our article on the end of Quest for Business covers the options. Also plan hygiene, charging, storage and who runs sessions on the shop floor.

Connecting to existing training systems

Training departments want results in the same place as other courses. VR apps can report completions and scores through standards such as xAPI, or export results for a learning management system. Even without integration, simple reports per trainee and per step show where people struggle and where the real procedure or instructions may need improving.

Costs

These are our published VR and AR packages. The biggest cost drivers are the number of procedures, how detailed the equipment must be, and whether usable CAD data exists. Our VR cost guide breaks this down further.

Keeping content current

Equipment, layouts and procedures change. Build scenarios so that steps, text and parts lists live in data files rather than code, and agree who on the client side approves changes. A small yearly update budget keeps training accurate; outdated VR training teaches the wrong thing convincingly.

Rollout plan

1. Pick one high-value procedure and define success, such as time to competence or error rate.
2. Build a pilot and run it with a group alongside current training.
3. Compare results and gather trainer and trainee feedback.
4. Decide whether to scale, and to which procedures next.
5. Plan devices, support and content updates for the long term.

Pitfalls

• Recreating a slide deck in VR instead of practising real actions.
• Too much visual detail for standalone headsets, causing low frame rates and discomfort.
• No plan for updating content when equipment or procedures change.
• Treating VR as a replacement for all hands-on training rather than preparation for it.

Working with us

We build VR training simulations in Unity for standalone headsets and PC VR, from single procedures to multi-scenario platforms. See VR development or start with a proof of concept.

Sources: PwC: VR soft skills training study · OSHA: control of hazardous energy (lockout/tagout) · xAPI overview · Unity: XR development. Checked October 20, 2026.

Related: VR development · VR & AR packages · Unity app development

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

WebXR is the browser standard for VR and AR: people open an experience from a link or QR code with no app to install. In 2026 it works well on Meta Quest's browser for VR and passthrough, on Chrome for Android for AR on ARCore phones, and for VR in Safari on Apple Vision Pro. Safari on iPhone still does not support WebXR AR, so iPhone users need fallbacks such as AR Quick Look or a native app. Choose WebXR for reach and speed to launch; choose native apps when accuracy or iPhone AR matters most.

Where WebXR works

Our article on ARKit vs ARCore vs WebXR explains why the iPhone gap decides many AR projects, and how our AR furniture demo works on iPhone shows a real example.

Frameworks

The iPhone fallback

For product visualisation, a practical pattern is model-viewer: Android users get WebXR or Scene Viewer, and iPhone users get Apple's AR Quick Look with a USDZ version of the model. It is not full WebXR, since interactions are limited, but it covers "see it in your room" for most shoppers. For richer iPhone AR, an App Clip or a full app built with ARKit or Unity AR Foundation is needed.

8th Wall and migrations

8th Wall, a commercial WebAR platform that worked around some browser gaps, ends hosted projects on 28 February 2027. Teams with live campaigns or printed QR codes should plan a migration; our 8th Wall migration guide covers the options.

Good uses for WebXR

• Campaigns and packaging: scan a QR code, see the experience in seconds.
• Product viewers: furniture, appliances and products in the customer's room.
• Events and exhibitions: no install queues.
• VR demos and training previews: share a link to a Quest headset.
• Prototypes: test an idea before investing in a native app.

Performance tips for WebXR

• Compress models: glTF with mesh compression and compressed textures can cut download size dramatically.
• Load progressively: show something useful in a second or two, then stream the rest.
• Keep draw calls low: merge static objects and share materials, especially for mobile AR.
• Target the device: standalone headsets and phones need lighter scenes than desktop browsers.
• Test on real hardware: desktop emulators hide most performance problems.

A typical WebAR campaign, step by step

1. Define the moment: what the customer should see in five seconds after scanning.
2. Prepare 3D assets at real-world scale and compress them for the web.
3. Build the experience with a WebXR framework, plus model-viewer or AR Quick Look for iPhone.
4. Generate QR codes and short links, and track scans and sessions with analytics.
5. Test on a range of Android phones and iPhones before printing anything.
6. Plan hosting for the length of the campaign and beyond, so printed codes keep working.

Limits to plan around

• Performance is lower than native apps; keep models light and scenes simple.
• Fewer platform features, such as advanced tracking and some sensors.
• iPhone AR is missing, as above.
• Download size matters: every second of loading loses visitors.

Measuring results

Because WebXR runs in a browser, normal web analytics work: track scans, page loads, how many visitors start the AR or VR session, how long they stay, and what they do next, such as visiting a product page. These numbers make WebXR campaigns easy to compare with other marketing.

Web or app?

Costs

A focused WebAR or WebXR experience fits our VR and AR packages, starting at $999 for a single-scene experience or WebAR demo and $2,999 for a complete app. Our AR app cost guide breaks down budgets further.

Working with us

We build WebXR experiences, product viewers and native AR apps, and help teams choose between them. Try our live browser AR demos or see AR development.

Sources: W3C Immersive Web: WebXR Device API · MDN: WebXR Device API · Google: ARCore and WebXR · Road to VR: visionOS 2 enables WebXR · Google: model-viewer · three.js. Checked October 20, 2026.

Related: AR development · VR & AR packages · Browser AR demos

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

Game feel is the moment-to-moment sensation of controlling a game: how quickly the character responds, how impacts land, and how the game reacts to every input. Developers create it with low input delay, forgiving controls, tuned movement curves, animation, camera effects, hit-stop, sound and haptics. It is why one platformer feels tight and another feels floaty even when the rules are the same.

Where the term comes from

Designer Steve Swink's book Game Feel (2008) describes it as the combination of real-time control (your input changes the game immediately), simulated space (objects move and collide in a believable world) and polish (effects that reinforce what is happening). In 2012, Martin Jonasson and Petri Purho's GDC talk "Juice it or lose it" showed how adding feedback to a plain Breakout clone transforms it, and "juice" became shorthand for that layer of polish.

The building blocks

Responsive input

Delay between pressing a button and seeing a reaction is the fastest way to ruin feel. Read input every frame, avoid unnecessary smoothing on controls, and keep the frame rate stable. Our article on frame rate and player experience explains why consistent frame pacing matters more than a high average.

Forgiving controls

Good platformers quietly help the player. Coyote time lets you jump for a fraction of a second after walking off a ledge. Input buffering remembers a jump pressed just before landing. Players never notice these, but they notice when they are missing.

Movement curves

How fast a character accelerates, stops and falls defines its weight. Many games make the fall faster than the rise so jumps feel snappy rather than floaty. These values are tuned by hand through playtesting, not calculated once.

Animation

Classic animation principles apply: anticipation before an action, squash and stretch on impact, follow-through after. A two-frame wind-up before a sword swing makes it feel heavier without slowing the game down.

Making impacts land

On phones, Apple's Core Haptics and Android's haptics APIs allow precise, short vibrations rather than a generic buzz. Used on the right moments, such as a successful match or a landed hit, they add a lot.

Camera

A camera that follows the player too rigidly feels mechanical; one that lags too much feels drunk. Small look-ahead in the direction of movement, gentle smoothing and occasional zoom on big moments all shape how the game feels without the player noticing the camera at all.

How to tune game feel

1. Start with the core action and make it feel good with grey boxes before adding content.
2. Expose the key values (speed, gravity, shake strength) so designers can tweak them while playing.
3. Change one thing at a time and play it, ideally with someone who has not played before.
4. Add effects gradually, then remove anything that hurts readability.
5. Add accessibility options to reduce shake, flashes and vibration, as recommended by the Game Accessibility Guidelines.

Game feel by genre

Common game feel mistakes

• Adding juice before the controls work: effects cannot fix a slow or imprecise character.
• Too much of everything: constant shake and flashes make it hard to read what is happening.
• Hiding latency with animation: long wind-ups feel cinematic in a trailer and sluggish in your hands.
• Tuning on one device only: what feels right at 120 frames per second may feel different at 30.
• Ignoring sound: many impacts that look fine feel weak because the audio is thin.

Game feel in commercial games

In mobile and casual games, feel often decides whether players return after the first session: a satisfying tap, merge or match is the core reward. In shooters, it is recoil, hit markers and sound. We spend dedicated time on feel in every project, from hyper-casual games to multiplayer shooters.

Sources: Steve Swink: Game Feel · GDC Vault: Juice it or lose it · Apple: Core Haptics · Android: haptics · Game Accessibility Guidelines. Checked October 20, 2026.

Related: Hyper-casual games · Multiplayer FPS development · Unity development

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

ASO for games means two jobs: being found in store search and browse, and converting the people who land on your page. On the App Store, search ranking comes mainly from the 30-character name, 30-character subtitle and a hidden 100-byte keyword field; on Google Play, from the 30-character title, 80-character short description and the 4,000-character full description. Conversion comes from the icon, screenshots and video, which both stores now let you test and tailor with custom pages. Treat ASO as ongoing work, updated with every content release, not a one-time setup.

Text: what each store reads

On the App Store, do not repeat words across the name, subtitle and keyword field; separate keywords with commas. On Google Play, write a natural description that uses the phrases players search for. Google's guidance warns against repeating keywords, listing unrelated terms, emojis in titles and claims such as "#1" or "best".

Pick keywords players actually use: genre terms ("merge puzzle", "idle tycoon"), mechanics, themes and the names players use for similar games, without using other games' trademarks in your metadata.

Visuals: where installs are won

• Icon: readable at small size, one strong idea, distinct from competitors in search results.
• First screenshots: most visitors never scroll. Show real gameplay and the core fantasy in the first two or three, with short captions.
• Preview video: real gameplay in the first seconds. Store and advertising rules expect ads and store assets to reflect the actual game.
• Portrait or landscape to match how the game is played.

Test and tailor: the 2026 toolkit

App Store

• Product page optimisation tests up to three alternative versions of your icon, screenshots and previews against the original, for up to 90 days.
• Custom product pages: up to 70 extra versions of your page, each with its own screenshots, promotional text and previews. They can be assigned keywords so they appear in matching searches, linked from ads, and given deep links on iOS 18 and later. Apple reports that developers see higher conversion on average when sending people to a custom product page.

Google Play

• Store listing experiments test up to two variants of your icon, feature graphic, screenshots and descriptions against the current listing.
• Custom store listings: up to 50 versions targeted by country, search keywords, unique URLs, Google Ads campaigns or user states such as pre-registration.

Use these together with paid campaigns: a custom page per audience or creative theme lets an ad's promise continue onto the store page. Our guide to playable ads covers the ad side.

Events and updates keep the page fresh

Apple's in-app events appear on your product page, in search and in editorial selections. You can publish up to 10 at a time, each lasting up to 31 days and promoted up to 14 days before it starts, with an event name of up to 30 characters. Google Play's promotional content in Play Console serves a similar purpose for events, offers and major updates. Games with regular LiveOps should plan store events alongside in-game events.

Ratings, reviews and localisation

• Ratings affect both conversion and ranking. Ask at happy moments, such as after a win, using the stores' official in-app review prompts, and never offer rewards for ratings, which store rules prohibit.
• Reply to reviews, especially about bugs, and say when they are fixed.
• Localise metadata and screenshots for your biggest markets, not just the game text; each language is a separate search audience.

An ASO routine

1. Research keywords for your genre and pick a primary phrase per market.
2. Write store text to the limits above.
3. Design the icon and first three screenshots, then test them.
4. Create custom pages for your main audiences and campaigns.
5. Plan store events with each content update.
6. Review search terms, conversion and reviews monthly, and iterate.

ASO works best alongside a good launch plan; see our soft launch guide and how to publish on Google Play. Our mobile game development service includes App Store Optimization in the Launch package.

Sources: Apple: custom product pages · Apple: product page optimisation · Apple: in-app events · Google Play: store listing best practices · Google Play: store listing experiments · Google Play: custom store listings. Checked October 14, 2026.

Related: Mobile game development · Publishing on Google Play · Soft launch guide

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

To prototype a game in two weeks, write down the one question the prototype must answer, test the idea on paper, build only the core mechanic in a greybox with placeholder shapes, fake everything else, playtest with real people in small rounds, and end with a written decision: kill, pivot or continue. Two weeks is enough because a prototype is not a small game. It is an experiment, and the code is meant to be thrown away.

Prototype, vertical slice or MVP?

Developer and educator Rami Ismail draws the line clearly: prototypes help you decide whether you should make a game, while a vertical slice shows whether you can. He recommends prototypes be fast, cheap and precise, limited to specific questions and treated as disposable.

Days 1–2: write the question, then play it on paper

Write one sentence: "This prototype will tell us whether ___." Good questions are specific: "Is swiping to build a bridge satisfying for two minutes?" or "Do players understand the merge rule without a tutorial?" Add what result counts as a pass. Then try the core rule with paper, cards or a whiteboard. Dan Cook has described making Triple Town's first prototypes on paper and whiteboards before a rough digital version. Paper finds broken rules in an afternoon.

Days 3–8: greybox the core mechanic

Build only what the question needs. Unity Learn describes greyboxing as blocking out a scene with primitive grey shapes so you can build movement, triggers and interactions before final art. Practical tools:

• Primitives and ProBuilder for levels and objects.
• Unity's free Starter Assets for ready-made first- and third-person controllers, including mobile touch controls.
• Free or AI-generated placeholders where a shape is not enough. If anything AI-made ships later, Steam asks developers to disclose AI-generated content.

The Experimental Gameplay Project at Carnegie Mellon, where students made games in under seven days, put it simply: fake it liberally and build the toy first. Skip menus, saving, settings and polish. Game designer Jesper Juul proposed a two-week version: week one for mechanics and controls, week two for tuning and progression. That is the rhythm here.

Days 9–12: playtest and tune

Put it in front of people who have not seen it. Do not explain; watch. Nielsen Norman Group's research on usability testing found that about five users uncover most usability problems, and recommends several small rounds over one big one. That is guidance for finding problems, not proof that a game is fun or will sell, but it fits prototyping well: test with about five people, fix, test again.

What to record:

• Did they understand the goal without help, and how long did it take?
• Where did they get stuck or bored?
• Did they want another go without being asked?
• What did they say the game was, in their own words?

To reach testers on devices: Apple's TestFlight supports up to 10,000 external testers, Google Play has internal and closed testing tracks, and Steam Playtest lets PC players request access without affecting the main game's reviews.

Days 13–14: decide

• Kill if the core is not fun after honest tuning. Cheap now, expensive later.
• Pivot if one part sparked interest; write the next question around it.
• Continue if it passed. Write a short design document (our GDD guide shows how) and plan the MVP or a market test.

For mobile ideas aimed at broad audiences, the next test is often marketability: short ads or playable ads to see what installs cost. Our hybrid-casual production guide covers that path.

Mistakes that waste the two weeks

• Asking several questions at once, so no answer is clear.
• Polishing art, which makes testers comment on visuals instead of play.
• Explaining the game to testers, which hides exactly what you need to learn.
• Keeping prototype code for production. Rebuild properly once the idea is proven.

If you want it built for you

We build prototypes to answer specific questions, typically in one to three weeks. Hyper-casual prototypes commonly cost $1,000 to $4,000, our multiplayer FPS prototype starts from $2,499, and our current Spark package starts from $999. See hyper-casual prototyping or our packages. AI tools can speed up placeholders too; our look at AI game generators explains where they help.

Sources: Rami Ismail: prototypes and vertical slices · Game Developer: prototype a game in under 7 days · Jesper Juul: the two-week variant · Unity Learn: greyboxing · Nielsen Norman Group: test with 5 users · Apple: TestFlight · Steamworks: Steam Playtest · Raph Koster blog: Daniel Cook on Triple Town prototypes. Checked October 14, 2026.

Related: Hyper-casual prototyping · Packages and quote · Game design document guide

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

A full-time Unity developer in the US costs roughly $135,000 a year in salary at the national median for software developers, and about $170,000 or more in the first year once benefits, payroll taxes, a Unity Pro seat and recruiting are added. Freelancers on marketplaces typically charge $15 to $75 an hour, agencies $25 to $99 an hour, and studios often quote a fixed price per project. The cheapest-looking option is rarely the cheapest way to a finished game, because one developer cannot also be your artist, tester, producer and release manager.

Option 1: hire in-house

The US Bureau of Labor Statistics has no separate "Unity developer" category; game programmers fall under software developers. Their median annual wage was $135,980 in May 2025, with the lowest 10% under $82,460 and the highest 10% above $214,670. Location matters: the California median was $174,410 and the Sacramento metro median $139,640.

Salary is not the cost. BLS data for June 2026 shows benefits make up about 31.5% of total compensation for professional occupations in private industry. Our own rough calculation from those figures puts a $135,980 salary at about $166,700 in employer cost. Add a Unity Pro seat at $2,310 a year and recruiting, and the first year passes $170,000 before hardware, other software, onboarding time and management.

In-house wins when you have years of continuous work, need someone in every meeting and want knowledge to stay in the company. It loses when the work is one project, or when you need several skills for a few months each.

Option 2: hire a freelancer

Both marketplaces say these are typical ranges from their own data, and actual rates are negotiated. Upwork also charges clients a marketplace fee: 5% on its Basic plan, plus a small contract initiation fee. Freelancers are a good fit for well-defined tasks: a feature, a port, a bug-fixing sprint, an SDK integration. They are a harder fit for a whole game, because you become the producer: you write the specification, review the code, find the artist, organise testing and handle store submission.

Before you hire, know the employment rules. In California, the ABC test presumes a worker is an employee unless the hiring business proves otherwise, and the IRS looks at behavioural and financial control. Get advice if a "freelancer" will work full time, on your schedule, for months.

Option 3: hire an agency or studio

Clutch's pricing guide, based on verified client reviews, lists Unity development at $25 to $49 an hour for most firms, with US firms averaging $50 to $99 an hour. Rates matter less than the model. A studio brings the roles a game needs, such as programming, art, design, QA and project management, and many quote a fixed price for a defined scope, which moves the risk of overruns to them.

For reference, typical 2026 market ranges for complete games run from $5,000 to $30,000 for hyper-casual and simple 2D games up to $150,000 to $500,000 or more for multiplayer and live-service titles, according to our game development cost guide. Our own current launch pricing starts at $999 for a focused game (Spark) and $2,999 for a full-featured mobile game (Launch).

The costs people forget

• Art and animation. A programmer with placeholder cubes is not a game. Budget for 2D or 3D art separately if your hire does not include it.
• QA. Testing on real devices, typically $2,000 to $5,000 for a simple 2D game and $10,000 to $20,000 or more for complex 3D, according to our cost guide.
• Store accounts and compliance. Apple charges $99 a year and Google Play $25 once. Both now set minimum SDK and target API requirements that must be met for every update.
• Production time. Someone has to plan, prioritise and review. If that is you, count your hours.
• Maintenance. Engine updates, OS changes and SDK updates continue after launch.

How to check Unity skills before you hire

1. Shipped titles. Ask for store links to games they worked on and what exactly they built. Download them.
2. A paid test task. A small, real task from your project, paid. Upwork lists requests for free work as a red flag, and good developers decline unpaid tests.
3. A code review. Have an experienced Unity developer read their code: structure, naming, performance habits, use of version control. Unity's free C# style guide is a useful checklist.
4. Platform experience. Mobile, PC, VR and WebGL each have their own pitfalls. Ask about the platform you need.
5. Certifications as a bonus, not proof. Unity offers User, Associate and Professional certifications, valid for three years. They show study, not shipped games.

Make sure you own the result

• Written IP assignment. Under US copyright law, a transfer of ownership must be in a signed written document. Contractor work is not automatically yours.
• Asset Store licences. Unity says assets bought by a contractor belong to the contractor's organisation. If you need the project files, you need your own licences for paid assets, or the contractor works inside your Unity organisation.
• Your own store accounts. Publish under your company's Apple and Google developer accounts from day one, so the game, reviews and players stay with you.
• Source code and build access. Insist on a shared repository you control, not a zip at the end.

Our in-house vs outsourcing comparison goes deeper into the full numbers, and the outsourcing guide covers contracts and engagement models.

Where we fit

We are a full team rather than a single developer: Unity engineers, artists, QA and a dedicated project manager, with 100% source-code ownership and an NDA on every project. You can hire us for a whole game, as a dedicated team or staff augmentation, or to work inside your codebase. See Unity game development for the services.

Sources: BLS: Software developers pay · BLS: Employer Costs for Employee Compensation · Upwork: Unity developer rates · Upwork: client fees · Fiverr: Unity developer cost guide · Clutch: software development pricing · Unity: Asset Store licences for client projects · 17 U.S.C. 204. Checked October 14, 2026.

Related: Outsource game development · Unity game development · In-house vs outsourcing

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

A hybrid-casual game moves through stage gates: a prototype, an install-cost test, a retention test, a meta layer and economy, monetisation, then a soft launch. A first playable build can start from $999 on our current launch pricing, a full release with meta and in-app purchases typically sits in the $30,000 to $80,000 market range, and the whole journey from concept to global launch can take a year or more once soft-launch iteration is included. Each gate exists so you only spend the next budget when the data earns it. For how the market got here, read our hyper-casual vs hybrid-casual overview; this post is about producing one.

Why stage gates

Sensor Tower's State of Gaming 2026, as summarised by GameDev Reports, describes hybrid-casual as the only mobile segment with meaningful in-app purchase growth in 2025, at about 20%. Competition followed. Publishers respond by testing many ideas cheaply and investing only in the few that pass: Voodoo says it tests around a thousand prototypes a year and fully launches only a handful. You do not need that volume, but you need the same discipline.

The stages

Team figures are typical ranges. Voodoo has said its games usually launch with about six people and can grow to about 20 as features are added. Unity's publishing team, Supersonic, has put hybrid-casual development at around 12 to 18 months from concept to launch; most of that is iteration in stages 3 to 6, not the first build.

Stage by stage

1. Prototype

One mechanic, no menus, placeholder art, built to answer one question. Our prototyping guide covers how. Hyper-casual-style prototypes commonly cost $1,000 to $4,000.

2. Marketability

Make short video ads or playable ads and run small campaigns to measure cost per install. SayGames argues that early install cost can mislead for hybrid games, because their appeal grows with depth, so treat it as a signal, not a verdict.

3. Retention

Add enough content to measure day-one and day-seven retention on fresh players. GameAnalytics calls the popular 40/20/10 retention rule a reference point, not a fixed threshold, because genres differ. Compare against the genre and your own previous tests.

4. Meta layer and economy

This is what makes it hybrid: progression, upgrades, collections or base building around the short core loop, and an economy of soft and hard currency. It is the stage where most budget goes and where game design experience matters most.

5. Monetisation

Sensor Tower notes hybrid-casual has split into ads-first and IAP-first models, with IAP-first titles often earning significantly more, while ads provide a revenue floor. Decide early which engine drives growth, because it shapes the economy. See ads vs in-app purchases.

6. Soft launch

Release in a few countries, fix stability first, then improve retention, then monetisation. Our soft launch guide explains markets, metrics and timing.

What it costs

Remember the costs outside development: user acquisition for tests and soft launch, analytics tools and the store fees. Our cost guide lists the hidden costs.

The mistakes that burn budgets

• Building the meta before proving the core. No progression system saves a mechanic people do not enjoy.
• Treating benchmark numbers as pass marks. Old hyper-casual targets do not fit games designed for depth.
• Skipping analytics until soft launch. Instrument from the first test build; see mobile game KPIs.
• No kill criteria. Decide in advance what result ends or pivots the project.

We build hybrid-casual games stage by stage, quoting each stage separately so you never commit the full budget up front. See hyper-casual and hybrid-casual development.

Sources: Unity: the shift from hyper to hybrid-casual · Voodoo: hybrid-casual pipeline · SayGames: hybrid publishing model · GameDev Reports: Sensor Tower State of Gaming 2026 · Sensor Tower: ads-first vs IAP-first · GameAnalytics: how to think about retention. Checked October 14, 2026.

Related: Hyper-casual and hybrid-casual · Hyper-casual vs hybrid-casual · Mobile game development

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

A first idle game can start from $999 on our current launch pricing, and typical 2026 market ranges are $5,000 to $30,000 for a simple 2D clicker, $30,000 to $80,000 for a casual 3D tycoon and $80,000 to $150,000 for a full 3D tycoon with deep monetisation. Unlike puzzle games, where levels drive the cost, idle and tycoon budgets go mostly into the economy: the maths behind costs, production, prestige and offline earnings, and the time it takes to tune them before and after launch.

Why idle games are harder than they look

Kongregate's Anthony Pecorella described idle games as a seesaw between production rates and costs. In his widely cited "Math of Idle Games" series, costs typically grow exponentially with each purchase, while production grows linearly or polynomially, so players hit walls that upgrades and multipliers push back. His worked example from AdVenture Capitalist uses a cost growth rate of 1.07 per lemonade stand. Small changes to numbers like that reshape hours of play, which is why the economy, not the art, is the expensive part.

The systems you are paying for

Generators, upgrades and multipliers

The core: things that produce currency, things that make them produce faster, and the cost curves that pace it all. Teams model these in spreadsheets or simulation tools first, so one parameter change updates every cost.

Prestige

A reset that wipes progress in exchange for a permanent bonus, so the next run goes faster. Games calculate the reward differently, for example from lifetime earnings or earnings since the last reset. Prestige is what turns a few days of play into months, and it needs the most balancing.

Offline progress

Players expect to earn while away. That means saving a timestamp when the app pauses (Unity's OnApplicationPause is the usual hook), calculating earnings on return, protecting against clock changes, and deciding on a cap. Designs vary: Pecorella noted that, at the time, Egg, Inc. capped offline earnings at two hours while Clicker Heroes had no limit.

Very big numbers

Idle numbers outgrow normal data types. A C# double tops out around 1.8 × 10³⁰⁸, and many idle games pass that. Libraries such as BreakInfinity.cs provide a number type for values far beyond it, trading some precision for speed. Formatting those numbers readably on screen is its own small design job.

The tycoon layer

Tycoon games add a visible world: managers, upgradable buildings, areas to unlock and often 3D scenes. That adds art, animation and performance work on top of the economy. Our Animal Shelter: 3D Safari Zoo case study, a Unity management sim with a build-and-upgrade loop and a balanced soft economy, shows the kind of scope involved.

Monetisation built into the economy

Idle games are well suited to rewarded ads because players constantly want more income. Unity's monetisation guidance gives the classic example of a home-screen video that doubles income for a few hours, with developers capping how much boost can stack. Returning players are often offered an ad to double what they earned offline. These must be opt-in: AdMob's policy requires a clear choice, a disclosed reward and no penalty for skipping.

In-app purchases usually sell permanent multipliers, managers, time skips and premium currency. Apple's guidelines require in-game currency to be sold through in-app purchase and say purchased currency may not expire. Our guide to ads vs in-app purchases covers the balance.

Tuning after launch

No spreadsheet survives real players. Plan to retune costs, rewards and ad placements using live data. Firebase Remote Config changes values without an app update and supports A/B tests, and analytics should track where players stall, when they prestige and when they quit. Budget for several tuning rounds in the first months.

Realistic budgets

Starting prices are our current launch packages; the market ranges come from our game development cost guide.

How to start

Model the economy before building anything, prototype the first 30 minutes of play, and test whether people return the next day. Then expand the world and the prestige layers. We build idle and tycoon games in Unity; see mobile game development, or compare budgets with our puzzle game cost guide.

Sources: Game Developer: The Math of Idle Games, Part I · Game Developer: The Math of Idle Games, Part III · Microsoft: C# floating-point types · BreakInfinity.cs · Unity: rewarded video monetisation · AdMob: rewarded ads policy · Firebase Remote Config. Checked October 14, 2026.

Related: Mobile game development · Game cost guide · Ads vs IAP

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

The mobile game KPIs that matter most are retention (do players come back on day 1, 7 and 30), monetisation per user (ARPDAU and LTV), and acquisition efficiency (CPI and ROAS). A game is commercially healthy when the lifetime value of a player comfortably exceeds the cost of acquiring one. Everything else, from session length to payer conversion, helps explain why those numbers move.

The formulas

Retention comes first

Retention is measured in cohorts: everyone who installed on a given day is followed over time. Mixing cohorts, such as comparing today's actives with yesterday's installs, produces numbers that look better than reality. Day-one retention mostly reflects the first session and tutorial; day seven reflects whether there is a reason to return; day 30 reflects depth and long-term goals.

For context, GameAnalytics' 2026 benchmarks, covering more than 16,000 mobile games with at least 1,000 monthly users in 2025, report:

The same report put median daily playtime at about 12 minutes. GameAnalytics stresses that genres and business models produce different curves, and calls the familiar 40/20/10 rule (40% day 1, 20% day 7, 10% day 30) a reference point rather than a pass mark. Compare against your genre and your own previous builds.

Monetisation per user

ARPDAU tells you what an average day of play earns, combining ads and purchases. ARPPU and payer conversion separate how many people pay from how much they spend; a game can grow revenue by converting more players or by giving payers more worth buying. Count ad revenue properly: in ad-supported games it is often most of the income, and leaving it out makes LTV look far too low. Our guide to ads vs in-app purchases explains the trade-offs.

LTV, CPI and ROAS: the business test

Lifetime value is the number that decides how much you can spend on marketing. Teams usually track LTV at day 7, 30 and 90 for each cohort and project it forward. CPI is what installs cost in a given market and channel. ROAS compares a cohort's revenue with what it cost to acquire, often measured at day 7 and day 30. If projected LTV is below CPI, buying installs loses money, however good the game feels.

Instrument from the first build

GameAnalytics recommends a minimum event set of session start, tutorial complete, level complete, purchase and ad view. Add funnel steps for your first session, economy sources and sinks, and the points where players quit. Firebase's Google Analytics is free and widely used with Unity; whatever tool you use, agree event names before development so data stays comparable between builds.

Mistakes that mislead

• Mixed cohorts and comparing players acquired from different channels as if they were the same.
• Ignoring ad revenue in LTV and ARPDAU.
• Over-reading small tests. A few percentage points on a few hundred players is noise.
• Celebrating averages. A rise in ARPPU can hide a fall in payers.
• Old benchmarks. Retention across the market has fallen in recent years; use current, genre-specific data.

We set up analytics, dashboards and LiveOps for the games we build and for live games that need it. See LiveOps outsourcing and our soft launch guide for how these numbers drive launch decisions.

Sources: GameAnalytics: 2026 mobile and PC benchmarks · GameAnalytics: how to think about retention · GameAnalytics: post-launch analytics · Firebase: Google Analytics. Checked October 14, 2026.

Related: Ads vs IAP · LiveOps outsourcing · Mobile game development

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

A soft launch is a release in a small set of countries before the global launch, used to fix technical problems, improve retention and tune monetisation with real players while the stakes are low. Work in order: make the game stable first, then make players come back, then make it earn. Most soft launches run from a few weeks for a small casual game to several months for games with deeper economies, and they end when the numbers show that paying for installs will be profitable, or that the game needs rethinking.

Why soft launch at all

A global launch spends your biggest marketing budget and your one chance at store featuring. Launching broken, or with retention you could have fixed, wastes both. A soft launch gives you real behaviour from thousands of players instead of guesses, at a fraction of the cost.

The three phases

Liftoff, a mobile advertising platform, describes a three-phase structure that matches how most studios work:

Liftoff suggests the technical phase in lower-cost countries with enough players to trust the data, on the order of tens of thousands of users. Move on only when the current phase's goal is met; tuning monetisation while players leave on day one is wasted effort.

Choosing test markets

There is no official list, but the reasoning is consistent:

• Language: test in the language of your main market so text and tutorials are judged fairly.
• Install cost: cheaper installs make the technical phase affordable; later phases need markets whose players behave like your target audience.
• Similarity: studios targeting the US often use smaller English-speaking markets for retention and monetisation tests; studios targeting other regions pick look-alike markets nearby.
• Device mix: include markets with plenty of lower-end Android phones to expose performance problems.
• Limited spill-over: avoid your main launch markets so early reviews and charts do not follow you there.

Setting up the stores

• Google Play: production, open and closed testing releases can be limited to specific countries. New personal developer accounts must first run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access, so plan that into the schedule. Our guide to publishing on Google Play walks through it.
• App Store: set availability by country in App Store Connect. TestFlight allows up to 100 internal and 10,000 external testers for pre-release checks, with the first external build reviewed by Apple.
• Measurement on iOS: since iOS 14.5, apps need permission through App Tracking Transparency to track users across apps, which makes iOS campaign results less precise. Plan your attribution setup early.

What good looks like

Compare against your genre and your own previous games rather than one universal number. For context, GameAnalytics' 2026 benchmarks, based on more than 16,000 mobile games in 2025, put median day-one retention at about 22% and the top quarter just above 30%, with median day-seven retention just under 4%. GameAnalytics itself calls the popular 40/20/10 rule a reference point, not a threshold. Our mobile game KPIs guide explains each metric and formula.

How long it takes

A small casual game may finish its soft launch in a few weeks if the numbers are good from the start. Games with meta layers and economies often iterate for several months, shipping updates every week or two and measuring each change on fresh players. Decide in advance how many iteration cycles you will fund before killing or pivoting.

Ready for global launch when

• Crash rates and performance are acceptable on low-end devices.
• Retention has stopped improving with each update and sits at a level your genre can sustain.
• Early revenue per user, projected forward, covers what installs cost in your launch markets.
• Live operations are ready: content schedule, events, support and a team to run them.

Running a soft launch takes a small live team. We handle builds, analytics, iteration and LiveOps through launch; see our article on LiveOps outsourcing or mobile game development.

Sources: Liftoff: how to soft launch a casual game · Google Play: set up testing · Google Play: testing requirements for new personal accounts · Apple: TestFlight overview · Apple: user privacy and data use · GameAnalytics: 2026 benchmarks · GameAnalytics: thinking about retention. Checked October 14, 2026.

Related: Mobile game development · Publishing on Google Play · LiveOps outsourcing

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

A playable ad is a short interactive slice of a game, usually 15 to 60 seconds, delivered as an offline HTML5 file of about 5 MB or less that runs inside the ad network's player and ends with an install button. Building the mini-game is the easy part. The real work is fitting it into each network's size limit and packaging, wiring each network's own call-to-action code, and producing enough variations to test. Third-party estimates put a single externally produced playable at a few thousand dollars and complex ones at tens of thousands.

Why UA teams use them

Players who install after trying the game know what they are getting, which tends to improve post-install quality. Liftoff's 2025 Mobile Ad Creative Index reported that playables converted impressions to installs at many times the rate of non-playable formats in its data, and that top-spending game advertisers put more of their budget into playables. Treat those as one vendor's figures, but the direction is consistent across the industry: playables have become a standard part of mobile game creative testing.

Three shapes of playable

• Standalone playable: the whole ad is interactive, with an end card and install button.
• Video plus playable end card: a short video followed by a playable end screen.
• Lead-in video: on Meta and TikTok a video plays first and invites people to try the game.

What each network requires

Common rules across networks: no external network requests, everything embedded in the file, sound muted until the player interacts, support for portrait and landscape, and an install button that is always reachable. Networks also moderate creatives; Unity, for example, checks for console errors, orientation handling and whether the playable is too hard.

One 2026 change matters: Unity sunset the ironSource Ads network on 30 April 2026, so new campaigns and creative uploads moved to Unity Ads. ironSource Exchange and LevelPlay mediation continue.

How playables are built

• From an existing Unity game. Unity Playworks converts a Unity project into playables for many networks without using the WebGL build target. Its Lite tier is free but downloads only for Unity Ads; the Pro tier for all networks is priced for large advertisers. A standard Unity WebGL build is usually far too large: developers on Unity's forum report struggling to get even simple builds under 5 MB.
• Lightweight HTML5 engines. Phaser, PlayCanvas and similar engines produce small files. Phaser offers a playable template for many networks, and PlayCanvas documents an export for Meta's format. Base64 embedding adds about a third to asset sizes, so art budgets are tight.
• Hand-built HTML5 and JavaScript for the smallest, fastest files, at the cost of rebuilding the game's feel from scratch.

Design rules that convert

• Show the core mechanic in the first second. No menus, no loading wait beyond a brief splash.
• Make the first win easy, then hint at depth: a harder level, an upgrade, a locked area.
• End at the right moment, on a success or a near miss, with the install button front and centre.
• Represent the real game. The UK Advertising Standards Authority has ruled that mobile game ads must reflect actual gameplay, and that "not representative of gameplay" small print does not fix a misleading ad.
• Test variations, not just one playable: difficulty, length, first scene and end card.

Testing before launch

Every network has a preview tool: AppLovin's Playable Preview app, Unity's Ad Testing app and Meta's Playable Preview Tool all let you check behaviour on a real device from a QR code or upload. Test on low-end Android phones, with the mute switch on and off, rotating the screen, and locking and unlocking the phone. Rejections usually come from the call-to-action code or file size, not the gameplay.

What playables cost

There is no standard price. AppAgent, a UA agency, says external production typically costs $3,000 to $5,000 per creative with a two to four week turnaround. Other vendors quote $5,000 to $30,000 or more for playables with complex art and several scenes. The main cost drivers are art reuse from the game, the number of networks, the number of variants, and whether the game is rebuilt in HTML5 or converted from Unity.

If you are still validating a game, playables pair naturally with prototype testing: our hyper-casual development service produces the playable and video creatives used for early install tests. For the bigger picture on testing ideas cheaply, see our game prototyping guide.

Sources: Unity: user acquisition creatives · Unity: sunsetting ironSource Ads · IAB Tech Lab: MRAID · Mintegral: creative asset specs · Unity Playworks developer docs · AppAgent: state of playable ads 2025 · Liftoff: 2025 Mobile Ad Creative Index · UK ASA: mobile game ads. Checked October 14, 2026.

Related: Hyper-casual games · Mobile game development · Hyper-casual vs hybrid-casual

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

A single-mechanic puzzle MVP can start from $999 on our current launch pricing, and typical 2026 market ranges are $5,000 to $30,000 for a simple 2D puzzle and $30,000 to $80,000 for a polished casual puzzle with a meta layer, in-app purchases and LiveOps. What moves a puzzle budget is not the core mechanic but the levels: how much each one costs to design and prove solvable, whether you build tools to make them faster, and how many new levels you commit to after launch.

Why puzzle is still worth building

According to Naavik's analysis of Sensor Tower data, mobile puzzle games earned about $10 billion in in-app purchase revenue in 2025, second only to strategy. Growth came mostly from merge games and from small niches such as sort, screw and block puzzles, while classic match-3 held steady at the top. Naavik describes the barrier in sort puzzles as creative rather than financial, while block puzzles need heavy user acquisition spending. That is the opportunity for smaller teams: a fresh twist on a cheap-per-level niche.

Sub-genre sets the cost per level

Solvability matters more than people expect. Researchers have shown that even simple ball and water sort puzzles are computationally hard in general, which is why studios generating levels use solvers to confirm each one can be finished.

Build the tools before the content

For any puzzle game with more than a few dozen levels, a level editor pays for itself. In Unity this is usually a custom editor window or a Tilemap-based workflow where designers place pieces, test instantly and save levels as data. Add an automatic solver or bot playtester and you can measure difficulty before a human plays. King has described using bots that play each Candy Crush level thousands of times before release to measure difficulty, with designers deciding whether the result matches their intent.

Our Dungeon Quest: Color Fill case study, a hyper-casual colour-fill puzzle with hundreds of bite-sized levels, shows why tooling and a tuned difficulty curve matter as much as the mechanic.

Difficulty and monetisation are one design

Most levels should feel achievable, with occasional hard levels after runs of easier ones. Hard levels are where players use boosters, buy extra moves or watch a rewarded ad to continue, so the difficulty curve and the economy must be designed together. Common income sources:

• Rewarded ads for continues, extra moves and reward multipliers. AdMob's policy requires players to opt in clearly and receive the promised reward.
• Interstitial ads at natural breaks between levels, with a paid "remove ads" option.
• In-app purchases for boosters, lives, coin packs and season passes.

Our guide to ads vs in-app purchases explains how to balance the two.

LiveOps: the cost that keeps going

Top puzzle games ship new levels on a fixed rhythm; their store listings advertise new levels every week or two, plus time-limited events. Plan your content cadence before launch, because it decides your monthly running cost. Firebase Remote Config and A/B testing let you tune difficulty and offers without shipping an update. Our article on LiveOps outsourcing covers what that ongoing work includes.

Realistic budgets

The first prices are our current launch packages; the market ranges come from our game development cost guide.

How to start small

Prototype the mechanic with a handful of levels, test whether people understand it without a tutorial, then build the level editor before producing content at volume. Launch with enough levels to measure retention honestly, and add depth once you know players come back. We build puzzle games in Unity for iOS and Android; see 2D game development and mobile game development.

Sources: Naavik: niche sub-genres reshaping puzzle · Naavik: match-3 and merge leaders · Ito et al.: sorting balls and water · AdMob: rewarded ads policy · Firebase Remote Config. Checked October 14, 2026.

Related: 2D game development · Mobile game development · Game cost guide

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

Run Unity's Render Pipeline Converter for materials that use Unity's own Standard, Legacy and Mobile shaders, then sort every custom shader into one of three routes: rebuild it in Shader Graph, port it to hand-written URP HLSL, or replace it with a URP feature that already does the job. Surface shaders, GrabPass and OnRenderImage do not exist in URP, so plan for those first. Built-in is deprecated but supported through the Unity 6.7 LTS cycle, at least until the end of 2028, so do this carefully rather than in a panic. Our Unity 6 upgrade guide covers the planning side; this post covers the shader work.

Step 1: back up and triage

The converter overwrites files and Unity's documentation warns they cannot be restored, so work on a branch. Then list every shader in the project. From Unity 6.4, Project Auditor is built into the editor (Window > Analysis > Project Auditor) and its Shaders view shows variants, passes and keywords per shader. Sort them:

Step 2: run the converter

Open Window > Rendering > Render Pipeline Converter. From Unity 6.4 you choose Built-in as the source and URP as the target, select the material and settings converters, click Scan, review the list, then Convert Assets; Unity 6.0 to 6.3 use an Initialize Converters step instead. Standard maps to URP Lit and Legacy and Mobile shaders map to Simple Lit. Unity notes that Simple Lit is not a performance match for old mobile shaders, because it considers all lights in the URP Asset, so profile on devices afterwards. Unity 6.5 also added a command-line converter for batch runs on large projects.

The converter does not touch custom shaders. Any material still showing magenta afterwards is on your list for the next steps.

Step 3: decide what to do with surface shaders

Surface shaders are Built-in only. Unity had planned "Block Shaders" as a replacement for scriptable pipelines, but its shader team said in January 2026 that development is on hold. That leaves two options:

• Shader Graph. Usually the fastest route for lit materials with custom colour, masks, dissolve or vertex animation. A Custom Function node lets you keep small pieces of existing HLSL. Unity 6.3 added custom lighting templates, including toon and simplified lighting.
• Hand-written HLSL using URP's lighting functions. URP's UniversalFragmentPBR takes a SurfaceData structure whose fields line up closely with Built-in's SurfaceOutputStandard, which makes it the closest equivalent for porting a surface shader by hand.

Step 4: port hand-written shaders

For vertex and fragment shaders, the changes are mechanical but must all be made:

1. Replace CGPROGRAM and ENDCG with HLSLPROGRAM and ENDHLSL.
2. Replace UnityCG.cginc with URP's Core.hlsl include, plus Lighting.hlsl if you light the surface.
3. Add "RenderPipeline" = "UniversalPipeline" to the SubShader tags. Without it, URP will not use the SubShader.
4. Set pass tags: UniversalForward for the main pass and a ShadowCaster pass if the object casts shadows. URP does not support Built-in tags such as ForwardAdd.
5. Wrap material properties in CBUFFER_START(UnityPerMaterial) and CBUFFER_END, identical in every pass, so the shader stays compatible with the SRP Batcher.
6. Use URP's helpers, for example TransformObjectToHClip or GetVertexPositionInputs for positions, GetMainLight for the main light, and SampleSH instead of ShadeSH9.
7. Rename _MainTex and _Color to _BaseMap and _BaseColor if scripts or other systems expect URP naming, and update any scripts that set the old names.

Step 5: replace GrabPass and OnRenderImage

GrabPass is not supported in URP. Turn on Opaque Texture in the URP Asset, which Unity describes as working like GrabPass, and sample it with SampleSceneColor in HLSL or the Scene Color node in Shader Graph. It only contains opaque objects, so refraction shaders must render as transparent.

OnRenderImage is not supported in scriptable pipelines, and Camera.AddCommandBuffer only works in Built-in. For simple full-screen effects, create a Fullscreen Shader Graph and add a Full Screen Pass Renderer Feature to the renderer. For complex effects, write a Renderer Feature using the render graph API; from Unity 6.4 the old Compatibility Mode for custom passes is removed, so new passes must use render graph.

The traps that waste days

• No shadows, no error. If a ported shader leaves out URP's main-light shadow keywords, it compiles cleanly and simply receives no shadows.
• Forward+ and extra lights. In the Forward+ path the old additional-light count returns zero; use the cluster light loop macros instead. The older _FORWARD_PLUS keyword was deprecated in Unity 6.1.
• Missing depth-normals pass. Custom shaders without one will not contribute to SSAO properly.
• Variant explosion. Every multi_compile multiplies variants and build time. Check stripping settings and the Frame Debugger after conversion.
• Scripts setting old property names. URP Lit keeps _Color only as a hidden legacy property, so code that sets it stops changing the visible colour.

Test it properly

Compare screenshots of every scene before and after, profile on your weakest target device, check the SRP Batcher is batching in the Frame Debugger, and run a full QA pass before any release. Conversions look finished long before they are.

Need help converting?

We convert Unity projects to URP for studios that want their own team on new content: audit first, then a fixed price for the shader and pipeline work. See co-development and project rescue or Unity game development.

Sources: Unity Manual: Render Pipeline Converter · Unity: render pipelines strategy for 2026 · Unity Manual: surface shaders · Unity Manual: GrabPass · Unity Scripting API: OnRenderImage · Unity: Block Shaders on hold. Checked October 14, 2026.

Related: Co-development and rescue · Unity game development · Unity 6 upgrade guide

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

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

1. Prototype the idea with AI. Prove the core loop is fun with generated placeholders. Keep it cheap and disposable.
2. Write down what worked. A short design document turns the prototype into decisions. Our game design document guide shows what to include.
3. Rebuild the foundation properly. Prototype code is usually thrown away. The production version needs clean architecture, real art direction and performance budgets.
4. Keep AI in the pipeline. Use it for concepting, variations and tooling, with artists and engineers in control of quality.
5. 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.

Related: AI game development · Is AI replacing developers? · Packages and quote

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

An AI NPC is a game character whose dialogue or decisions come from a language model at runtime instead of a fixed script. In 2026 they work best in narrow roles with clear goals: a companion who comments on what you do, a shopkeeper you can haggle with, a suspect you interrogate. They need guardrails, a fallback for when the model is slow or wrong, and a running-cost estimate before launch. Done well, they make a world feel alive. Bolted on, they make it feel like a chatbot wearing a costume.

What has actually shipped

For years AI NPCs were tech demos. In 2025 they started appearing in commercial games. Krafton's life sim inZOI added an experimental "Smart Zoi" setting in which characters' thoughts and actions are driven by a small language model running on the player's own GPU, through NVIDIA's ACE technology; NVIDIA describes it as a 0.5-billion-parameter model. Characters adjust their daily plans based on what happened to them, and players can watch their inner thoughts. NetEase added an on-device ACE teammate to NARAKA: BLADEPOINT MOBILE PC VERSION that fights alongside you, finds items and suggests skills. Other big publishers have shown prototypes, but most AI characters in 2026 are still optional features or experiments rather than the core of a game.

The lesson from what shipped: the successful versions give the model a small, well-defined job inside systems the game already controls.

The five parts of an AI NPC

1. Input. Typed text, or speech converted to text. Voice feels magical but adds a speech-recognition step, latency and accents to test.
2. Character brain. A language model given a persona: who the character is, what they know, what they want and how they speak. This instruction block is the most important piece of writing in the feature.
3. Memory and world state. What the character remembers about the player and what is true in the game right now: quest progress, inventory, time of day. Without it, characters contradict the game.
4. Guardrails. Rules and filters that keep the character in role, on topic and within your age rating, plus checks on anything the model asks the game to do.
5. Output and actions. Text or synthesised voice, animation and lip sync, and a short, fixed list of game actions the model may request, such as give item, change mood or open shop. The game validates every request; the model never changes game state directly.

Cloud model or on-device model?

Many teams prototype with a cloud model, because it is fast to try ideas, then decide per character whether the quality justifies the cost or whether a smaller model will do.

How to estimate running costs

Cloud models charge per token, roughly three-quarters of a word. Each player message sends the persona, the relevant memory and world state, and the recent conversation, then receives a short reply. The estimate is simple arithmetic:

monthly cost ≈ players × conversations per player × turns per conversation × (input tokens × input price + output tokens × output price)

Run it with your own design numbers and your provider's current price list. Three habits keep the bill small: keep the persona tight, summarise long conversations instead of resending them, and use the provider's prompt caching so the unchanging persona is billed at a discount. A cheaper, faster model is often better for in-game chatter anyway, because players notice delay more than eloquence.

Design rules that separate good AI NPCs from gimmicks

• Give the character a job. "Convince the player not to enter the mine" is a design. "Talk about anything" is a chatbot.
• Let the game stay in charge. Quests, rewards and outcomes come from your systems. The model chooses words and requests actions from a short list.
• Hide the wait. Thinking animations, short pre-written barks and streamed text make a two-second response feel natural.
• Fail gracefully. If the model times out or a filter blocks a reply, fall back to a scripted line in character. Never show an error.
• Test like an adversary. Players will try to break the character within minutes. Red-team prompts for jailbreaks, spoilers and off-rating content before launch.

Store rules, ratings and voice

Steam requires developers to disclose AI use in its content survey and to describe the guardrails on live-generated content, and it shows the disclosure on the store page. Age ratings apply to everything a character can say, so your filters must match your rating. If characters speak, check the licence of any synthetic voice, and remember that voice actors' union agreements now include consent and disclosure rules for AI voice replicas.

What it takes to build one

A focused prototype, one character in one scene of an existing Unity or Unreal project, is usually a few weeks of work and the cheapest way to learn whether the idea is fun. A production feature adds memory, guardrails, voice, localisation, cost controls and analytics. We build both on our AI and LLM game development service, using cloud models, including the latest Claude models, or on-device models depending on the game, and quote a fixed price after a short brief.

Sources: NVIDIA: ACE characters in inZOI and NARAKA: BLADEPOINT · VGC on Steam AI disclosure. Checked October 12, 2026.

Related: AI game development · Is AI replacing game developers? · Unity development

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

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

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:

1. 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.
2. 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.
3. Input. Galaxy XR is built around hand and eye tracking, with controllers optional. Every interaction must work without a controller.
4. Performance. Profile on the device. Display resolution and refresh targets differ from Quest, so frame budgets and render scale need retuning.
5. 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.

Related: VR game development · VR and AR packages · Smart glasses development

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

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

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.

Related: Unity game development · PC and Steam games · Mobile games

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

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

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.

Related: AR development · VR development · AR learning trails

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

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

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.