<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ocean View Games</title>
    <description>The latest articles on DEV Community by Ocean View Games (@oceanviewgames).</description>
    <link>https://dev.to/oceanviewgames</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3759146%2F14494f92-1fd2-4a18-a5fa-9ff13c592600.png</url>
      <title>DEV Community: Ocean View Games</title>
      <link>https://dev.to/oceanviewgames</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/oceanviewgames"/>
    <language>en</language>
    <item>
      <title>Game Development for Startups: From MVP to Launch</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Mon, 02 Nov 2026 22:34:22 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/game-development-for-startups-from-mvp-to-launch-3i9l</link>
      <guid>https://dev.to/oceanviewgames/game-development-for-startups-from-mvp-to-launch-3i9l</guid>
      <description>&lt;p&gt;You have a game idea and decisions to make about what to build first. You may be preparing for funding, working with a limited initial budget or scaling a project that has already secured investment. In each case, the first technical choices should help you test the idea without creating unnecessary work later.&lt;/p&gt;

&lt;p&gt;We &lt;a href="https://oceanviewgames.co.uk/industries/startups?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;work with startups and indie studios&lt;/a&gt; regularly, from pre-seed teams with a game design document to funded studios scaling towards launch. This post goes deeper into how to get from concept to shipped product, covering what an MVP actually looks like, how to scale after funding, and why the partner you choose matters more than you might expect.&lt;/p&gt;

&lt;p&gt;The right approach varies between mobile, PC and educational projects. A few early decisions can help avoid costly surprises later, but no architecture can remove all delivery risk.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Startups Need From a Game Dev Partner
&lt;/h2&gt;

&lt;p&gt;Startup game development is fundamentally different from working with an established studio. You are not maintaining a live product or iterating on a proven formula. You are proving a concept under time pressure, often with investors watching. That context changes what matters in a development partner.&lt;/p&gt;

&lt;h3&gt;
  
  
  Speed to Prototype
&lt;/h3&gt;

&lt;p&gt;A useful early priority is getting the riskiest assumption into a testable form. Not a polished trailer. Not concept art. A working build that demonstrates your core gameplay loop and key differentiator. Long pre-production can be risky if it delays learning from real users.&lt;/p&gt;

&lt;p&gt;Speed to prototype matters, but the useful target depends on the scope. A small single-player mobile concept may reach a playable core loop in weeks; a systems-heavy title, substantial content slice, or online backend takes longer. The point is to identify the riskiest assumption and get it into a real build early, not to optimise for an arbitrary calendar promise.&lt;/p&gt;

&lt;p&gt;Speed does not mean cutting corners. It means having engineers who have built similar systems before and can make architectural decisions without weeks of research. When your lead developer has shipped mobile games, live products, platform ports, or systems-heavy Unity projects before, the path from concept to prototype compresses dramatically. Experience reduces the amount of exploratory work required for familiar problems and, just as importantly, helps identify which decisions are genuinely uncertain and deserve a prototype.&lt;/p&gt;

&lt;h3&gt;
  
  
  Build for the Decision You Need to Make
&lt;/h3&gt;

&lt;p&gt;This is where many startup game projects get into trouble. The prototype gets built as a throwaway, with hardcoded systems, monolithic scripts, and assumptions that only work for the first demo. Then when funding arrives and the team needs to add content, platforms, services, or more developers, they discover that large parts of the prototype need to be rebuilt.&lt;/p&gt;

&lt;p&gt;The architectural decisions that matter most in the first weeks of a project are often invisible to non-technical stakeholders, but they determine whether your codebase can grow or needs to be thrown away. These include:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Platform and service boundaries.&lt;/strong&gt; Decide early which responsibilities belong in the client, which belong in platform services or a backend, and which data needs to survive reinstalls or device changes. You do not need production infrastructure on day one, but you should avoid baking temporary assumptions into every gameplay system.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Data persistence layer.&lt;/strong&gt; How player data is stored, synced, and recovered needs to be designed from the start. A prototype that saves everything locally cannot become a live service game without a fundamental rearchitecture. Planning for cloud saves, server-side validation, and offline resilience early costs very little but saves months later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Analytics and telemetry hooks.&lt;/strong&gt; Investors and publishers want data. If your prototype has no analytics infrastructure, you cannot answer basic questions about session length, retention, or where players drop off. Instrumenting a codebase after the fact is tedious and error-prone. Planning simple event names and analytics boundaries early can make later instrumentation easier. The actual effort depends on the SDK, privacy requirements and project design.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Modular system design.&lt;/strong&gt; Systems like inventory, progression, combat, and UI should be loosely coupled so that changes to one do not cascade through the entire project. This is the difference between adding a new feature in a day versus spending a week untangling dependencies.&lt;/p&gt;

&lt;p&gt;For prototypes intended to continue into production, we plan a clear route for the parts that need to grow. That means clean separation of concerns, modular systems that can be extended without refactoring everything around them, and service boundaries that can evolve as the product's real requirements become clearer.&lt;/p&gt;

&lt;h3&gt;
  
  
  Technical Credibility for Investors
&lt;/h3&gt;

&lt;p&gt;Investors in game startups are increasingly technical. They want to know that the architecture can support the vision, that the team has relevant experience, and that the technical risks have been identified and mitigated. A playable build, honest technical plan and a clear record of what has and has not been validated can help address those questions.&lt;/p&gt;

&lt;p&gt;When we built the server architecture and core gameplay systems for &lt;a href="https://oceanviewgames.co.uk/case-studies/domi-online-unity-mmo?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt;, the client needed more than a proof of concept. They needed to demonstrate to investors that the underlying technology could support a full-scale MMORPG. That meant building a server-authoritative backend using FishNet that held up in closed alpha stress tests with up to 500 players, with a functioning in-game economy and real-time combat. We delivered exactly that: a playable MMO with server-authoritative networking and a working in-game economy, tested by real players, rather than a slide deck with promises. That kind of technical credibility is what earns investor confidence in a game startup.&lt;/p&gt;




&lt;h2&gt;
  
  
  MVP and Prototype Development
&lt;/h2&gt;

&lt;p&gt;The term "MVP" gets used loosely in game development. An MVP tests whether a limited product provides value; a vertical slice demonstrates a representative part of the intended final experience. They sometimes overlap, but they are not interchangeable.&lt;/p&gt;

&lt;h3&gt;
  
  
  What a Game MVP Actually Looks Like
&lt;/h3&gt;

&lt;p&gt;A game MVP is a limited product designed to test a market or user assumption. A vertical slice is a representative, often polished example of the intended production experience. A vertical slice can be useful for pitching, but it does not by itself prove player demand. It may include: gameplay, UI, audio, platform integration, and (where relevant) networking. It should feel like a finished experience, even if the content is limited.&lt;/p&gt;

&lt;p&gt;Specifically, a strong MVP includes:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Core loop playable.&lt;/strong&gt; The fundamental gameplay cycle that players will repeat. If your game is a city builder, the player should be able to place buildings, manage resources, and experience the progression loop. If it is an educational game, the learner should be able to complete a representative activity and see the intended feedback or outcome.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key differentiator visible.&lt;/strong&gt; Whatever makes your game different from existing titles needs to be front and centre. If your pitch is "an RPG with an AI-driven narrative system," that system needs to be working in the MVP, even if the content around it is placeholder.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Running on target platform.&lt;/strong&gt; If you are building a mobile game, the MVP must run on mobile devices. Performance characteristics, input methods, and screen constraints are fundamentally different on mobile. A Unity editor build that runs at 60fps on a development PC tells you nothing about whether it will run acceptably on a mid-range Android device. We have written extensively about &lt;a href="https://oceanviewgames.co.uk/blog/posts/managing-thermal-throttling-unity-mobile?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;managing performance on mobile&lt;/a&gt; and why early device testing is non-negotiable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Monetisation touchpoints (if applicable).&lt;/strong&gt; If your business model depends on in-app purchases, a battle pass, or an ad-supported model, the MVP should include at least the integration points for those systems. Investors want to see that you have thought about how the game makes money, not just how it plays.&lt;/p&gt;

&lt;p&gt;To make this concrete, here is what an MVP looks like for different types of game:&lt;/p&gt;

&lt;p&gt;For a &lt;strong&gt;mobile casual game&lt;/strong&gt;, an MVP might consist of three to five playable levels demonstrating the core loop, a basic meta-layer (progression, unlocks, or a simple economy), UI that works across phone and tablet form factors, and a functioning tutorial. This is enough to validate whether the core mechanic is fun and to start gathering retention data from playtests.&lt;/p&gt;

&lt;p&gt;For a &lt;strong&gt;midcore mobile title&lt;/strong&gt;, the scope expands to include deeper progression systems, multiple interacting mechanics (for example, combat plus base-building plus resource management), and early monetisation hooks. The vertical slice needs to show that these systems create a satisfying loop together, not just that each works in isolation.&lt;/p&gt;

&lt;p&gt;For an &lt;strong&gt;educational or serious game&lt;/strong&gt;, the MVP should prove both the experience and the practical delivery model. That might mean one representative learning scenario, the assessment or reporting flow, deployment on the target devices, and enough analytics or LMS integration to show that outcomes can be measured. The aim is to validate the experience before commissioning a large content library.&lt;/p&gt;

&lt;h3&gt;
  
  
  Timeline Expectations
&lt;/h3&gt;

&lt;p&gt;As rough planning examples rather than quotes, MVP windows can look like this when the brief, art dependencies, and technical risks are reasonably clear:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Small casual mobile prototype (often measured in weeks).&lt;/strong&gt; A focused vertical slice of a single-player mobile game: core loop, basic UI, placeholder art, and a build running on device. A narrow, well-defined concept may fit into roughly four to six weeks, but content, integrations, and art readiness can move that substantially.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Deeper systems prototype (often a couple of months or more).&lt;/strong&gt; Multiple interacting systems, early progression, and enough presentation quality for stakeholder or investor demos require more integration and iteration. Eight to twelve weeks can be a useful starting assumption for some scopes, but it should be validated against the actual feature list and dependencies.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Systems-heavy or connected product (scope-dependent).&lt;/strong&gt; A vertical slice with backend services, persistence, live data, or other production-like infrastructure takes longer than a self-contained prototype because more layers have to work together. Prove the highest-risk integration first and keep the first milestone narrow enough that you can still change direction.&lt;/p&gt;

&lt;p&gt;These timelines assume a team of two to four experienced developers working with a clear brief. If you are not sure what your game will cost or how long it will take, our &lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;game development cost estimator&lt;/a&gt; and &lt;a href="https://oceanviewgames.co.uk/resources/game-development-timeline-estimator?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;game development timeline estimator&lt;/a&gt; can give you a starting framework.&lt;/p&gt;




&lt;h2&gt;
  
  
  Scaling After Funding
&lt;/h2&gt;

&lt;p&gt;Securing funding is a milestone, not a finish line. The transition from prototype to production is where many startup game projects stumble, because the skills and approach that work for a three-person prototype team do not automatically scale to a ten-person production team.&lt;/p&gt;

&lt;h3&gt;
  
  
  From Prototype to Production
&lt;/h3&gt;

&lt;p&gt;The first step after funding is an honest technical assessment of your prototype. Even well-built prototypes will have areas that need reinforcement before they can support a full production workload. This might mean replacing placeholder networking with production-grade infrastructure, implementing proper asset pipelines, or building out the tooling that your content creators will need.&lt;/p&gt;

&lt;p&gt;This is not a rewrite. If the prototype was built with scalability in mind, it is a structured expansion of existing systems. If it was not, this is the point where the cost of throwaway prototyping becomes painfully visible.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Co-Development Model
&lt;/h3&gt;

&lt;p&gt;For startups that have just secured funding, the &lt;a href="https://oceanviewgames.co.uk/services/codevelopment?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;co-development model&lt;/a&gt; can be an effective way to add capacity. Rather than waiting for every permanent hire to be recruited and onboarded, a co-development partner can begin integrating with your existing team while you continue building the long-term organisation.&lt;/p&gt;

&lt;p&gt;In practice, we start by joining the project's version control, communication channels, and planning tools, then review the codebase, architectural patterns, build process, and coding standards. The first production contribution depends on the codebase and scope, but the goal is to get useful work flowing without creating a long parallel onboarding project.&lt;/p&gt;

&lt;p&gt;During active development, we typically work in the same sprint cadence as your internal team, attending standups, contributing to code reviews, and owning specific systems or features end to end. This is not outsourcing in the traditional sense. We are not working from a specification document in isolation and delivering a build at the end of the month. We are embedded in your team, working shoulder to shoulder (or screen to screen) on a daily basis.&lt;/p&gt;

&lt;p&gt;When it comes to handoff, we document every system we build, maintain clean commit histories, and ensure that your internal team can maintain and extend our work without us. A good co-development engagement should leave your team stronger, not dependent. We transfer knowledge continuously throughout the project, not in a single handoff meeting at the end.&lt;/p&gt;

&lt;p&gt;This model gives you production capacity without the overhead of full-time employment. You scale up during intensive development phases and scale down during content creation or QA periods. Our &lt;a href="https://oceanviewgames.co.uk/services/gamedevelopment?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;game development services&lt;/a&gt; are built around this model, providing dedicated Unity engineers who work as an extension of your team rather than as external contractors.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Choose a Specialist Studio
&lt;/h2&gt;

&lt;p&gt;Choosing a development partner is about matching the team’s experience to the project. For a game startup, experience with the target platforms and gameplay systems can make a meaningful difference to risk and planning.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where Specialist Game Experience Helps
&lt;/h3&gt;

&lt;p&gt;A general software team may be very good at its own discipline while having less experience with the particular constraints of a game. That does not make the team unsuitable, but it does mean the scope should account for where specialist input or additional investigation will be needed.&lt;/p&gt;

&lt;p&gt;Game development is not web development with graphics. The constraints are different: frame time, input responsiveness, device performance, asset size, platform APIs, save integrity, build pipelines, and certification can all shape technical decisions. A strong software team can learn those constraints, but a specialist game team starts with more of that context already in place.&lt;/p&gt;

&lt;p&gt;For a startup with a fixed budget, unexpected research and rework can put delivery dates under pressure. Ask potential partners which comparable problems they have solved, where they expect uncertainty and how they will test the highest-risk assumptions early.&lt;/p&gt;

&lt;h3&gt;
  
  
  Senior Engineering Ownership
&lt;/h3&gt;

&lt;p&gt;When you are working with startup budgets and timelines, the early architecture needs senior ownership. Junior developers can contribute effectively when they are supported, but critical technical decisions should not be left to an unsupervised team that is learning the problem space at the client's expense.&lt;/p&gt;

&lt;p&gt;Every developer on our team is senior. David's background includes RuneScape Mobile at Jagex, while Adam brings long-term Unity and studio experience. For a startup, that means the people making early architectural decisions are the same people implementing and reviewing the systems, rather than a sales layer handing the project to a junior team.&lt;/p&gt;

&lt;p&gt;This matters most when early decisions have expensive consequences. An experienced engineer is more likely to recognise a familiar mobile-performance, persistence, build, or architecture risk while it is still cheap to change, rather than discovering it during late device testing or production hardening.&lt;/p&gt;

&lt;h3&gt;
  
  
  Domain Expertise That Transfers
&lt;/h3&gt;

&lt;p&gt;General software development experience does not automatically translate to game development. Games have unique constraints: real-time rendering, frame-budget management, input latency, platform certification requirements, and player experience considerations that web and enterprise developers rarely encounter.&lt;/p&gt;

&lt;p&gt;As a Unity Certified Expert with 12 years of experience, I worked on the RuneScape Mobile team at Jagex from 2017 to 2019. Working on a long-lived MMORPG moving onto iOS and Android exposed the kind of problems that only appear when legacy architecture, mobile performance constraints, platform requirements, and established player expectations meet. That experience still shapes how I assess technical risk on new projects.&lt;/p&gt;

&lt;p&gt;We bring that same depth to every startup engagement. Whether the challenge is &lt;a href="https://oceanviewgames.co.uk/services/mobile?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;optimising a Unity game for low-end Android devices&lt;/a&gt;, architecting live game systems that scale, or designing &lt;a href="https://oceanviewgames.co.uk/blog/posts/building-infinite-progression-systems-unity?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;progression systems&lt;/a&gt; that keep players engaged, we have done it before and can do it efficiently.&lt;/p&gt;

&lt;p&gt;You can learn more about &lt;a href="https://oceanviewgames.co.uk/about?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;our team&lt;/a&gt; and see the full range of projects we have delivered on our &lt;a href="https://oceanviewgames.co.uk/case-studies?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;case studies page&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Ready to Build?
&lt;/h2&gt;

&lt;p&gt;If you have funding, a game concept, and a deadline, we would like to hear from you. We work with startups from prototype through to launch, providing the technical expertise and production capacity to turn your vision into a shipped product.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://oceanviewgames.co.uk/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups#contact" rel="noopener noreferrer"&gt;Contact us&lt;/a&gt; to discuss your project. We will give you an honest assessment of scope, timeline, and cost before any commitment.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;David Edgecombe is the Director and Principal Unity Engineer at &lt;a href="https://oceanviewgames.co.uk/?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=game-development-for-startups" rel="noopener noreferrer"&gt;Ocean View Games&lt;/a&gt;, a UK game development studio working across Unity, mobile, educational games, co-development, and legacy modernisation. His background includes hands-on development on RuneScape Mobile at Jagex.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>LiveOps for Indie Studios: Doing More with Less</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Tue, 27 Oct 2026 19:45:51 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/liveops-for-indie-studios-doing-more-with-less-5290</link>
      <guid>https://dev.to/oceanviewgames/liveops-for-indie-studios-doing-more-with-less-5290</guid>
      <description>&lt;p&gt;Launch day is not the finish line. For mobile and live-service games, it is barely the starting pistol. The real work - keeping players engaged, retaining them over weeks and months, and building sustainable revenue - happens through live operations (LiveOps).&lt;/p&gt;

&lt;p&gt;The problem for indie studios is that most LiveOps advice is written for teams with dedicated data analysts, content pipelines staffed by dozens of artists, and server infrastructure budgets that would fund an entire indie game. That advice is useless if you are a team of 3-10 people operating on a lean budget.&lt;/p&gt;

&lt;p&gt;At Ocean View Games, we have worked on live game systems for projects ranging from our own internal titles like Empires Rise to previous live-service development on &lt;a href="https://oceanviewgames.co.uk/case-studies/domi-online-unity-mmo?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt;, a cap-less MMORPG that ran four closed alpha stress tests. That work has shaped how we think about the trade-offs small teams face, though every game needs its own evidence.&lt;/p&gt;

&lt;p&gt;This article is a practical guide to running effective LiveOps on an indie budget.&lt;/p&gt;




&lt;h2&gt;
  
  
  What LiveOps Actually Means for Indies
&lt;/h2&gt;

&lt;p&gt;LiveOps is a broad term that encompasses everything you do to keep a live game healthy after launch. For a large studio, this might involve a 50-person team running 24/7 server operations. For an indie studio, it comes down to four core activities:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Content updates&lt;/strong&gt; - New features, levels, items, or events that give players a reason to come back&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Monetisation management&lt;/strong&gt; - Adjusting pricing, running sales, and optimising ad placements based on real data&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Community engagement&lt;/strong&gt; - Communicating with players, responding to feedback, and building a relationship that drives retention&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Technical maintenance&lt;/strong&gt; - Bug fixes, performance improvements, SDK updates, and platform compliance&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The key insight is that you do not need to do all of these at scale from Day 1. You need a system that lets you do them efficiently and grow as your player base grows.&lt;/p&gt;




&lt;h2&gt;
  
  
  Building a Seasonal Content Calendar
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why Seasonality Works
&lt;/h3&gt;

&lt;p&gt;Seasonal events are the backbone of indie LiveOps because they solve multiple problems simultaneously:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;They give lapsed players a reason to return (a limited-time event creates urgency)&lt;/li&gt;
&lt;li&gt;They provide a predictable content rhythm that sets player expectations&lt;/li&gt;
&lt;li&gt;They create natural monetisation windows (themed cosmetics, bundles, limited offers)&lt;/li&gt;
&lt;li&gt;They generate social media content and community discussion organically&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Indie-Friendly Content Calendar
&lt;/h3&gt;

&lt;p&gt;A large studio might run events every two weeks. For an indie team, that pace is unsustainable. Here is one possible starting cadence to adjust to your team and player response:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quarterly Major Events (4 per year)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tied to real-world seasons or holidays (Halloween, Christmas, Summer, Spring)&lt;/li&gt;
&lt;li&gt;Each event includes 1-2 new gameplay elements, themed cosmetics, and a limited-time challenge&lt;/li&gt;
&lt;li&gt;Plan these 2-3 months in advance so art and design work can be spread across sprints&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Monthly Minor Updates (12 per year)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Balance changes, quality-of-life improvements, and bug fixes&lt;/li&gt;
&lt;li&gt;Community-requested features (pick the most impactful request from your feedback channels)&lt;/li&gt;
&lt;li&gt;These keep the game feeling alive between major events&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Weekly Rotations (Automated)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rotating daily challenges, featured items in the shop, or leaderboard resets&lt;/li&gt;
&lt;li&gt;Build these systems once and they run themselves. A daily challenge system that draws from a pool of pre-made challenges can provide months of content with zero ongoing effort.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; The secret to sustainable indie LiveOps is automation. Invest development time into building systems that generate variety (rotating shops, daily challenges, procedural missions) rather than hand-crafting every piece of content individually.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Our Experience with Domi Online
&lt;/h3&gt;

&lt;p&gt;For Domi Online, we designed operational systems with a small team in mind. The important principle was to keep event and configuration data separate from client code wherever practical, so routine live changes do not automatically become a full engineering-and-release exercise. That kind of data-driven workflow matters more, not less, when the team is lean.&lt;/p&gt;




&lt;h2&gt;
  
  
  A/B Testing with Small Audiences
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Problem with Small Sample Sizes
&lt;/h3&gt;

&lt;p&gt;A/B testing can help evaluate changes to monetisation and engagement, but the standard advice assumes you have tens of thousands of daily active users (DAU). When you have 500 DAU, traditional A/B testing hits a wall: sample sizes are too small to reach statistical significance in any reasonable timeframe.&lt;/p&gt;

&lt;h3&gt;
  
  
  Practical Approaches for Indie Scale
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1. Test fewer variables with larger effect sizes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Do not A/B test whether a button should be blue or green. Test things with large expected differences:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Free currency reward of 100 vs. 500 for completing a tutorial&lt;/li&gt;
&lt;li&gt;Showing a special offer after level 3 vs. after level 5&lt;/li&gt;
&lt;li&gt;Interstitial ad frequency of every 3 minutes vs. every 5 minutes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;At a few hundred daily active users, small experiments can take a long time to produce a trustworthy signal. In practice, small studios should test larger hypotheses, run them for long enough to observe behaviour, and avoid overreacting to week-to-week noise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Choose a valid test method before checking results&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Repeatedly checking a conventional fixed-sample A/B test and stopping when the result looks good can create false positives. Proper sequential methods exist, but they need planned stopping rules and statistical safeguards. With a small audience, a structured qualitative test or a limited rollout may provide more useful evidence than forcing a significance claim.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Leverage your community for qualitative feedback&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When quantitative data is scarce, qualitative data becomes invaluable:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Run polls in your Discord server asking players to choose between two options&lt;/li&gt;
&lt;li&gt;Release a feature to a small beta group and collect structured feedback before a full rollout&lt;/li&gt;
&lt;li&gt;Use suitable, consent-aware analytics and playtesting to understand how players interact with a feature; verify which tools actually support session recording rather than assuming analytics includes replay&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;4. Evaluate a Remote Configuration Tool&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Remote configuration tools can help change suitable values without shipping a new client build. Check current pricing, platform restrictions, consent requirements and experimentation support before choosing a provider. A remote parameter change is not automatically a statistically reliable A/B test.&lt;/p&gt;




&lt;h2&gt;
  
  
  Event-Driven Monetisation
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Core Principle: Respect Player Context
&lt;/h3&gt;

&lt;p&gt;Monetisation should fit the player experience and business model. Avoid exploiting pressure, frustration or near-misses. Consider offers that players can understand and choose freely.&lt;/p&gt;

&lt;p&gt;Here are the emotional moments that drive conversion:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Achievement:&lt;/strong&gt; The player just completed a difficult challenge or reached a milestone. Offer a celebratory bundle or cosmetic that commemorates the achievement.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Player choice:&lt;/strong&gt; Offer an optional convenience item when it is relevant, without manufacturing failure or urgency.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Collection progress:&lt;/strong&gt; The player is 80% of the way to completing a set. Show their progress and offer the remaining pieces.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cosmetic interest:&lt;/strong&gt; Let players browse optional cosmetic items without pressure from comparisons with other players.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Designing Offers Carefully on an Indie Budget
&lt;/h3&gt;

&lt;p&gt;You do not need a sophisticated machine learning pipeline to implement contextual offers. A simple rule-based system works:&lt;/p&gt;

&lt;p&gt;A safer first step is to identify where offers fit naturally in a game's progression, then check whether they interrupt play or penalise people who do not pay. Do not trigger purchases simply because a player has failed repeatedly, and avoid artificial urgency unless a time limit is real and explained.&lt;/p&gt;

&lt;p&gt;These rules can be configured server-side (via Firebase Remote Config or PlayFab) and adjusted based on what you see in your analytics. No machine learning required.&lt;/p&gt;

&lt;h3&gt;
  
  
  When Rewarded Ads Make Sense
&lt;/h3&gt;

&lt;p&gt;Rewarded video ads can suit some free-to-play games, especially where optional rewards fit the design. They are not appropriate for every genre, audience or platform, and their commercial value depends on retention, geography and ad demand.&lt;/p&gt;

&lt;p&gt;Best practices for rewarded ads:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Place them at natural break points (between levels, after a defeat, at a daily reward screen)&lt;/li&gt;
&lt;li&gt;Make the reward meaningful (double coins, an extra life, a temporary boost) but not so powerful that non-watching players feel disadvantaged&lt;/li&gt;
&lt;li&gt;Set sensible frequency caps using player feedback and actual retention data rather than a universal daily number&lt;/li&gt;
&lt;li&gt;Use mediation (IronSource, AdMob, or Unity Ads) to maximise fill rates and eCPM&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We cover monetisation strategy in much more depth in our &lt;a href="https://oceanviewgames.co.uk/services/monetization?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;game monetisation services&lt;/a&gt; overview.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; There is no single best revenue mix for indie games. Compare ads, purchases, premium pricing and subscriptions against your audience and gameplay before committing.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Community Engagement on a Budget
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Your Community Is Your LiveOps Team
&lt;/h3&gt;

&lt;p&gt;For indie studios, the player community is not just an audience. It is an extension of your team. Engaged communities generate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Bug reports&lt;/strong&gt; that are more detailed and more numerous than any QA team you could afford&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Content ideas&lt;/strong&gt; that reflect what players actually want (not what you assume they want)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Word-of-mouth marketing&lt;/strong&gt; that no advertising budget can replicate&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User-generated content&lt;/strong&gt; (fan art, guides, videos) that provides free marketing material&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Minimum Viable Community Stack
&lt;/h3&gt;

&lt;p&gt;You do not need a community manager or a custom forum. Here is the minimum stack we recommend:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Discord server&lt;/strong&gt; (free) - Your primary community hub. Use channels for bug reports, feature requests, general discussion, and announcements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Social media presence&lt;/strong&gt; (1 platform, done well) - Choose one platform where your audience lives. For most game developers, this is Twitter/X or TikTok. Post development updates, behind-the-scenes content, and respond to player messages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In-game news feed&lt;/strong&gt; - A simple scrollable news panel in the main menu that announces events, patch notes, and community highlights. Build it once and update it via a remote config.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Communication Cadence
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Weekly:&lt;/strong&gt; A brief dev update in Discord (even a few sentences about what you worked on this week)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-update:&lt;/strong&gt; Patch notes published to Discord and the in-game news feed&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-event:&lt;/strong&gt; Announcement post on social media with screenshots or a short video&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Consistency matters more than frequency. A short weekly update builds more trust than sporadic long posts.&lt;/p&gt;




&lt;h2&gt;
  
  
  Tools That Scale from Hundreds to Thousands
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Free/Cheap Tier Stack
&lt;/h3&gt;

&lt;p&gt;One advantage indie developers have in 2026 is that many enterprise-grade tools offer free tiers that are more than sufficient for games with small-to-medium player bases. Here is the stack we recommend:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;Free Tier Limit&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Firebase Analytics&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Event tracking, user properties, funnel analysis&lt;/td&gt;
&lt;td&gt;Unlimited events&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Firebase Remote Config&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Feature flags, A/B tests, server-side config&lt;/td&gt;
&lt;td&gt;2,000 parameters&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Firebase Crashlytics&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Crash reporting and diagnostics&lt;/td&gt;
&lt;td&gt;Unlimited&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Unity Analytics&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Session tracking, retention, basic monetisation metrics&lt;/td&gt;
&lt;td&gt;Included with Unity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;IronSource / AdMob&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Ad mediation&lt;/td&gt;
&lt;td&gt;Revenue share only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;PlayFab&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Player accounts, leaderboards, economy&lt;/td&gt;
&lt;td&gt;100K MAU free&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Discord&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Community management&lt;/td&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;GitHub Actions&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CI/CD for automated builds&lt;/td&gt;
&lt;td&gt;2,000 mins/month free&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This entire stack costs nothing until you reach a scale where you can afford to pay. And by the time you hit PlayFab's 100K MAU limit, your game is generating enough revenue to cover the upgrade.&lt;/p&gt;

&lt;h3&gt;
  
  
  When to Invest in Custom Infrastructure
&lt;/h3&gt;

&lt;p&gt;Most indie games never need custom server infrastructure. PlayFab, Firebase, and similar platforms handle the vast majority of use cases. The exceptions are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Real-time multiplayer&lt;/strong&gt; requiring authoritative servers (like Domi Online, where gameplay ran server-authoritatively on FishNet, hosted on AWS)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User-generated content systems&lt;/strong&gt; that require content moderation and storage&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Competitive ranked modes&lt;/strong&gt; requiring anti-cheat and server-side validation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your game falls into one of these categories, budget for server costs from the start. We cover this in our &lt;a href="https://oceanviewgames.co.uk/services/gamedevelopment?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;Unity game development services&lt;/a&gt; overview.&lt;/p&gt;




&lt;h2&gt;
  
  
  Measuring What Matters
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Three Metrics That Drive Indie LiveOps
&lt;/h3&gt;

&lt;p&gt;With limited analytics resources, focus on three metrics:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Day-1 / Day-7 / Day-30 Retention&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Retention tells you whether players are finding a reason to come back, but there is no single healthy percentage across every genre, audience, acquisition channel, or business model. Establish your own baseline and segment it by version, platform, acquisition source, and player cohort.&lt;/p&gt;

&lt;p&gt;The most useful question is not "are we above an industry benchmark?" but "where are players leaving, and did the change we shipped improve that cohort?" If most new players leave before they reach the core loop, fix onboarding before investing heavily in LiveOps.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. ARPDAU (Average Revenue Per Daily Active User)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This tells you how much revenue the active audience generates on average. Do not use one generic ARPDAU target across genres: compare cohorts over time, separate ads from IAP, and correlate movements with content updates, events, pricing changes, and acquisition mix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Session Length and Frequency&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;How long do players play per session, and how many sessions per day? Increasing session frequency (from once a day to twice a day) is often easier and more valuable than increasing session length. This is where daily challenges, login rewards, and energy systems earn their place.&lt;/p&gt;




&lt;h2&gt;
  
  
  A Realistic LiveOps Timeline for Indie Studios
&lt;/h2&gt;

&lt;p&gt;Here is a phased approach that assumes a team of 2-5 developers:&lt;/p&gt;

&lt;h3&gt;
  
  
  Months 1-3 Post-Launch: Stabilise
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Fix critical bugs reported by early players&lt;/li&gt;
&lt;li&gt;Monitor retention metrics and identify the biggest drop-off points&lt;/li&gt;
&lt;li&gt;Implement basic analytics if not already in place&lt;/li&gt;
&lt;li&gt;Engage with your early community and gather feedback&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Months 4-6: Optimise
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Run your first A/B test (start with ad frequency or a reward amount)&lt;/li&gt;
&lt;li&gt;Launch your first seasonal event&lt;/li&gt;
&lt;li&gt;Implement a daily challenge or daily reward system&lt;/li&gt;
&lt;li&gt;Begin a regular communication cadence with your community&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Months 7-12: Scale
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Refine your content calendar based on what worked&lt;/li&gt;
&lt;li&gt;Add a second monetisation mechanic (if you started with ads, consider adding IAPs)&lt;/li&gt;
&lt;li&gt;Build automated systems (rotating shops, procedural challenges) to reduce manual content creation&lt;/li&gt;
&lt;li&gt;Evaluate whether your player base supports investing in custom infrastructure&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  The Bottom Line
&lt;/h2&gt;

&lt;p&gt;Effective LiveOps is not about doing everything a large studio does, but smaller. It is about identifying the &lt;strong&gt;highest-impact activities for your specific game and player base&lt;/strong&gt; and executing them consistently with the resources you have.&lt;/p&gt;

&lt;p&gt;Start with retention. If players are not coming back, no amount of events or monetisation tuning will save the game. Once retention is healthy, layer in monetisation optimisation. Then scale content production through automation and community engagement.&lt;/p&gt;

&lt;p&gt;Many tools offer entry-level plans, but pricing and quotas change. The data is available. The only resource you cannot manufacture is time - so spend it on the things that move the metrics that matter.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/gamedevelopment?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;Unity Game Development Services&lt;/a&gt; - Our full-cycle development capabilities, including LiveOps architecture&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/monetization?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;Game Monetisation Services&lt;/a&gt; - How we design and implement sustainable revenue strategies&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/startups?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;Games for Startups and Indie Studios&lt;/a&gt; - How we work with indie teams to maximise limited budgets&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-monetisation-strategy?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=liveops-indie-studios" rel="noopener noreferrer"&gt;Monetisation Strategy Picker&lt;/a&gt; - Find the right monetisation model for your live-service game.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Alternatives to Upwork Unity Developers</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Tue, 20 Oct 2026 07:37:52 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/alternatives-to-upwork-unity-developers-fo5</link>
      <guid>https://dev.to/oceanviewgames/alternatives-to-upwork-unity-developers-fo5</guid>
      <description>&lt;p&gt;If you need a Unity developer and you're wary of &lt;a href="https://www.upwork.com" rel="noopener noreferrer"&gt;Upwork&lt;/a&gt;, these are the main alternatives:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Other freelance marketplaces&lt;/strong&gt; such as &lt;a href="https://www.peopleperhour.com" rel="noopener noreferrer"&gt;PeoplePerHour&lt;/a&gt; and &lt;a href="https://www.yunojuno.com" rel="noopener noreferrer"&gt;YunoJuno&lt;/a&gt; in the UK, or &lt;a href="https://pro.fiverr.com" rel="noopener noreferrer"&gt;Fiverr Pro&lt;/a&gt; and &lt;a href="https://www.freelancer.com" rel="noopener noreferrer"&gt;Freelancer.com&lt;/a&gt;, which work much like Upwork&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vetted talent networks&lt;/strong&gt; such as &lt;a href="https://www.toptal.com" rel="noopener noreferrer"&gt;Toptal&lt;/a&gt; and &lt;a href="https://arc.dev" rel="noopener noreferrer"&gt;Arc&lt;/a&gt;, which screen developers before you see them&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Games job boards&lt;/strong&gt; such as &lt;a href="https://www.workwithindies.com" rel="noopener noreferrer"&gt;Work With Indies&lt;/a&gt; and &lt;a href="https://hitmarker.net" rel="noopener noreferrer"&gt;Hitmarker&lt;/a&gt;, which reach people who already work in games&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a href="https://www.linkedin.com" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;&lt;/strong&gt;, for direct outreach to developers with a visible work history&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review directories&lt;/strong&gt; such as &lt;a href="https://clutch.co" rel="noopener noreferrer"&gt;Clutch&lt;/a&gt;, where studios are listed with reviews from their clients&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A co-development studio&lt;/strong&gt; such as &lt;a href="https://oceanviewgames.co.uk/services/codevelopment?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Ocean View Games&lt;/a&gt; (London), when you need senior Unity engineers, continuity and someone accountable for the result&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The rest of this post explains when each one makes sense, the warning signs to look for in a Unity project, and when Upwork is still the right choice.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why I'm Writing This
&lt;/h2&gt;

&lt;p&gt;I've been on Upwork since 2020 and have completed &lt;a href="https://www.upwork.com/freelancers/~01a442546a3e86db9b" rel="noopener noreferrer"&gt;45 jobs there, with 100% Job Success and a Top Rated badge&lt;/a&gt;. The work covered full games, porting, bug fixing and technical advice. That track record is mine personally, built alongside running Ocean View Games.&lt;/p&gt;

&lt;p&gt;I'm not planning to take new work through Upwork, but this isn't a post about why the platform is bad. It does some things very well. It also has one structural weakness that matters a lot when you're hiring for something as technical as Unity development, and you should understand it before you post a job.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Upwork Does Well
&lt;/h2&gt;

&lt;p&gt;If you've never hired a developer before, Upwork lowers the risk of working with a stranger.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Payment protection.&lt;/strong&gt; On fixed-price contracts, you fund each milestone in advance and Upwork holds the money until you approve the work. You can request changes before releasing payment.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hourly tracking.&lt;/strong&gt; On hourly contracts, time is logged through Upwork's desktop app, which records activity and takes periodic screenshots. You can review hours before they're paid and dispute them within a set window.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Admin handled for you.&lt;/strong&gt; Contracts, invoicing and payments all go through the platform, so you're not chasing paperwork with someone in another country.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A public track record.&lt;/strong&gt; Job Success scores and client feedback give you something to go on, which is more than a cold email gives you.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a nervous first-time client with a small, well-defined task, that safety net is worth a lot.&lt;/p&gt;




&lt;h2&gt;
  
  
  Where It Goes Wrong
&lt;/h2&gt;

&lt;p&gt;Upwork is open to the world. There is no technical bar to clear before someone can describe themselves as a Unity developer and bid on your project.&lt;/p&gt;

&lt;p&gt;That creates three problems:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Skill is hard to judge from a profile.&lt;/strong&gt; There are many unskilled developers on the platform, and a confident proposal looks the same whether or not the person behind it can deliver.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scams happen.&lt;/strong&gt; Fake profiles, copied portfolios and people misrepresenting their experience are a real risk, and payment protection doesn't recover the weeks you lose.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unity problems surface late.&lt;/strong&gt; A Unity project can look fine in a demo and still be built on code and assets that fall apart as the game grows. By the time bugs and performance issues appear, much of the budget has gone.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  A Real Example
&lt;/h3&gt;

&lt;p&gt;A client contacted me on Upwork because something felt wrong. He'd hired another freelancer for a Unity app, communication had become difficult, and he'd already put around £20,000 into the project. He asked me to look over the code and give him an honest opinion.&lt;/p&gt;

&lt;p&gt;It didn't take long. The project had hard-coded values throughout, no structure that would let it grow or change, and expensive code running constantly. The art was a mix of clashing styles, with high and low polygon models side by side. In my view, he wasn't getting what he had paid for.&lt;/p&gt;

&lt;p&gt;I told him plainly that I would start again rather than build on it. He let the freelancer go that same day, and the freelancer didn't dispute it; he simply disappeared. I rebuilt the project, we released it, and he became a very happy client.&lt;/p&gt;

&lt;p&gt;The original freelancer passed every check Upwork offers. The problems were in the code and assets, which no profile shows you.&lt;/p&gt;




&lt;h2&gt;
  
  
  Red Flags in a Unity Project
&lt;/h2&gt;

&lt;p&gt;These are the warning signs I saw in that project, and they come up again and again when I'm asked to review someone else's work. You don't need to read code to ask about them.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Hard-coded values everywhere.&lt;/strong&gt; Prices, speeds, text and level data written directly into the code, so every small change needs a developer and a new build.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No modularity.&lt;/strong&gt; Systems tangled together so that changing one thing breaks another. It works today and becomes slower and riskier to change every week.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expensive work running every frame.&lt;/strong&gt; Code doing heavy work dozens of times a second when it only needs to happen occasionally. It's a common cause of poor performance, battery drain and overheating on phones.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fighting the engine.&lt;/strong&gt; Writing plain C# isn't a problem in itself, but a developer who rebuilds things Unity already provides, or ignores tools such as ScriptableObjects and prefabs, is usually creating extra work and extra bugs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mismatched art.&lt;/strong&gt; Assets in different styles, with very high and very low polygon counts mixed together. It looks unprofessional and hurts performance, and usually means assets were collected rather than planned.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Poor communication.&lt;/strong&gt; Vague progress updates and builds you can't run yourself are often the first sign, well before the technical problems show.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you recognise several of these in a project you've inherited, get it reviewed before paying for new features.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Alternatives Available in the UK
&lt;/h2&gt;

&lt;p&gt;I haven't hired through every option below myself, so for the platforms I've stuck to what they say about how they work. Details were last checked in October 2026; check current terms and fees before you sign up, as these change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Other Freelance Marketplaces: PeoplePerHour, YunoJuno, Fiverr Pro and Freelancer.com
&lt;/h3&gt;

&lt;p&gt;These work much like Upwork: you post a job or browse profiles, and the platform handles the agreement and the payment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;PeoplePerHour&lt;/strong&gt; is a UK-based marketplace. &lt;a href="https://www.peopleperhour.com/static/how-it-works-buyer" rel="noopener noreferrer"&gt;Its guide for buyers&lt;/a&gt; says your money is held in escrow once you accept a freelancer's proposal, and is released when you pay the freelancer's invoice for the finished work. If you're not happy, you can raise a dispute instead.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;YunoJuno&lt;/strong&gt; is a UK platform for booking freelancers. &lt;a href="https://www.yunojuno.com/ir35-compliance" rel="noopener noreferrer"&gt;It says it completes IR35 status determinations&lt;/a&gt;, keeps a record of each decision and the reasoning behind it, and provides insurance on IR35 bookings. There's more on IR35 below.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fiverr Pro&lt;/strong&gt; is the part of Fiverr where freelancers have been &lt;a href="https://help.fiverr.com/hc/en-us/articles/29453184449169-How-Fiverr-Pro-for-freelancers-work" rel="noopener noreferrer"&gt;vetted by Fiverr's own team&lt;/a&gt;. &lt;strong&gt;Freelancer.com&lt;/strong&gt; is a global marketplace whose &lt;a href="https://www.freelancer.com/community/articles/the-lowdown-on-milestone-payments" rel="noopener noreferrer"&gt;Milestone Payments&lt;/a&gt; hold your money until you release it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best for:&lt;/strong&gt; small, well-defined tasks where you want the platform to hold the payment, or, with YunoJuno, booking an individual UK contractor with the IR35 paperwork handled.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; none of these tests game development skills specifically, so you still need to vet Unity experience yourself using the questions further down.&lt;/p&gt;

&lt;h3&gt;
  
  
  Vetted Talent Networks: Toptal and Arc
&lt;/h3&gt;

&lt;p&gt;These networks screen developers before clients ever see them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Toptal&lt;/strong&gt; describes &lt;a href="https://www.toptal.com/top-3-percent" rel="noopener noreferrer"&gt;a screening process&lt;/a&gt; covering language and personality, an in-depth skill review, live screening and test projects, and says typically fewer than 3% of applicants are accepted. The process takes weeks, which tells you it's more than a profile check.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Arc&lt;/strong&gt; offers vetted freelance and full-time developers, and &lt;a href="https://arc.dev" rel="noopener noreferrer"&gt;says its candidates are vetted&lt;/a&gt; for domain expertise and English fluency.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best for:&lt;/strong&gt; companies hiring an individual engineer who will work inside their own team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; general screening tests software engineering, not game development. A strong web developer can pass and still have never built a Unity game. Use the questions further down to check for game experience.&lt;/p&gt;

&lt;h3&gt;
  
  
  Games Job Boards: Work With Indies and Hitmarker
&lt;/h3&gt;

&lt;p&gt;These boards are used by people who already work in games, so you skip the general freelancers who bid on everything. Hitmarker is a UK company, founded in Newcastle, and lists games and esports roles worldwide.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best for:&lt;/strong&gt; contract or permanent hires where game experience matters more than platform safeguards.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; there's no escrow or payment protection, so you handle contracts and payment yourself.&lt;/p&gt;

&lt;h3&gt;
  
  
  LinkedIn
&lt;/h3&gt;

&lt;p&gt;LinkedIn lets you search for developers by the studios and games they've worked on, and approach them directly. Work history there is public and easier to check against real projects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best for:&lt;/strong&gt; finding experienced developers who aren't actively bidding on freelance platforms.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; the best developers on LinkedIn are often employed, so expect a slower process and plenty of polite declines.&lt;/p&gt;

&lt;h3&gt;
  
  
  Review Directories: Clutch
&lt;/h3&gt;

&lt;p&gt;If you'd rather hire a team than an individual, Clutch lists studios with reviews gathered from their clients. You use it to research and shortlist, then contact the studios directly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best for:&lt;/strong&gt; projects big enough that you want a company, not a person, accountable for delivery.&lt;/p&gt;

&lt;p&gt;You can see how this works on &lt;a href="https://clutch.co/profile/ocean-view-games" rel="noopener noreferrer"&gt;our own Clutch profile&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; a directory is a starting point, not a guarantee. Read the reviews for projects similar to yours and still ask to see their work.&lt;/p&gt;

&lt;h3&gt;
  
  
  A Co-Development Studio
&lt;/h3&gt;

&lt;p&gt;A co-development studio provides senior engineers who either build the game for you or work inside your existing team. This is what we do at Ocean View Games: you speak to the engineer doing the work throughout, not to an account manager. Ocean View Games is a London-based Unity studio, and I lead it as a Unity Certified Expert and former Jagex developer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Best for:&lt;/strong&gt; projects where architecture, performance or a launch deadline matters, and where you need the same people from start to finish.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; you pay for senior experience, so it isn't the cheapest route for small tasks. For a comparison of costs and trade-offs, see &lt;a href="https://oceanviewgames.co.uk/blog/posts/co-development-vs-freelancers-vs-hiring?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Co-Development vs Freelancers vs Full-Time Hires&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Hiring a Unity Developer in the UK
&lt;/h2&gt;

&lt;p&gt;If you're hiring from the UK, a few rules and practicalities apply whichever route you take. This is a summary, not legal or tax advice.&lt;/p&gt;

&lt;h3&gt;
  
  
  IR35 and Off-Payroll Working
&lt;/h3&gt;

&lt;p&gt;Many UK contractors work through their own limited company. Under the off-payroll working rules, known as IR35, a medium or large client is responsible for deciding whether the contractor would count as an employee if they were engaged directly, and must give them a status determination statement explaining the decision. If you're a small client, you're exempt from making that decision: the contractor's own company makes it instead.&lt;/p&gt;

&lt;p&gt;Engaging a studio to deliver a defined service under a business-to-business contract is generally a different arrangement from hiring an individual's personal services, although the terms of the contract and how the work is actually done still matter. Check the HM Revenue &amp;amp; Customs (HMRC) guidance on &lt;a href="https://www.gov.uk/guidance/understanding-off-payroll-working-ir35" rel="noopener noreferrer"&gt;understanding off-payroll working&lt;/a&gt; for your own situation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Practical Points
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Contracts under English law.&lt;/strong&gt; A UK supplier will normally contract under the law of England and Wales, so a dispute is handled in a legal system you already know.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Invoicing and payment in pounds.&lt;/strong&gt; There's no currency conversion or international transfer fee, and the price you agree is the price you pay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;VAT-registered suppliers.&lt;/strong&gt; A supplier registered for Value Added Tax (VAT) shows its VAT number on its invoices, and if your business is registered too you can usually reclaim the VAT you're charged.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A UK time zone.&lt;/strong&gt; Calls happen during your working day, and a problem raised in the morning can be looked at the same day.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Several of the options above are UK companies: PeoplePerHour and YunoJuno are based in London, and Hitmarker was &lt;a href="https://hitmarker.net/about" rel="noopener noreferrer"&gt;founded in Newcastle&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  A Quick Comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Who vets the developer&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Upwork&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;You, helped by public job history&lt;/td&gt;
&lt;td&gt;Small, well-scoped tasks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;PeoplePerHour / YunoJuno / Fiverr Pro / Freelancer.com&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;You, helped by public feedback; Fiverr Pro adds its own vetting&lt;/td&gt;
&lt;td&gt;Small tasks, and UK contractor bookings through YunoJuno&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Toptal / Arc&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The network, with general engineering screening&lt;/td&gt;
&lt;td&gt;Individual engineers joining your team&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Games job boards&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;You&lt;/td&gt;
&lt;td&gt;Contract or permanent game hires&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;LinkedIn&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;You, helped by public work history&lt;/td&gt;
&lt;td&gt;Experienced developers not on freelance sites&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Clutch&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Client reviews&lt;/td&gt;
&lt;td&gt;Shortlisting studios&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Co-development studio (e.g. Ocean View Games)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Their portfolio and client track record&lt;/td&gt;
&lt;td&gt;Larger or technically risky projects&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Upwork, PeoplePerHour, Fiverr and Freelancer.com all hold your payment until you approve the work or release it. With job boards, LinkedIn and studios, your protection comes from the contract you sign and paying against milestones.&lt;/p&gt;




&lt;h2&gt;
  
  
  Questions to Ask Before You Hire
&lt;/h2&gt;

&lt;p&gt;Technical quiz questions don't tell you much any more. Anyone can paste them into an AI and read back a convincing answer. What an AI can't do is talk about work the developer has actually done, or show they understand your product. Ask about them, not about trivia.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. "What have you built?"&lt;/strong&gt;&lt;br&gt;
It doesn't need to be a fully released game. A prototype, a game jam entry or a personal project all count. A good answer is something you can see or play, with a clear explanation of which parts they built themselves.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. "Walk me through a decision you made on that project. What were the pros and cons?"&lt;/strong&gt;&lt;br&gt;
A good developer can explain why they chose one approach over another and what they gave up. If they can only describe what they did, not why, be wary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. "What would you do differently if you built it again?"&lt;/strong&gt;&lt;br&gt;
Experienced developers always have an answer, because every project teaches you something. "Nothing" is a red flag.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. "Tell me back what you think I'm building, and who it's for."&lt;/strong&gt;&lt;br&gt;
Before any work starts, they should be able to explain your product in their own words. If they can't, the code they write won't fit what you need.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. "How will I see progress, and how often?"&lt;/strong&gt;&lt;br&gt;
You want builds you can run yourself at regular points, not just screenshots and status messages.&lt;/p&gt;

&lt;p&gt;Alongside the conversation, protect yourself with the basics:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Pay against milestones,&lt;/strong&gt; each with something you can run and test.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Insist on version control from day one,&lt;/strong&gt; in a repository you own, so the project is never held hostage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Get IP ownership in writing.&lt;/strong&gt; The contract should assign the code and assets to you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;If you've inherited a project, get it reviewed before adding features.&lt;/strong&gt; A &lt;a href="https://oceanviewgames.co.uk/services/technical-audit?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Unity technical audit&lt;/a&gt; tells you what you've actually got, so you're not paying for features on top of foundations that won't hold.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  When Upwork Is Still the Right Choice
&lt;/h2&gt;

&lt;p&gt;Use Upwork when the task is small and clearly defined, such as fixing a specific bug, integrating an SDK or getting a second opinion on a technical decision. Use it when you're new to hiring and the payment protection matters more to you than anything else, and when you're prepared to vet candidates yourself using the questions above.&lt;/p&gt;

&lt;p&gt;Look elsewhere when the project is large, when the architecture needs to last, when there's a launch date you can't move, or when you need the same experienced people from start to finish.&lt;/p&gt;

&lt;p&gt;If you're weighing up budgets across these options, our &lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;game development cost guide&lt;/a&gt; covers typical project ranges and what drives them.&lt;/p&gt;




&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What are the best alternatives to Upwork for hiring Unity developers in the UK?
&lt;/h3&gt;

&lt;p&gt;PeoplePerHour and YunoJuno are UK-based freelance platforms, while Toptal and Arc offer individual engineers who have been screened in advance. Games job boards such as Hitmarker and Work With Indies reach people who already work in games, and Clutch helps you shortlist studios. For larger or technically risky projects, a UK co-development studio such as Ocean View Games gives you senior engineers who stay with the project from start to finish.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Upwork good for hiring Unity developers?
&lt;/h3&gt;

&lt;p&gt;It can be. Upwork's payment protection and public feedback make it a reasonable choice for small, well-defined Unity tasks. The weakness is that there's no technical bar to joining, so the quality of developers varies widely and you have to vet them yourself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Upwork safe for hiring a developer?
&lt;/h3&gt;

&lt;p&gt;Upwork's escrow on fixed-price milestones and its hourly tracking protect your money, provided you keep payments and communication on the platform. They don't protect you from hiring someone who can't do the job, and that's the bigger risk on technical work.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I check that a Unity developer is genuine?
&lt;/h3&gt;

&lt;p&gt;Ask to see something they've built, then get them to talk through the decisions they made on it and what they'd change. Technical quiz questions are less useful now, because answers can be looked up with AI. A developer who has really done the work can discuss it in detail.&lt;/p&gt;

&lt;h3&gt;
  
  
  What are the warning signs of a badly built Unity project?
&lt;/h3&gt;

&lt;p&gt;Hard-coded values throughout, systems that can't be changed without breaking something else, heavy code running every frame, art in mismatched styles and polygon counts, and progress updates without builds you can run yourself.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I hire a freelancer or a studio for my Unity game?
&lt;/h3&gt;

&lt;p&gt;A freelancer suits a small, well-scoped task or extra capacity on a team that already has technical leadership. A studio suits larger projects where you need senior architecture decisions, continuity and someone accountable for delivery.&lt;/p&gt;

&lt;h3&gt;
  
  
  What can I do if my Upwork developer left my Unity project unfinished?
&lt;/h3&gt;

&lt;p&gt;Get the project reviewed before adding anything new, so you know whether to fix it or rebuild parts of it. Our &lt;a href="https://oceanviewgames.co.uk/services/project-rescue?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Unity project rescue and takeover&lt;/a&gt; service covers this, starting with an assessment of the code and assets you have.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/blog/posts/co-development-vs-freelancers-vs-hiring?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Co-Development vs Freelancers vs Full-Time Hires&lt;/a&gt; - How the main hiring models compare for game studios&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/choosing-a-game-development-studio?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Choosing a Game Development Studio&lt;/a&gt; - What to look for when hiring a team&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/blog/posts/how-to-write-game-development-brief?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;How to Write a Game Development Brief That Gets Accurate Quotes&lt;/a&gt; - Get better proposals, wherever you hire&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/project-rescue?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=alternatives-to-upwork-unity-developers" rel="noopener noreferrer"&gt;Unity Project Rescue and Takeover&lt;/a&gt; - For projects another developer left unfinished&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Gamification in Corporate Training: Beyond Compliance Checkboxes</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Tue, 13 Oct 2026 02:25:40 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/gamification-in-corporate-training-beyond-compliance-checkboxes-142k</link>
      <guid>https://dev.to/oceanviewgames/gamification-in-corporate-training-beyond-compliance-checkboxes-142k</guid>
      <description>&lt;p&gt;A common failure mode in corporate e-learning is optimising for completion rather than competence. Employees click through slides, pass a short quiz, and the LMS records that training happened. That proves attendance; it does not necessarily prove that somebody can make the right decision when the real situation appears.&lt;/p&gt;

&lt;p&gt;The problem is often not the employee. Some courses have been designed primarily to demonstrate completion rather than assess how learning is applied. When the primary goal is "prove that employees saw this content," the result can be passive learning with little opportunity to practise.&lt;/p&gt;

&lt;p&gt;Game-based learning can offer a different approach. Instead of asking employees to absorb information, it asks them to &lt;strong&gt;make decisions, face consequences, and adapt their behaviour&lt;/strong&gt; - the same cognitive processes that drive real-world performance. This post focuses on game-based learning through interactive scenarios. Gamification can add elements such as points or rewards to existing training, while game-based learning uses the activity itself to practise decisions. Both can have a role, but they are not the same thing.&lt;/p&gt;




&lt;h2&gt;
  
  
  Where Traditional E-Learning Can Fall Short
&lt;/h2&gt;

&lt;p&gt;Before examining the solution, it is worth understanding exactly why the current approach underperforms.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Passive Consumption Problem
&lt;/h3&gt;

&lt;p&gt;Traditional e-learning often follows a pattern: read content, watch a video, answer multiple-choice questions. That can be useful for checking recognition, but many workplace tasks require recall, judgement, and application under imperfect conditions. If the training never asks learners to practise those decisions, the assessment may be measuring the wrong thing.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Compliance Trap
&lt;/h3&gt;

&lt;p&gt;When training exists primarily to satisfy regulatory requirements, the incentive structure is backwards. The organisation wants proof of completion, not proof of competence. Employees learn that the fastest path through is to click "Next" repeatedly, skim the quiz questions, and move on. The LMS records a completion. Everybody is satisfied, and nobody has learned anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Context Gap
&lt;/h3&gt;

&lt;p&gt;Real workplace decisions happen under pressure, with incomplete information, and with consequences for getting it wrong. A multiple-choice question about data protection policy bears no resemblance to the actual moment when an employee must decide whether to share a file externally. Without contextual practice, knowledge remains abstract and inapplicable.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Game-Based Corporate Training Actually Looks Like
&lt;/h2&gt;

&lt;p&gt;Badges and leaderboards are examples of gamification, but they cannot replace useful practice on their own. For the situations discussed here, we mean &lt;strong&gt;designing game-based training around interactive decision-making&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Scenario-Based Simulations
&lt;/h3&gt;

&lt;p&gt;The most effective corporate training games place employees inside realistic workplace scenarios and ask them to make decisions. Consider these examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Compliance training&lt;/strong&gt;: Instead of reading about data handling policies, the employee manages a simulated inbox where they must identify phishing attempts, classify documents by sensitivity, and decide when to escalate a potential breach. Wrong decisions trigger realistic consequences - a simulated data leak, a regulatory inquiry, a news headline&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Customer service training&lt;/strong&gt;: The employee handles a series of increasingly difficult customer interactions, choosing from dialogue options and observing how the conversation unfolds based on their choices&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Safety training&lt;/strong&gt;: Workers navigate a virtual environment identifying hazards, choosing corrective actions, and managing time pressure - simulating the cognitive load of a real work environment&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Onboarding&lt;/strong&gt;: New hires explore a simulated version of company systems and processes, completing tasks that mirror their actual first-week responsibilities&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In each case, the employee is &lt;strong&gt;actively engaging with the material&lt;/strong&gt; rather than passively observing it. This is the critical distinction.&lt;/p&gt;

&lt;h3&gt;
  
  
  Branching Decision Trees
&lt;/h3&gt;

&lt;p&gt;Linear training presents the same content to everyone in the same order. Game-based training adapts based on the learner's choices. A branching decision tree allows:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Employees who demonstrate competence to progress quickly through familiar material&lt;/li&gt;
&lt;li&gt;Employees who struggle with specific topics to receive additional practice in those areas&lt;/li&gt;
&lt;li&gt;Different learning paths based on role, department, or experience level&lt;/li&gt;
&lt;li&gt;Multiple outcomes that show how different decisions lead to different results&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This approach respects the employee's time while ensuring that everyone achieves the required level of competence.&lt;/p&gt;

&lt;h3&gt;
  
  
  Decision-Quality Scoring
&lt;/h3&gt;

&lt;p&gt;Traditional training uses binary pass/fail assessment. You either answered the question correctly or you did not. Game-based training can be designed to record more aspects of decisions, where appropriate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Speed&lt;/strong&gt;: How quickly did the employee identify the correct course of action?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accuracy&lt;/strong&gt;: Did they make the right call?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reasoning, if captured&lt;/strong&gt;: Can learners explain their choice, or does the scenario record enough steps to analyse the route they took?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Consistency&lt;/strong&gt;: Do they make the same types of errors repeatedly?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Improvement&lt;/strong&gt;: How does performance change across repeated scenarios?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This may reveal patterns that one score misses, although collecting extra data is only worthwhile if someone can act on it.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Game-based training can give learners opportunities to practise decisions in realistic scenarios. The game mechanic is not the point - the decision-making practice is the point.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Measurable Outcomes: What L&amp;amp;D Teams Should Measure
&lt;/h2&gt;

&lt;p&gt;The case for scenario-based training should rest on results that can be measured against an existing approach, not on an assumption that it will always be more engaging or effective.&lt;/p&gt;

&lt;h3&gt;
  
  
  Completion Rates
&lt;/h3&gt;

&lt;p&gt;Completion rate is worth measuring, but it should be measured against your existing course rather than against a generic benchmark. If a scenario-based module improves completion, that is useful; if completion rises but decision quality does not, the redesign has not solved the real problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  Knowledge Retention
&lt;/h3&gt;

&lt;p&gt;Game-based training can be designed around learning techniques such as retrieval practice, spaced repetition, and repeated decision-making rather than relying only on passive presentation. Useful patterns include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Retrieval practice&lt;/strong&gt;: Forcing the learner to recall information rather than recognise it&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Spaced repetition&lt;/strong&gt;: Revisiting concepts at increasing intervals&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interleaving&lt;/strong&gt;: Mixing different types of problems rather than grouping them by topic&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Desirable difficulty&lt;/strong&gt;: Making tasks challenging enough to require effort without being frustrating&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Time-to-Competency
&lt;/h3&gt;

&lt;p&gt;How long does it take a new hire to become productive? A well-designed simulation may help improve this metric by letting employees practise real workflows in a safe environment before they encounter them on the job. Mistakes in a well-contained simulation avoid many of the risks of learning on the job. Mistakes made with real customers or real data cost real money.&lt;/p&gt;

&lt;h3&gt;
  
  
  Behavioural Change
&lt;/h3&gt;

&lt;p&gt;The ultimate measure of training effectiveness is not what employees know but what they do differently. Game-based training with scenario-based decision-making can provide practice closer to workplace tasks, but any improvement in real behaviour still needs to be tested.&lt;/p&gt;




&lt;h2&gt;
  
  
  Building the Business Case: ROI Metrics for Leadership
&lt;/h2&gt;

&lt;p&gt;L&amp;amp;D teams often struggle to justify training investments because the benefits are intangible. Scenario-based training can capture more detailed learning data, but connecting that data to business outcomes requires evaluation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Direct Cost Savings
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Potentially fewer compliance incidents&lt;/strong&gt;: Compare incident rates before and after training, while allowing for other changes that may affect the result&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Potentially lower onboarding costs&lt;/strong&gt;: Measure whether new starters reach agreed competency milestones sooner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Possible retention benefits&lt;/strong&gt;: If employee retention is part of the business case, measure it rather than assuming training alone will reduce turnover&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Potentially fewer training hours&lt;/strong&gt;: Check whether adaptive routes save staff time without weakening learning outcomes&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Measurable Learning Metrics
&lt;/h3&gt;

&lt;p&gt;Depending on their design, interactive training systems may capture additional analytics, including:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Competency heat maps&lt;/strong&gt; - which departments or roles struggle with which topics?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decision-pattern analysis&lt;/strong&gt; - are specific types of errors systemic across the organisation?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Time-to-mastery curves&lt;/strong&gt; - how does learning speed vary across cohorts?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Retention decay rates&lt;/strong&gt; - how quickly does performance degrade without refresher training?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If these measures are collected reliably and interpreted alongside other evidence, they can help L&amp;amp;D teams decide where training needs attention.&lt;/p&gt;

&lt;h3&gt;
  
  
  The ROI Formula
&lt;/h3&gt;

&lt;p&gt;A practical framework for calculating game-based training ROI:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Cost of current training&lt;/strong&gt;: Development time + delivery time + employee hours spent + LMS licensing&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cost of training failures&lt;/strong&gt;: Compliance incidents, onboarding delays, performance errors attributable to training gaps&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cost of game-based solution&lt;/strong&gt;: Development investment + platform costs + ongoing content updates&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Projected improvements&lt;/strong&gt;: Set conservative targets against your own baseline, then validate them with a pilot before extrapolating across the organisation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Whether the investment pays back depends on the cost of the problem you are solving. A pilot gives you the evidence to calculate payback using your own incident rates, onboarding time, learner hours, and support costs instead of relying on a generic ROI promise.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Frame the business case around cost avoidance and productivity gains, not engagement scores. Leadership cares about reduced incidents, faster onboarding, and measurable competency - not completion certificates.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Implementation Considerations
&lt;/h2&gt;

&lt;h3&gt;
  
  
  LMS Integration
&lt;/h3&gt;

&lt;p&gt;An LMS connection may be essential for some training projects, but it is not automatic. Requirements depend on the platform, reporting needs and IT constraints. Before commissioning development, confirm whether SCORM, xAPI, an LMS-specific API or a simpler reporting approach is appropriate. Integration requirements should be confirmed during discovery; they need suitable implementation and testing before a delivery commitment.&lt;/p&gt;

&lt;h3&gt;
  
  
  Multi-Device Deployment
&lt;/h3&gt;

&lt;p&gt;Corporate training reaches employees on desktops, tablets, and mobile phones. Field workers, remote employees, and office staff all need access. We build responsive, cross-platform experiences using Unity that adapt to the target device - touch-optimised interfaces for tablets and phones, keyboard/mouse support for desktops.&lt;/p&gt;

&lt;h3&gt;
  
  
  Content Update Pipelines
&lt;/h3&gt;

&lt;p&gt;Regulations change. Products update. Processes evolve. A training game that requires a full redevelopment every time the content changes is not sustainable.&lt;/p&gt;

&lt;p&gt;One useful design option is to separate editable learning content from the application logic so teams can update material without needing a full rebuild every time. Data-driven architectures separate content from logic, meaning your team can modify training scenarios through a spreadsheet or CMS rather than requesting a development sprint.&lt;/p&gt;

&lt;h3&gt;
  
  
  Enterprise Security
&lt;/h3&gt;

&lt;p&gt;Corporate training handles employee data and potentially sensitive business processes. Security, hosting, personal data and authentication requirements must be scoped with the commissioning organisation. SSO, on-premise hosting and data-handling arrangements are not assumed capabilities or automatic features; they need technical and legal review before being promised.&lt;/p&gt;




&lt;h2&gt;
  
  
  From Our Experience: Lessons in Educational Game Design
&lt;/h2&gt;

&lt;p&gt;Our work in &lt;a href="https://oceanviewgames.co.uk/services/educationalgames?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;educational game development&lt;/a&gt; has taught us principles that apply directly to corporate training:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When we partnered with The Language Conservancy to build Vocab Builder - a suite of 9 mini-games for language preservation - we learned that &lt;strong&gt;every game mechanic must serve a specific learning objective&lt;/strong&gt;. The same principle applies to corporate training: the game mechanic is the vehicle, not the destination&lt;/li&gt;
&lt;li&gt;Our data-driven asset pipeline approach (originally designed so linguistic experts could add new languages without developer involvement) translates directly to corporate content management, where L&amp;amp;D teams need to update training material independently&lt;/li&gt;
&lt;li&gt;Focus testing with real learners - a core part of our &lt;a href="https://oceanviewgames.co.uk/services/gamedesign?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;game design&lt;/a&gt; process - is equally critical for corporate training. Employees will tell you what feels patronising, what feels confusing, and what actually teaches them something&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These principles, combined with our experience designing games that balance engagement with measurable outcomes, form a useful principle when planning an interactive training project.&lt;/p&gt;




&lt;h2&gt;
  
  
  Getting Started
&lt;/h2&gt;

&lt;p&gt;If your organisation is considering game-based training, here are the first steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Identify one high-impact training programme&lt;/strong&gt; that currently underperforms. Compliance training is often the best starting point because the costs of failure are quantifiable&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Define success metrics before development begins&lt;/strong&gt;. What does "better" look like - higher completion rates, fewer incidents, faster onboarding, or all three?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Start with a pilot&lt;/strong&gt;. Build a single training module as a proof of concept, measure the results against your existing approach, and use the data to build the business case for broader adoption&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose a development partner with educational game expertise&lt;/strong&gt;. Generic app developers build games. Specialist studios build learning experiences that happen to be games. The distinction matters&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/corporate-training?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;Corporate Training Industry Page&lt;/a&gt; - How we approach gamified learning for enterprise L&amp;amp;D teams&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/educationalgames?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;Educational Game Development Services&lt;/a&gt; - Our methodology for building games that teach&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/gamedesign?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;Game Design Services&lt;/a&gt; - From concept to Game Design Document&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;Game Development Cost Estimator&lt;/a&gt; - Estimate costs for training game development.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-brief-builder?utm_source=devto&amp;amp;utm_medium=syndication&amp;amp;utm_campaign=gamification-corporate-training" rel="noopener noreferrer"&gt;Game Development Brief Builder&lt;/a&gt; - Structure your training game requirements.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>5 Signs You Need a Co-Development Partner</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Mon, 05 Oct 2026 20:23:39 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/5-signs-you-need-a-co-development-partner-k65</link>
      <guid>https://dev.to/oceanviewgames/5-signs-you-need-a-co-development-partner-k65</guid>
      <description>&lt;p&gt;Nobody starts a game studio planning to ask for help. You build your team, define your vision, and set out to deliver something great. But game development is unpredictable. Scope creeps. Key people leave. Publisher milestones arrive faster than anticipated. Technical challenges turn out to be harder than the prototype suggested.&lt;/p&gt;

&lt;p&gt;At some point, many studios face a critical decision: do we push our existing team harder, or do we bring in external support?&lt;/p&gt;

&lt;p&gt;The answer is not always obvious. Asking for help too early wastes money. Asking too late puts the project at risk. At Ocean View Games, we operate as a &lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;co-development partner&lt;/a&gt; for studios ranging from funded startups to established mid-size teams. We have seen the patterns that indicate when a studio genuinely needs external support - and we have also seen studios bring in help they did not need.&lt;/p&gt;

&lt;p&gt;This post covers the five clearest signals that it is time to bring in a co-development partner, explains what co-development actually means (it is not outsourcing), and offers guidance on how to make the partnership work.&lt;/p&gt;




&lt;h2&gt;
  
  
  First: Co-Development Is Not Outsourcing
&lt;/h2&gt;

&lt;p&gt;These terms are used loosely in the industry, but they describe fundamentally different relationships. Understanding the distinction matters because it affects how you scope the engagement, how you manage communication, and what results you can expect.&lt;/p&gt;

&lt;h3&gt;
  
  
  Outsourcing
&lt;/h3&gt;

&lt;p&gt;Outsourcing means handing off a defined piece of work - a set of 3D character models, a batch of level designs, a completed feature - to an external team that works independently and delivers the finished product. Communication is typically at the handoff points: briefing, review, revision, delivery.&lt;/p&gt;

&lt;p&gt;Outsourcing works well for &lt;strong&gt;well-defined, self-contained deliverables&lt;/strong&gt; where the external team does not need deep context about the rest of your project.&lt;/p&gt;

&lt;h3&gt;
  
  
  Co-Development
&lt;/h3&gt;

&lt;p&gt;Co-development means embedding external developers directly into your team. They attend your stand-ups, work in your Jira, push to your repo, and follow your coding standards. From a day-to-day workflow perspective, they are indistinguishable from your internal developers.&lt;/p&gt;

&lt;p&gt;Co-development works well for &lt;strong&gt;complex, interdependent work&lt;/strong&gt; where the external team needs to understand your architecture, collaborate with your engineers in real time, and make decisions that affect other systems.&lt;/p&gt;

&lt;p&gt;For embedded engineering engagements, we use a co-development model. When we partnered with Domi Online to build their MMORPG infrastructure, we did not deliver a "networking module" in isolation. We acted as the core engineering team - building combat systems, skill progression, multiplayer networking, and environment rendering as an integrated whole. As Domi Online's CEO put it: "There would be no Domi Online without their expertise."&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Use outsourcing for well-defined, self-contained deliverables. Use co-development when the external team needs to work inside your architecture and make decisions alongside your developers.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Sign 1: You Are Missing Milestones
&lt;/h2&gt;

&lt;p&gt;This is the most visible and most urgent signal. If your team is consistently missing sprint commitments, your vertical slice date keeps slipping, or your publisher is sending increasingly concerned emails about the Alpha delivery, something has to change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why Milestones Slip
&lt;/h3&gt;

&lt;p&gt;In our experience, milestone slippage in game development usually comes from one of three root causes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Underestimated scope.&lt;/strong&gt; The feature list was defined before technical unknowns were fully understood. Networking code took three times longer than estimated. The AI system required a complete rewrite.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Technical debt compounding.&lt;/strong&gt; Early prototyping decisions ("we'll clean this up later") are now slowing every subsequent feature. Adding new content takes twice as long because it keeps breaking existing systems.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Team capacity mismatch.&lt;/strong&gt; The project plan was written for a team of eight, but attrition or hiring delays mean you are running with five.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  How Co-Development Helps
&lt;/h3&gt;

&lt;p&gt;A co-development partner provides experienced capacity much faster than the 2-3 month lead time of traditional hiring, once codebase access and onboarding are confirmed. We bring senior engineers who can navigate complex codebases and start contributing production-ready code within the first sprint.&lt;/p&gt;

&lt;p&gt;When we work as an embedded team, we adopt your sprint cadence and take ownership of specific features or backlog items. This directly reduces the load on your internal team and helps you recover missed milestones without burning out the people you already have.&lt;/p&gt;




&lt;h2&gt;
  
  
  Sign 2: You Have a Critical Skill Gap
&lt;/h2&gt;

&lt;p&gt;Game development requires a breadth of technical skills that few small or mid-sized studios have fully in-house. You might have strong gameplay programmers but nobody who owns performance, mobile platform work, legacy modernisation, build pipelines, or a difficult architectural problem that cuts across the whole project.&lt;/p&gt;

&lt;h3&gt;
  
  
  Common Skill Gaps We Fill
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Mobile performance&lt;/strong&gt; - Desktop developers moving to mobile can underestimate thermal limits, memory pressure, battery use, touch input, and device variation. These problems benefit from &lt;a href="https://oceanviewgames.co.uk/services/mobile" rel="noopener noreferrer"&gt;mobile-specific expertise&lt;/a&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Legacy code and architecture&lt;/strong&gt; - An older Unity project can be commercially valuable while still being difficult to change safely. A fresh pair of senior eyes can identify where to stabilise, refactor, or isolate risk before feature work continues.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Platform integration and porting&lt;/strong&gt; - Store SDKs, save systems, input, achievements, content delivery, and platform requirements all introduce work outside the core game loop.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Live operations and tooling&lt;/strong&gt; - Telemetry, remote configuration, content pipelines, and operational tooling require a different mindset from simply getting a build to launch.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Alternative Is Expensive
&lt;/h3&gt;

&lt;p&gt;Hiring for a specialist role can take months once sourcing, interviews, notice periods, and onboarding are included. If the gap is project-specific, a permanent hire may not be the right investment anyway. Co-development lets you add the capability for the period where it is actually needed.&lt;/p&gt;

&lt;p&gt;A co-development partner gives you access to senior specialists for the period you need them without committing to a permanent hire. There is still onboarding, but relevant experience can keep that ramp-up focused.&lt;/p&gt;




&lt;h2&gt;
  
  
  Sign 3: A Publisher Deadline Is Approaching
&lt;/h2&gt;

&lt;p&gt;Publisher relationships are built on trust, and trust is built on delivery. When you have committed to a milestone date - a vertical slice for a greenlight review, an Alpha build for a trade show, a content update for a seasonal event - missing that date has consequences beyond the immediate project.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Pressure Compounds
&lt;/h3&gt;

&lt;p&gt;Late deliveries do not just delay revenue. They erode publisher confidence, which can affect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Approval for additional funding tranches&lt;/li&gt;
&lt;li&gt;Marketing support and featuring commitments&lt;/li&gt;
&lt;li&gt;Future project greenlight decisions&lt;/li&gt;
&lt;li&gt;The overall perception of your studio as a reliable partner&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  How to Scope a Rescue Engagement
&lt;/h3&gt;

&lt;p&gt;When studios approach us with an imminent deadline, we follow a rapid triage process:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Assess the gap.&lt;/strong&gt; What specifically is not done? What is the minimum viable delivery that satisfies the milestone requirements?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Identify parallelisable work.&lt;/strong&gt; Which outstanding tasks can an external team take on without blocking your internal team?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Define integration points.&lt;/strong&gt; How will our code merge into your project? What are the coding standards, branching strategy, and review process?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Execute.&lt;/strong&gt; Once access and onboarding are sorted, we aim to be set up in your environment and pulling tickets within days rather than weeks. The exact timeline depends on how quickly access can be granted and how complex the codebase is.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The key is acting early. If you can see a deadline becoming unrealistic two months out, that is the time to engage a co-development partner - not two weeks before the due date.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; A co-development partner is most effective when engaged early enough to make a meaningful impact. The worst time to ask for help is when it is already too late.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Sign 4: Your Team Is Burning Out
&lt;/h2&gt;

&lt;p&gt;Crunch is the industry's worst-kept secret. Extended periods of overtime, weekend work, and sustained high pressure lead to reduced code quality, increased bugs, declining morale, and - ultimately - people leaving.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Hidden Cost of Burnout
&lt;/h3&gt;

&lt;p&gt;The financial impact of developer burnout is severe and often underestimated:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Attrition.&lt;/strong&gt; Replacing a senior developer carries recruitment cost, onboarding time, and a productivity gap while the replacement learns the project.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bug rates increase.&lt;/strong&gt; Tired developers write buggier code. The resulting QA burden and rework cycle further extends timelines.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decision quality degrades.&lt;/strong&gt; Architectural decisions made under sustained pressure tend to prioritise short-term expedience over long-term stability. This creates technical debt that compounds over the life of the project.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Creativity suffers.&lt;/strong&gt; Game development is a creative discipline. Exhausted teams produce safe, uninspired work. The spark that makes a game special gets ground down by sustained overwork.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  How Co-Development Relieves Pressure
&lt;/h3&gt;

&lt;p&gt;Bringing in an embedded co-development team does not add management overhead for your leads - not if the partner is experienced. Senior co-development engineers should be self-directed within your sprint framework. They take tickets, submit pull requests, and participate in reviews like any other team member.&lt;/p&gt;

&lt;p&gt;The immediate effect is that your internal team's workload drops to sustainable levels. Features that were being deferred because nobody had capacity start moving again. People get to work regular hours. Code quality improves. Morale recovers.&lt;/p&gt;

&lt;p&gt;This is not a luxury. It is a &lt;strong&gt;strategic investment in the sustainability of your team and your project&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Sign 5: You Need to Scale for Live Operations
&lt;/h2&gt;

&lt;p&gt;Shipping the game is a milestone, not the finish line. For live-service games, the real work begins at launch: daily content operations, seasonal events, server monitoring, bug fixes, platform updates, community management, and ongoing optimisation.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Live-Ops Capacity Problem
&lt;/h3&gt;

&lt;p&gt;During development, your entire team is focused on building the game. At launch, that same team needs to simultaneously:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Fix critical bugs reported by players&lt;/li&gt;
&lt;li&gt;Deploy hotfixes without introducing regressions&lt;/li&gt;
&lt;li&gt;Develop and ship the first post-launch content update&lt;/li&gt;
&lt;li&gt;Monitor server performance and scale infrastructure&lt;/li&gt;
&lt;li&gt;Respond to platform-specific issues (iOS update breaks something, Google Play policy change requires compliance updates)&lt;/li&gt;
&lt;li&gt;Begin pre-production on the next major update&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This often creates a step-change in workload just as the team is trying to stabilise the launch.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Co-Development Solution
&lt;/h3&gt;

&lt;p&gt;A common and effective pattern is to engage a co-development partner specifically for live operations support. Your internal team focuses on the next major content milestone while the co-development team handles:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Bug triage and fixing&lt;/strong&gt; - Addressing player-reported issues and crash reports&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SDK and platform updates&lt;/strong&gt; - Keeping third-party SDKs current and maintaining store compliance&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Technical debt reduction&lt;/strong&gt; - Refactoring systems that were rushed to ship, improving stability for the long term&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Seasonal content implementation&lt;/strong&gt; - Building and deploying time-limited events based on your design team's specifications&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This split allows your internal team to remain focused and creative while the live game receives the attention and stability it needs to retain players.&lt;/p&gt;




&lt;h2&gt;
  
  
  Making Co-Development Work
&lt;/h2&gt;

&lt;p&gt;Bringing in an external team is only effective if the integration is handled well. Here is what we have learned from our engagements:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Treat Them Like Internal Team Members
&lt;/h3&gt;

&lt;p&gt;The biggest mistake studios make is treating co-development partners as vendors. If your external developers are excluded from architecture discussions, design reviews, and retrospectives, they cannot make informed decisions. They end up producing code that technically meets the ticket requirements but does not align with the broader vision.&lt;/p&gt;

&lt;p&gt;Give them the same access to information, the same voice in meetings, and the same accountability as your internal developers.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Invest in Onboarding
&lt;/h3&gt;

&lt;p&gt;Even senior developers need context. Spend time walking through your architecture, explaining design intent, and sharing the unwritten conventions that every codebase accumulates. A day or two of thorough onboarding saves weeks of misalignment.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Establish Clear Code Standards
&lt;/h3&gt;

&lt;p&gt;Provide your style guide, naming conventions, branching strategy, and PR review process upfront. At Ocean View Games, the first thing we do on any co-development engagement is review the client's coding standards and ensure every line we write matches their project's conventions. When we leave, there should be no way to tell which code we wrote.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Define Ownership Boundaries
&lt;/h3&gt;

&lt;p&gt;Be explicit about which systems or features the co-development team owns. Ambiguous ownership leads to duplicated effort and merge conflicts. Clear boundaries allow both teams to work in parallel with confidence.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Plan the Handover
&lt;/h3&gt;

&lt;p&gt;Every co-development engagement should have a defined exit plan. We document every system we build, comment our code thoroughly, and provide technical handover sessions to ensure your internal team can maintain and extend our work without confusion. Zero lock-in is a core principle - if our engagement ends, your team picks up exactly where we left off.&lt;/p&gt;




&lt;h2&gt;
  
  
  Is It Time?
&lt;/h2&gt;

&lt;p&gt;If you recognise one or more of these signs in your studio, it is worth having the conversation. Not every situation requires a co-development partner - sometimes the answer is a scope reduction, a timeline extension, or a targeted hire. But when capacity, expertise, or timeline pressures exceed what your internal team can sustainably handle, a co-development partnership is the most effective way to bridge the gap.&lt;/p&gt;

&lt;p&gt;At Ocean View Games, we work with &lt;a href="https://oceanviewgames.co.uk/industries/game-studios" rel="noopener noreferrer"&gt;game studios&lt;/a&gt; and &lt;a href="https://oceanviewgames.co.uk/industries/startups" rel="noopener noreferrer"&gt;funded startups&lt;/a&gt; as embedded Unity engineering teams. We join your workflow, adopt your standards, and deliver production-ready code from the first sprint. Our team brings senior-level experience from projects including &lt;a href="https://oceanviewgames.co.uk/projects/domi" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt; and RuneScape Mobile - complex, high-stakes codebases where quality and reliability are non-negotiable.&lt;/p&gt;

&lt;p&gt;If you want to explore whether co-development is the right model for your current project, &lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;reach out to our team&lt;/a&gt;. We are happy to discuss your situation, even if the conclusion is that you do not need us yet.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;Co-Development &amp;amp; Staff Augmentation Services&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oceanviewgames.co.uk/industries/game-studios" rel="noopener noreferrer"&gt;Game Studios Industry Page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oceanviewgames.co.uk/industries/startups" rel="noopener noreferrer"&gt;Startups Industry Page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oceanviewgames.co.uk/case-studies/domi-online-unity-mmo" rel="noopener noreferrer"&gt;Domi Online MMORPG Case Study&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://oceanviewgames.co.uk/services/network-engineering" rel="noopener noreferrer"&gt;Multiplayer &amp;amp; Network Engineering Services&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-brief-builder" rel="noopener noreferrer"&gt;Game Development Brief Builder&lt;/a&gt; - Structure your needs before approaching partners.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Building Accessible Games: WCAG for Interactive Content</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Mon, 28 Sep 2026 21:21:23 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/building-accessible-games-wcag-for-interactive-content-4eim</link>
      <guid>https://dev.to/oceanviewgames/building-accessible-games-wcag-for-interactive-content-4eim</guid>
      <description>&lt;p&gt;Accessibility in games is not charity work. It is sound engineering, responsible design, and increasingly, a contractual requirement. When public institutions, government bodies, and educational publishers commission interactive content, they expect compliance with established accessibility standards. And even for commercial titles targeting the widest possible audience, accessible design consistently improves the experience for everyone who plays.&lt;/p&gt;

&lt;p&gt;Our team's prior institutional work included educational projects for Cambridge University Press, the Museum of London, and European research consortia funded by EU Horizon 2020. In every one of those projects, accessibility was not a nice-to-have feature bolted on at the end. It was a design constraint from Day 1, and it made the games better.&lt;/p&gt;

&lt;p&gt;This article is a practical guide to applying &lt;strong&gt;WCAG 2.2 AA standards&lt;/strong&gt; to interactive game content. We will cover what the guidelines actually mean for games, where they apply, and how to implement them without compromising the player experience.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Accessibility Matters for Games
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Numbers Are Significant
&lt;/h3&gt;

&lt;p&gt;Disability and temporary or situational access needs affect a substantial part of any broad audience. Designing an experience that depends on one input method, one colour distinction, or perfect hearing needlessly narrows who can use it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Institutional Clients Require It
&lt;/h3&gt;

&lt;p&gt;If you are building interactive content for &lt;strong&gt;government bodies, museums, or educational publishers&lt;/strong&gt;, accessibility requirements are often part of procurement. The exact legal and contractual standard depends on the client, jurisdiction, platform, and nature of the service, so confirm the required conformance target during discovery rather than assuming one rule applies to every game.&lt;/p&gt;

&lt;p&gt;During our team's work on the Great Fire of London interactive game for the Museum of London, accessibility was a core deliverable. The game needed to be playable in classrooms across the UK on a range of devices, by children of varying abilities. This meant responsive layouts, readable text, keyboard-navigable menus, and colour-blind-friendly visual design were non-negotiable.&lt;/p&gt;

&lt;h3&gt;
  
  
  It Improves UX for Everyone
&lt;/h3&gt;

&lt;p&gt;This is not just a feel-good talking point. Accessible design patterns consistently produce better user experiences across the board:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Larger tap targets&lt;/strong&gt; designed for motor-impaired players also reduce misclicks on mobile for all players&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High-contrast UI&lt;/strong&gt; designed for low-vision players also improves readability in bright sunlight or on cheap screens&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Remappable controls&lt;/strong&gt; designed for players with limited dexterity also satisfy power users who prefer custom bindings&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subtitles and visual cues&lt;/strong&gt; designed for deaf players also help anyone playing on a commuter train with the volume off&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Accessible design is not a constraint on creativity. Many accessibility decisions - clearer hierarchy, flexible input, readable UI, captions - also improve usability in everyday situations for a wider audience.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Understanding WCAG 2.2 in a Game Context
&lt;/h2&gt;

&lt;p&gt;The Web Content Accessibility Guidelines (WCAG) were written for web content, not games specifically. Applying them to interactive experiences requires interpretation. Here is how the four core principles, known by the acronym POUR, translate to game development.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Perceivable
&lt;/h3&gt;

&lt;p&gt;Players must be able to perceive the information presented. In a game, this means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Text alternatives&lt;/strong&gt; for non-text content. If a quest objective is communicated through an icon alone, provide a text label or tooltip alongside it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Captions and subtitles&lt;/strong&gt; for audio content. Any dialogue, narration, or critical sound effect should have a visual equivalent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sufficient colour contrast.&lt;/strong&gt; The minimum contrast ratio for normal text is 4.5:1 against its background. For large text (18pt or 14pt bold), the ratio is 3:1. HUD elements, menu text, and in-game dialogue must meet these thresholds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No information conveyed by colour alone.&lt;/strong&gt; If a health bar goes from green to red, it must also change shape, label, or pattern so colour-blind players can interpret it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Operable
&lt;/h3&gt;

&lt;p&gt;Players must be able to operate the interface. For games, this is where things get interesting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Keyboard/controller accessibility.&lt;/strong&gt; Every menu, dialogue, and critical gameplay interaction should be operable without a mouse. For educational web games deployed to classrooms (where students may use Chromebooks with trackpads or keyboard-only setups), this is essential.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No time-dependent inputs unless adjustable.&lt;/strong&gt; If a game mechanic requires a player to press a button within a strict time window, provide an option to extend or disable that timer. This is particularly relevant for quick-time events (QTEs).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Seizure safety.&lt;/strong&gt; Avoid flashing content that exceeds three flashes per second. This is not just a guideline; it is a serious health concern.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Navigable structure.&lt;/strong&gt; Players should always know where they are in the game's menu hierarchy and how to return to the main menu or pause screen.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. Understandable
&lt;/h3&gt;

&lt;p&gt;The game's interface and content must be understandable:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Readable text.&lt;/strong&gt; Use clear fonts and test them at the actual physical sizes, viewing distances, resolutions, and scaling settings your players will use. A single point-size rule does not translate reliably across phones, tablets, browsers, and televisions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Predictable behaviour.&lt;/strong&gt; Menus should behave consistently. A "back" button should always go back. Settings should persist across sessions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Error prevention and recovery.&lt;/strong&gt; If a player makes a purchase, confirm it. If a player accidentally deletes a save file, ask for confirmation. This aligns with both accessibility best practice and good UX.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. Robust
&lt;/h3&gt;

&lt;p&gt;The content must be robust enough to be interpreted by a wide range of user agents, including assistive technologies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Semantic markup.&lt;/strong&gt; For HTML5/WebGL games, use proper ARIA roles and labels so screen readers can interpret menu elements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assistive technology compatibility.&lt;/strong&gt; Test with screen readers (NVDA, VoiceOver) to ensure critical UI elements are announced correctly.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Practical Implementation Guide
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Colour Blindness Modes
&lt;/h3&gt;

&lt;p&gt;Colour vision deficiency is common enough that colour-only communication is a poor default. The most common categories you will encounter in testing are:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Deuteranopia&lt;/strong&gt; (red-green, most common)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Protanopia&lt;/strong&gt; (red-green)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tritanopia&lt;/strong&gt; (blue-yellow, rare)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Implementation approach:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Never use colour as the sole indicator of state. Pair every colour change with a shape, icon, or text change.&lt;/li&gt;
&lt;li&gt;Provide a colour-blind mode in the settings menu that swaps problematic colour pairs. At minimum, target deuteranopia.&lt;/li&gt;
&lt;li&gt;Use a colour-blind simulation tool during development. We recommend the Coblis simulator or Unity's built-in colour blindness simulation in the Scene View.&lt;/li&gt;
&lt;li&gt;Test your UI with the Ishihara plate methodology: if two UI elements are distinguishable only by hue (not by brightness, shape, or label), they will fail for some players.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In our work on &lt;a href="https://oceanviewgames.co.uk/services/educationalgames" rel="noopener noreferrer"&gt;educational games&lt;/a&gt;, we adopted a "shape-first" design language. Every interactive element has a distinct silhouette, and colour is layered on top as a secondary cue. This approach survived colour-blind testing without requiring a separate "mode" at all.&lt;/p&gt;

&lt;h3&gt;
  
  
  Screen Reader Support for Menu Systems
&lt;/h3&gt;

&lt;p&gt;For HTML5 and WebGL games, screen reader support is achievable and increasingly expected:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use semantic HTML elements (&lt;code&gt;&amp;lt;button&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;nav&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;dialog&amp;gt;&lt;/code&gt;) rather than generic &lt;code&gt;&amp;lt;div&amp;gt;&lt;/code&gt; elements for all menu UI&lt;/li&gt;
&lt;li&gt;Apply &lt;code&gt;aria-label&lt;/code&gt; attributes to any interactive element where the visible text is insufficient (such as icon-only buttons)&lt;/li&gt;
&lt;li&gt;Manage focus programmatically. When a menu opens, move focus to the first interactive element. When it closes, return focus to the element that opened it.&lt;/li&gt;
&lt;li&gt;Announce dynamic changes with &lt;code&gt;aria-live&lt;/code&gt; regions. If a player's score changes, a screen reader user should be able to access that information.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For Unity-based games deployed to native platforms, screen reader integration is more limited but improving. Unity's UI Toolkit supports some accessibility features natively, and third-party packages like UAP (Unity Accessibility Plugin) can bridge the gap for mobile deployments.&lt;/p&gt;

&lt;h3&gt;
  
  
  Motor Accessibility
&lt;/h3&gt;

&lt;p&gt;Motor impairments range from tremors that make precision inputs difficult to conditions that limit a player to a single switch input. Here is what we recommend:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Remappable controls.&lt;/strong&gt; Allow every control to be rebound. This is already standard practice on PC and console, but mobile games often neglect it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Adjustable input sensitivity.&lt;/strong&gt; Provide sliders for camera speed, dead zones, and aim assist.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hold vs. toggle options.&lt;/strong&gt; Any action that requires holding a button (sprinting, aiming) should have an alternative toggle mode.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Auto-play and assist modes.&lt;/strong&gt; For educational games, consider whether a teacher or carer needs a way to advance, repeat, or operate content on behalf of the learner. The right option depends on the learning objective and target users.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Motor accessibility features are not "easy mode." They are input flexibility. Many non-disabled players prefer toggle-to-sprint, adjustable sensitivity, and remapped controls. Building these options benefits your entire player base.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Subtitle and Caption Best Practices
&lt;/h3&gt;

&lt;p&gt;Subtitles in games have historically been an afterthought: tiny white text with no background, rendering them useless in bright scenes. Modern standards demand better:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Background contrast.&lt;/strong&gt; Place subtitles on a semi-transparent dark background. Never render white text directly over gameplay footage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Speaker identification.&lt;/strong&gt; Use colour coding or labels to indicate who is speaking. Remember to pair colour with a name label for colour-blind players.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Size options.&lt;/strong&gt; Provide at least three subtitle size options (small, medium, large).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sound effect captions.&lt;/strong&gt; Critical gameplay sounds (an approaching enemy, an alarm) should have optional visual indicators or descriptive captions like "[footsteps approaching from behind]".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Positioning.&lt;/strong&gt; Allow players to adjust subtitle position to avoid covering important gameplay elements.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Accessibility in Educational and Government Games
&lt;/h2&gt;

&lt;p&gt;When we build games for government institutions and &lt;a href="https://oceanviewgames.co.uk/industries/museums" rel="noopener noreferrer"&gt;museums&lt;/a&gt;, the accessibility requirements are typically more formal and more stringent than for commercial titles.&lt;/p&gt;

&lt;h3&gt;
  
  
  Compliance Documentation
&lt;/h3&gt;

&lt;p&gt;Institutional clients may require an &lt;strong&gt;accessibility conformance report&lt;/strong&gt; documenting which criteria the experience meets, partially meets, or does not meet. Some procurements use a VPAT/ACR format; others specify their own evidence. We recommend maintaining this document throughout development rather than producing it as a last-minute exercise before delivery.&lt;/p&gt;

&lt;h3&gt;
  
  
  Testing with Real Users
&lt;/h3&gt;

&lt;p&gt;Automated accessibility checkers (Axe, Lighthouse) can catch low-hanging fruit like missing alt text and poor contrast ratios. But they cannot tell you whether a game is genuinely playable by someone using a switch device or screen reader. We strongly recommend:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Inclusive user testing&lt;/strong&gt; with disabled participants during the prototype phase&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Expert accessibility audits&lt;/strong&gt; from a specialist consultancy during beta&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ongoing regression testing&lt;/strong&gt; to ensure new features do not break existing accessibility features&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Classroom Deployment Considerations
&lt;/h3&gt;

&lt;p&gt;During our team's experience building educational games for projects funded by EU Horizon 2020, we learned that classroom environments introduce unique accessibility challenges:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Students may be using &lt;strong&gt;shared Chromebooks&lt;/strong&gt; with no personalised accessibility settings&lt;/li&gt;
&lt;li&gt;Teachers may need to operate the game on behalf of a student using a projector&lt;/li&gt;
&lt;li&gt;Internet connectivity may be unreliable, so the game needs to function offline&lt;/li&gt;
&lt;li&gt;Multiple students with different accessibility needs may be playing simultaneously on different devices in the same classroom&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These constraints forced us to build accessibility settings that are easy to change per-session rather than per-installation, stored in-game rather than relying on OS-level accessibility features.&lt;/p&gt;




&lt;h2&gt;
  
  
  Testing Your Game's Accessibility
&lt;/h2&gt;

&lt;p&gt;Here is a practical testing checklist we use at Ocean View Games:&lt;/p&gt;

&lt;h3&gt;
  
  
  Visual Accessibility
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Run every screen through a colour contrast checker (minimum 4.5:1 for body text)&lt;/li&gt;
&lt;li&gt;Enable a colour-blind simulation and verify all critical information is still distinguishable&lt;/li&gt;
&lt;li&gt;Scale text to 200% and verify no content is lost or overlapping&lt;/li&gt;
&lt;li&gt;Verify all images and icons have text alternatives&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Motor Accessibility
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Play through the entire game using only a keyboard (no mouse)&lt;/li&gt;
&lt;li&gt;Play through using only a controller&lt;/li&gt;
&lt;li&gt;Verify all hold-to-activate actions have a toggle alternative&lt;/li&gt;
&lt;li&gt;Test with reduced input speed (simulate motor impairment by limiting inputs per second)&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Auditory Accessibility
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Play through the entire game with volume at zero&lt;/li&gt;
&lt;li&gt;Verify all critical audio information has a visual equivalent&lt;/li&gt;
&lt;li&gt;Check that subtitles are readable, properly timed, and correctly attributed&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Cognitive Accessibility
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Verify all instructions are clear and use plain language&lt;/li&gt;
&lt;li&gt;Check that the game can be paused at any point&lt;/li&gt;
&lt;li&gt;Verify that tutorials can be replayed&lt;/li&gt;
&lt;li&gt;Test that difficulty options are accessible and clearly explained&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Building Accessibility Into Your Development Process
&lt;/h2&gt;

&lt;p&gt;One of the most expensive mistakes is treating accessibility as a post-production polish pass. Retrofitting it late can force changes across input, UI architecture, content, audio, and QA at the point where those systems are hardest to change.&lt;/p&gt;

&lt;p&gt;Here is how we integrate it into our process:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Discovery phase:&lt;/strong&gt; Define accessibility targets (WCAG AA, platform-specific guidelines) as formal requirements in the GDD&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prototyping phase:&lt;/strong&gt; Test core mechanics with keyboard-only and controller-only input before committing to a control scheme&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Production sprints:&lt;/strong&gt; Include accessibility acceptance criteria in every user story. "As a colour-blind player, I can distinguish between friendly and enemy units without relying on colour alone."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;QA phase:&lt;/strong&gt; Run the accessibility checklist above as part of every test pass&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Delivery:&lt;/strong&gt; Produce an accessibility conformance report alongside the final build&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/educationalgames" rel="noopener noreferrer"&gt;Educational Game Development Services&lt;/a&gt; - How we build accessible learning experiences for institutional clients&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/education" rel="noopener noreferrer"&gt;Education Industry&lt;/a&gt; - Compliance requirements for institutional and public-sector interactive content&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/museums" rel="noopener noreferrer"&gt;Games for Museums and Cultural Institutions&lt;/a&gt; - Accessible interactive experiences for heritage organisations&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Game Development Budget Breakdown: Where Does the Money Go?</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Sat, 26 Sep 2026 23:16:35 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/game-development-budget-breakdown-where-does-the-money-go-ao1</link>
      <guid>https://dev.to/oceanviewgames/game-development-budget-breakdown-where-does-the-money-go-ao1</guid>
      <description>&lt;p&gt;One of the most common questions we hear from clients is deceptively simple: "How much will my game cost?" The honest answer is always "it depends," but that does not mean we cannot give you a clear framework for understanding where the money goes and why.&lt;/p&gt;

&lt;p&gt;Between David and Adam, our experience spans mobile, PC, educational games, legacy modernisation, and large live-game codebases. That gives us a useful planning framework for where budgets tend to go, even though the exact split changes substantially from project to project.&lt;/p&gt;

&lt;p&gt;This post breaks down the major cost categories in a typical game development budget, explains what drives spending in each one, and offers guidance on where to prioritise when funds are limited.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Five Core Budget Categories
&lt;/h2&gt;

&lt;p&gt;For planning, we split game-development budgets into five core categories. The exact percentages shift with genre, scope, art requirements, platform targets, and team structure. The ranges below are heuristics based on the kinds of projects we scope, not universal industry benchmarks.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Category&lt;/th&gt;
&lt;th&gt;Typical Share&lt;/th&gt;
&lt;th&gt;What It Covers&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Engineering&lt;/td&gt;
&lt;td&gt;40-50%&lt;/td&gt;
&lt;td&gt;Gameplay programming, systems architecture, networking, platform porting&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Art &amp;amp; Audio&lt;/td&gt;
&lt;td&gt;20-30%&lt;/td&gt;
&lt;td&gt;2D/3D art, animation, UI design, VFX, music, sound effects&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Design&lt;/td&gt;
&lt;td&gt;10-15%&lt;/td&gt;
&lt;td&gt;Game design, level design, economy balancing, UX research&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;QA &amp;amp; Testing&lt;/td&gt;
&lt;td&gt;5-10%&lt;/td&gt;
&lt;td&gt;Functional testing, device testing, performance profiling, regression&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Project Management&lt;/td&gt;
&lt;td&gt;5-10%&lt;/td&gt;
&lt;td&gt;Production, scheduling, client communication, tooling&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These numbers assume you are working with an external development partner or agency. If you are building in-house, the ratios still hold, but the absolute numbers will include salary overheads, equipment, and office costs that are baked into agency rates.&lt;/p&gt;




&lt;h2&gt;
  
  
  Engineering: 40-50% of the Budget
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Engineering is usually the largest cost on the projects we scope&lt;/strong&gt;, and for good reason. Your engineers are not just writing gameplay code - they are building the foundational systems that everything else sits on top of.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Drives Engineering Costs
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Core systems architecture&lt;/strong&gt; - the skeleton of your game. This includes input handling, scene management, save systems, and the gameplay loop itself. A robust architecture pays dividends later; a fragile one creates exponential technical debt.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Networking and multiplayer&lt;/strong&gt; - if your game has any online component, expect engineering costs to increase significantly. Server-authoritative backends, state synchronisation, lag compensation, and matchmaking systems are complex and require specialist expertise. When we built the networking layer for Domi Online, we used FishNet on a cost-optimised AWS infrastructure specifically to keep operational expenses sustainable without sacrificing security or performance.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Platform-specific work&lt;/strong&gt; - shipping on iOS and Android is not simply "building once." Each platform has its own APIs, compliance requirements, input systems, and performance characteristics. Console porting adds another layer of complexity with certification requirements (TRC, XR, Lotcheck).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Performance optimisation&lt;/strong&gt; - mobile devices have strict thermal, memory, and battery constraints. David's previous work on RuneScape Mobile at Jagex reinforced how much engineering can sit behind making a desktop-scale game behave well on mobile hardware. Even much smaller games need profiling and optimisation passes on real devices.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Third-party integrations&lt;/strong&gt; - analytics, ad mediation, in-app purchases, authentication, cloud save, and push notifications. Each SDK integration carries its own implementation and maintenance cost.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Do not underestimate engineering costs for "simple" games. A 2D puzzle game still needs save systems, monetisation integration, device testing, and store compliance. The visible gameplay is often the smallest part of the engineering workload.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Where to Save
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Use proven frameworks and libraries rather than building everything from scratch. Our internal development framework shortens setup by reusing standardised components for audio, haptics, UI, and scene management instead of rebuilding the same foundations on every project.&lt;/li&gt;
&lt;li&gt;Prioritise your core loop. Get the one thing that makes your game fun working before investing in ancillary systems.&lt;/li&gt;
&lt;li&gt;Choose your platforms carefully at launch. Shipping on one platform first and porting later is almost always cheaper than simultaneous multi-platform development.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Art and Audio: 20-30% of the Budget
&lt;/h2&gt;

&lt;p&gt;Art is what players see first. It drives store page conversion, first impressions, and perceived quality. But it is also the category where scope creep is most dangerous.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Drives Art Costs
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Visual fidelity&lt;/strong&gt; - a hyper-casual game with flat 2D art costs a fraction of a game with hand-painted environments and 3D character animations. The gap is enormous.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Asset volume&lt;/strong&gt; - an open-world game needs hundreds or thousands of unique assets. A puzzle game might need dozens. When we developed Empires Rise, our internal 4X strategy game, sourcing and integrating art assets across multiple civilisations and biomes was a significant production effort.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Animation&lt;/strong&gt; - character animation, UI animation, and VFX all require specialised skills. Skeletal animation systems (Spine, Unity's Animation Rigging) reduce costs compared to frame-by-frame approaches, but still require skilled artists.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Audio&lt;/strong&gt; - music, sound effects, and voice acting. Often underbudgeted, audio is critical to game feel. A good sound designer can make a £10,000 game feel like a £100,000 game.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;UI/UX design&lt;/strong&gt; - interface design for games is a specialised discipline, particularly for mobile. Touch targets, safe areas, adaptive layouts, and platform-specific conventions all matter.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Where to Save
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Define your art style early and stick to it. Style changes mid-production are the single most expensive art decision.&lt;/li&gt;
&lt;li&gt;Use asset stores strategically for non-hero content (background foliage, generic sound effects), but invest in custom work for anything the player interacts with directly.&lt;/li&gt;
&lt;li&gt;Modular art pipelines reduce cost at scale. Design characters, environments, and UI elements as composable pieces rather than bespoke one-offs.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Design: 10-15% of the Budget
&lt;/h2&gt;

&lt;p&gt;Game design is often the most undervalued line item, yet it has the highest leverage on your game's commercial success. A well-designed game with modest art will outperform a beautiful game with poor mechanics.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Drives Design Costs
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Game Design Documentation (GDD)&lt;/strong&gt; - the blueprint for your entire project. A thorough GDD covers mechanics, progression, economy, UI flows, and technical specifications. This document prevents expensive mid-production pivots.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Economy and balancing&lt;/strong&gt; - free-to-play games live or die by their economy design. Modelling currency flows, progression curves, and pricing requires data-driven iteration that continues well past launch.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Level design&lt;/strong&gt; - creating engaging content that uses your mechanics effectively. For &lt;a href="https://oceanviewgames.co.uk/projects/navigo" rel="noopener noreferrer"&gt;Navigo&lt;/a&gt;, the educational game our team built during a previous agency tenure for the EU Horizon 2020 programme, designing 15 unique mini-games across four languages required extensive collaboration with educational specialists.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;User research and playtesting&lt;/strong&gt; - testing with real players reveals problems that no amount of internal review will catch. Budget for at least two rounds of structured playtesting.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Where to Save
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Invest heavily in pre-production design. Every pound spent on design validation before production begins saves five to ten pounds in engineering rework.&lt;/li&gt;
&lt;li&gt;Use greybox prototyping to validate mechanics before committing to art production. We build playable Unity prototypes in our &lt;a href="https://oceanviewgames.co.uk/services/gamedesign" rel="noopener noreferrer"&gt;game design process&lt;/a&gt; specifically to find the fun before spending on final assets.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Design and prototyping are high-leverage spend. A clear GDD and an early playable prototype can expose expensive assumptions before they turn into production rework.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  QA and Testing: 5-10% of the Budget
&lt;/h2&gt;

&lt;p&gt;QA is the category that gets cut first when budgets tighten, and it is the category that causes the most damage when underfunded. A crash-heavy launch or a broken tutorial will tank your store rating and retention metrics.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Drives QA Costs
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Device fragmentation&lt;/strong&gt; - Android alone has thousands of device configurations. Testing across a representative set of screen sizes, chipsets, and OS versions is essential for mobile games.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Regression testing&lt;/strong&gt; - every new feature risks breaking existing ones. Systematic regression sweeps before each build delivery catch issues before players do.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Performance profiling&lt;/strong&gt; - ensuring stable frame rates, acceptable memory usage, and manageable thermal output across your target devices. This is particularly critical for mobile, where a game that overheats the phone will be uninstalled immediately.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Platform certification&lt;/strong&gt; - console submissions (TRC, XR, Lotcheck) require extensive pre-validation. A failed certification costs weeks of delay.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Live service testing&lt;/strong&gt; - if your game receives updates, every patch needs testing. Seasonal events, balance changes, and new content all carry regression risk.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Where to Save
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Automate where possible. Unit tests for core systems and automated build verification catch regressions cheaply.&lt;/li&gt;
&lt;li&gt;Prioritise the critical path. Test the first-time user experience and core gameplay loop exhaustively. Edge cases in rarely-used menus can wait.&lt;/li&gt;
&lt;li&gt;Integrate QA into your development pipeline from day one, not as an afterthought at the end of production.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Project Management: 5-10% of the Budget
&lt;/h2&gt;

&lt;p&gt;Project management is the glue that holds everything together. It includes production scheduling, client communication, risk management, and the tools that enable the team to collaborate effectively.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Drives PM Costs
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Team coordination&lt;/strong&gt; - the larger the team and the more external dependencies (freelancers, external art studios, platform holders), the more management overhead is required.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Client communication&lt;/strong&gt; - regular sprint reviews, playable demos, and status reports take time to prepare but are essential for maintaining alignment.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Tooling and infrastructure&lt;/strong&gt; - Jira, Notion, version control (Git, Perforce, Plastic SCM), CI/CD pipelines, and cloud services all carry licence and maintenance costs.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Risk management&lt;/strong&gt; - identifying and mitigating technical and schedule risks before they become crises. A good producer pays for themselves many times over.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Where to Save
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Use agile methodologies with two-week sprints. Short cycles surface problems early when they are cheap to fix.&lt;/li&gt;
&lt;li&gt;Invest in good tooling. The cost of a Jira licence is trivial compared to the cost of miscommunication.&lt;/li&gt;
&lt;li&gt;Define scope clearly at project start. The single biggest driver of PM overhead is scope creep.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Budget Allocation by Game Type
&lt;/h2&gt;

&lt;p&gt;The ranges below are illustrative planning examples, not fixed market prices. Existing code, supplied art, content volume, platform requirements, and technical risk can move a real quote substantially.&lt;/p&gt;

&lt;p&gt;The percentages above are averages. Here is how they shift for common game types:&lt;/p&gt;

&lt;h3&gt;
  
  
  Mobile Casual / Hyper-Casual
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Engineering: 35-40%&lt;/li&gt;
&lt;li&gt;Art: 25-30%&lt;/li&gt;
&lt;li&gt;Design: 10-15%&lt;/li&gt;
&lt;li&gt;QA: 5-10%&lt;/li&gt;
&lt;li&gt;PM: 5-10%&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total range:&lt;/strong&gt; £30,000-150,000&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Mobile Mid-Core (Strategy, RPG)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Engineering: 40-50%&lt;/li&gt;
&lt;li&gt;Art: 20-30%&lt;/li&gt;
&lt;li&gt;Design: 10-15%&lt;/li&gt;
&lt;li&gt;QA: 5-10%&lt;/li&gt;
&lt;li&gt;PM: 5-10%&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total range:&lt;/strong&gt; £100,000-500,000&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Multiplayer / Online Games
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Engineering: 45-55% (networking costs increase significantly)&lt;/li&gt;
&lt;li&gt;Art: 15-25%&lt;/li&gt;
&lt;li&gt;Design: 10-15%&lt;/li&gt;
&lt;li&gt;QA: 10-15% (multiplayer testing is more complex)&lt;/li&gt;
&lt;li&gt;PM: 5-10%&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total range:&lt;/strong&gt; £200,000-2,000,000+&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Educational / Serious Games
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Engineering: 35-45%&lt;/li&gt;
&lt;li&gt;Art: 20-25%&lt;/li&gt;
&lt;li&gt;Design: 15-20% (curriculum alignment increases design work)&lt;/li&gt;
&lt;li&gt;QA: 5-10%&lt;/li&gt;
&lt;li&gt;PM: 5-10%&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Total range:&lt;/strong&gt; £50,000-300,000&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Planning Your Budget: Practical Steps
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Start with scope, not budget&lt;/strong&gt; - define what your game needs to do before setting a number. Our &lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator" rel="noopener noreferrer"&gt;game development cost estimator&lt;/a&gt; can help you build a baseline estimate.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Build a contingency&lt;/strong&gt; - leave meaningful budget and schedule margin for unknowns. The right percentage depends on how much of the design, technology, and content is already proven.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Phase your investment&lt;/strong&gt; - do not commit the entire budget before the riskiest assumptions have been tested. Use discovery and prototyping to decide whether the full production investment still makes sense.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Understand the cost of delay&lt;/strong&gt; - a three-month delay does not just cost three months of developer time. It costs three months of missed revenue, three months of market timing risk, and the opportunity cost of what your team could have built instead.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Get an external estimate&lt;/strong&gt; - even if you are building in-house, an external perspective on scope and cost can reveal blind spots. Our &lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost" rel="noopener noreferrer"&gt;game development cost breakdown&lt;/a&gt; provides additional context on what drives pricing.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator" rel="noopener noreferrer"&gt;Game Development Cost Estimator&lt;/a&gt; - Interactive tool to estimate your project's budget&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost" rel="noopener noreferrer"&gt;Game Development Cost Breakdown&lt;/a&gt; - Detailed guide to what drives game development pricing&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/gamedevelopment" rel="noopener noreferrer"&gt;Unity Game Development Services&lt;/a&gt; - Our full-cycle Unity development offering&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/blog/posts/co-development-vs-freelancers-vs-hiring" rel="noopener noreferrer"&gt;Co-Development vs Freelancers vs Full-Time Hires&lt;/a&gt; - Understand the staffing models that affect your budget&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Why Your Legacy Educational Game Needs an Update</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Sat, 26 Sep 2026 23:16:28 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/why-your-legacy-educational-game-needs-an-update-4doi</link>
      <guid>https://dev.to/oceanviewgames/why-your-legacy-educational-game-needs-an-update-4doi</guid>
      <description>&lt;p&gt;Somewhere in your organisation, there is an educational game that was built five, ten, or even fifteen years ago. It might have been a Flash-based interactive for a museum. It might be a Unity 4 app that no longer compiles. It might be a Java applet that last ran reliably in Internet Explorer 8. Whatever it is, it was effective when it launched - teachers loved it, learners engaged with it, and the investment paid for itself many times over.&lt;/p&gt;

&lt;p&gt;But now it is dying. Not because the content is wrong or the pedagogy is outdated, but because &lt;strong&gt;the technology underneath it has become obsolete&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;This post makes the case for modernising your legacy educational game - and explains what that process actually involves.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Four Forces Killing Your Legacy Game
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Flash Is Dead (and It Is Not Coming Back)
&lt;/h3&gt;

&lt;p&gt;Adobe Flash was officially discontinued in December 2020. Every major browser has removed Flash Player support. Chromebooks - the dominant device in schools - never supported it. If your educational game was built in Flash, it is effectively inaccessible to the audience it was designed for.&lt;/p&gt;

&lt;p&gt;This is not a theoretical risk. Thousands of educational interactives built between 2000 and 2015 were Flash-based. Many of these were excellent learning tools that represented significant investment. Without modernisation, that investment is lost entirely.&lt;/p&gt;

&lt;p&gt;Flash end-of-life is the most urgent trigger, but it is not the only one. Legacy Unity projects (pre-Unity 2018), Java applets, Silverlight applications, and even early HTML games with jQuery dependencies face similar obsolescence timelines as browsers and operating systems drop support for older runtimes.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Learners Are Mobile-First
&lt;/h3&gt;

&lt;p&gt;When your educational game was built, the target device was a desktop computer or perhaps a laptop. Today, learners reach for tablets and phones first. In many schools, the primary computing device is a Chromebook or iPad.&lt;/p&gt;

&lt;p&gt;A game designed for a 4:3 desktop monitor with mouse-and-keyboard input does not work on a 6-inch touchscreen. The interface elements are too small to tap accurately. The layout wastes screen real estate or, worse, overflows the viewport. Hover states do not exist on touch devices. The entire interaction model needs rethinking.&lt;/p&gt;

&lt;p&gt;This is not just a convenience issue - it is an &lt;strong&gt;access issue&lt;/strong&gt;. If your educational game cannot run on the devices learners actually use, it reaches nobody.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Accessibility Requirements Have Evolved
&lt;/h3&gt;

&lt;p&gt;WCAG 2.2 was published in 2023 and is rapidly becoming the baseline expectation for publicly funded educational content. Many legacy games were built before WCAG 2.0 was widely adopted, let alone 2.2.&lt;/p&gt;

&lt;p&gt;Common accessibility gaps in legacy educational games include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No keyboard navigation&lt;/strong&gt;: Games built for mouse-only interaction are unusable for learners with motor disabilities&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Poor colour contrast&lt;/strong&gt;: Aesthetic choices from a decade ago often fail modern contrast ratio requirements (4.5:1 for normal text)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No text alternatives&lt;/strong&gt;: Images, animations, and audio without alt text or transcripts exclude learners using screen readers&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fixed text sizes&lt;/strong&gt;: Content that cannot be scaled excludes learners with visual impairments&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No captions or subtitles&lt;/strong&gt;: Audio-dependent content excludes deaf and hard-of-hearing learners&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For publicly funded educational content, accessibility is not optional. Institutions face legal obligations under the Equality Act 2010 (UK), ADA (US), and equivalent legislation worldwide. A game that does not meet current standards is a compliance liability.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. LMS Integration Expectations
&lt;/h3&gt;

&lt;p&gt;Modern educational institutions expect training content to integrate with their Learning Management System. Teachers want to track which students completed which modules, how they scored, and where they struggled.&lt;/p&gt;

&lt;p&gt;Legacy games typically have no LMS integration whatsoever. They are standalone experiences that produce no data. In an era when xAPI, SCORM, and Learning Tools Interoperability (LTI) are standard expectations, a game that cannot report learner progress back to the institution's systems is increasingly difficult to justify deploying.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Legacy educational games face four simultaneous pressures: runtime obsolescence (Flash/Java/Silverlight), device incompatibility (mobile-first learners), accessibility non-compliance (WCAG 2.2), and integration gaps (no LMS reporting). Any one of these is sufficient reason to modernise. Most legacy games face all four.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The Modernisation Spectrum
&lt;/h2&gt;

&lt;p&gt;Not every legacy game needs the same level of intervention. The scope depends on the game's current state and your institution's requirements.&lt;/p&gt;

&lt;h3&gt;
  
  
  Level 1: Runtime Migration
&lt;/h3&gt;

&lt;p&gt;The lightest touch. The game logic and design remain largely unchanged, but the underlying technology is replaced. Flash to HTML5/WebGL is the most common migration of this type.&lt;/p&gt;

&lt;p&gt;This is appropriate when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The game design and content are still sound&lt;/li&gt;
&lt;li&gt;The target devices and screen sizes have not changed dramatically&lt;/li&gt;
&lt;li&gt;Accessibility requirements are minimal or already met&lt;/li&gt;
&lt;li&gt;No LMS integration is needed&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Level 2: Platform Modernisation
&lt;/h3&gt;

&lt;p&gt;The game logic is preserved, but the interface is redesigned for modern devices and accessibility standards. This typically involves:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Responsive layouts that work on mobile, tablet, and desktop&lt;/li&gt;
&lt;li&gt;Touch-friendly interaction redesign&lt;/li&gt;
&lt;li&gt;WCAG 2.2 compliance (keyboard navigation, contrast, text scaling, screen reader support)&lt;/li&gt;
&lt;li&gt;Modern aspect ratio support (16:9, 19.5:9 instead of legacy 4:3)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Level 3: Full Reconstruction
&lt;/h3&gt;

&lt;p&gt;The game is rebuilt from the ground up on a modern engine (typically Unity or HTML5), preserving the pedagogical design but modernising everything else. This is necessary when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The original source code is lost&lt;/li&gt;
&lt;li&gt;The game design needs significant updates to reflect current curriculum&lt;/li&gt;
&lt;li&gt;LMS integration is required&lt;/li&gt;
&lt;li&gt;The game needs to support multiple new platforms (iOS, Android, Chromebook, WebGL)&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  A Real-World Example: The Great Fire of London
&lt;/h2&gt;

&lt;p&gt;To illustrate what modernisation looks like in practice, consider the Great Fire of London interactive game. Originally built in Flash, this educational game was a staple in UK classrooms, teaching children about the historic events of 1666 through interactive scenarios and mini-games.&lt;/p&gt;

&lt;p&gt;When browsers dropped Flash support, the game faced extinction. During David's previous agency tenure, the team he worked with was commissioned by the Museum of London to rescue the experience.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Challenge
&lt;/h3&gt;

&lt;p&gt;The original source code had been &lt;strong&gt;lost&lt;/strong&gt;. This meant a simple recompile or automated conversion was impossible. The team had to treat the original Flash game as a "black box" and reverse-engineer every interaction.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Approach
&lt;/h3&gt;

&lt;p&gt;The team catalogued every interaction, animation timing, and win-state condition from the original Flash version by playing through it systematically. Using this as a blueprint, they:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Reverse-engineered the game logic&lt;/strong&gt; frame by frame, documenting every mechanic and state transition&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extracted and optimised original assets&lt;/strong&gt; - converting Flash vector art into optimised sprite sheets that load quickly on school Wi-Fi networks&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rebuilt the UI for modern screens&lt;/strong&gt; - the original 4:3 CRT layout was re-engineered for responsive 16:9, with UI elements decoupled from the game world so menus anchor to screen edges on any device&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Targeted school hardware&lt;/strong&gt; - the rebuilt version runs on Chromebooks, iPads, and modern web browsers, covering the vast majority of school computing environments&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  The Result
&lt;/h3&gt;

&lt;p&gt;The Great Fire of London game continues to be used in classrooms today, running natively in modern browsers without plugins. The pedagogical design that made it effective remains intact. The technology underneath is modern, maintainable, and accessible.&lt;/p&gt;

&lt;p&gt;This project demonstrates a critical principle of legacy modernisation: &lt;strong&gt;the goal is to preserve what works (the learning design) while replacing what does not (the technology)&lt;/strong&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Even when original source code is lost, legacy educational games can be fully reconstructed through reverse engineering. The Great Fire of London rescue proves that no game is truly "dead" if the content and pedagogy are worth saving.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The Cost of Doing Nothing
&lt;/h2&gt;

&lt;p&gt;Some organisations delay modernisation because it requires budget. But the cost of inaction is not zero - it is hidden.&lt;/p&gt;

&lt;h3&gt;
  
  
  Lost Educational Value
&lt;/h3&gt;

&lt;p&gt;If your game was effective when it launched, every day it remains inaccessible is a day learners miss out on that educational value. The original development investment generates zero return once the game stops working.&lt;/p&gt;

&lt;h3&gt;
  
  
  Accumulated Technical Debt
&lt;/h3&gt;

&lt;p&gt;The longer you wait, the harder (and more expensive) modernisation becomes. Flash decompilers become less reliable. Original team members leave. Documentation gets lost. The gap between the original technology and current standards widens.&lt;/p&gt;

&lt;h3&gt;
  
  
  Compliance Risk
&lt;/h3&gt;

&lt;p&gt;Accessibility non-compliance can create contractual, reputational, and in some contexts legal risk. The applicable requirement depends on the institution, jurisdiction, platform, and how the content is provided, so it should be part of the modernisation audit rather than treated as a cosmetic upgrade.&lt;/p&gt;

&lt;h3&gt;
  
  
  Institutional Reputation
&lt;/h3&gt;

&lt;p&gt;An educational institution that deploys broken, outdated, or inaccessible digital content sends the wrong message about its commitment to quality and inclusion.&lt;/p&gt;




&lt;h2&gt;
  
  
  What to Look For in a Modernisation Partner
&lt;/h2&gt;

&lt;p&gt;Not every game development studio is equipped for legacy modernisation. This is specialist work that requires a specific skill set.&lt;/p&gt;

&lt;h3&gt;
  
  
  Reverse Engineering Capability
&lt;/h3&gt;

&lt;p&gt;If your original source code is lost (and it very often is), the modernisation partner needs experience in decompilation and reconstruction. This is not standard game development work - it requires forensic analysis of compiled binaries, asset extraction from legacy formats, and the ability to recreate game logic from observed behaviour.&lt;/p&gt;

&lt;h3&gt;
  
  
  Educational Game Experience
&lt;/h3&gt;

&lt;p&gt;A studio that builds commercial games is not necessarily equipped to build educational ones. The modernisation partner should understand:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Curriculum alignment and pedagogical design&lt;/li&gt;
&lt;li&gt;Age-appropriate UX for your target demographic&lt;/li&gt;
&lt;li&gt;Accessibility standards (WCAG 2.2) and how to implement them in games&lt;/li&gt;
&lt;li&gt;LMS integration protocols (xAPI, SCORM, LTI)&lt;/li&gt;
&lt;li&gt;Data protection requirements for educational contexts (GDPR-K, COPPA)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Cross-Platform Deployment
&lt;/h3&gt;

&lt;p&gt;Your modernised game needs to reach the devices your learners actually use. The partner should have experience deploying to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Modern web browsers (HTML5/WebGL)&lt;/li&gt;
&lt;li&gt;Chromebooks (the dominant classroom device in many regions)&lt;/li&gt;
&lt;li&gt;iPads and Android tablets&lt;/li&gt;
&lt;li&gt;Interactive whiteboards and kiosk installations (for museum contexts)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Preservation Mindset
&lt;/h3&gt;

&lt;p&gt;The right partner understands that the goal is not to build a new game - it is to &lt;strong&gt;preserve an existing educational asset&lt;/strong&gt;. The pedagogy, content accuracy, and learning design should be treated as sacred. The technology is what gets replaced.&lt;/p&gt;




&lt;h2&gt;
  
  
  Planning Your Modernisation Project
&lt;/h2&gt;

&lt;p&gt;If you are considering updating a legacy educational game, here is a practical starting point:&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1: Audit the Current State
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What technology was the original game built in?&lt;/li&gt;
&lt;li&gt;Do you have the original source code and assets?&lt;/li&gt;
&lt;li&gt;What devices do your learners currently use?&lt;/li&gt;
&lt;li&gt;What accessibility standards do you need to meet?&lt;/li&gt;
&lt;li&gt;Does the game need LMS integration?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Step 2: Define the Target State
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Which platforms must the modernised game support?&lt;/li&gt;
&lt;li&gt;What accessibility standard or conformance target is required by the client or procurement framework?&lt;/li&gt;
&lt;li&gt;Do you need analytics or LMS integration?&lt;/li&gt;
&lt;li&gt;Does the game content (curriculum, facts, scenarios) need updating alongside the technology?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Step 3: Assess Scope and Budget
&lt;/h3&gt;

&lt;p&gt;The scope varies enormously depending on whether source code is available, how many platforms need supporting, and whether the content itself needs updating. A runtime migration (Flash to HTML5 with minimal changes) is a fraction of the cost of a full reconstruction.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Engage a Specialist
&lt;/h3&gt;

&lt;p&gt;Legacy modernisation is not a good fit for general-purpose web agencies. Look for a studio with specific experience in:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Flash-to-HTML5 or Flash-to-Unity conversion&lt;/li&gt;
&lt;li&gt;Educational game development&lt;/li&gt;
&lt;li&gt;Cross-platform deployment to school hardware&lt;/li&gt;
&lt;li&gt;Accessibility compliance&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Our Approach
&lt;/h2&gt;

&lt;p&gt;At Ocean View Games, &lt;a href="https://oceanviewgames.co.uk/services/legacy-modernisation" rel="noopener noreferrer"&gt;legacy game modernisation&lt;/a&gt; is one of our core services. We bring direct experience in Flash-to-HTML5 conversion, cross-platform educational game deployment, and building accessible, LMS-integrated learning experiences.&lt;/p&gt;

&lt;p&gt;Our team's experience working on the Great Fire of London modernisation project - reverse-engineering a lost-source Flash game into a fully functional modern HTML5 experience - demonstrated exactly the kind of forensic, preservation-focused approach that legacy educational games require.&lt;/p&gt;

&lt;p&gt;Whether your game needs a runtime migration, a full platform modernisation, or a ground-up reconstruction, we start with a feasibility audit that tells you exactly what is possible, what it costs, and how long it takes - before you commit to anything.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/legacy-modernisation" rel="noopener noreferrer"&gt;Legacy Game Modernisation Services&lt;/a&gt; - Our full approach to rescuing and modernising legacy titles&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/case-studies/educational-game-modernization-fire-of-london" rel="noopener noreferrer"&gt;Fire of London Case Study&lt;/a&gt; - Detailed breakdown of the Flash-to-HTML5 rescue project&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/educationalgames" rel="noopener noreferrer"&gt;Educational Game Development Services&lt;/a&gt; - How we build curriculum-aligned games for institutions&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/education" rel="noopener noreferrer"&gt;Education Industry Page&lt;/a&gt; - Our work with educational institutions&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator" rel="noopener noreferrer"&gt;Game Development Cost Estimator&lt;/a&gt; - Estimate the cost of modernising your legacy game.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/unity-migration-checker" rel="noopener noreferrer"&gt;Unity Migration Checker&lt;/a&gt; - Check if your Unity project needs migration.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Cross-Platform Save Systems: Cloud Sync Done Right</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Sat, 26 Sep 2026 23:16:19 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/cross-platform-save-systems-cloud-sync-done-right-2kmc</link>
      <guid>https://dev.to/oceanviewgames/cross-platform-save-systems-cloud-sync-done-right-2kmc</guid>
      <description>&lt;p&gt;Few systems in game development are as universally needed - and as consistently underestimated - as save data management. When your game lives on a single platform and a single device, saving is straightforward. The moment you add a second platform or a second device, you inherit an entirely new class of engineering problems: conflict resolution, offline play, schema evolution, and platform-specific API compliance.&lt;/p&gt;

&lt;p&gt;We have built save systems for games across the complexity spectrum. Our work on &lt;a href="https://oceanviewgames.co.uk/projects/domi" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt;, a persistent MMORPG with a server-authoritative backend, demanded a fundamentally different architecture than a mobile puzzle game. David's time working on RuneScape Mobile at Jagex also reinforced the wider lesson behind this article: long-lived games make persistence and backwards compatibility architectural concerns, not implementation details.&lt;/p&gt;

&lt;p&gt;This post is a technical guide for Unity developers building cross-platform cloud save systems. We will cover architecture decisions, platform-specific APIs, conflict resolution strategies, offline-first design, and schema migration for live games.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Cloud Save Is Harder Than It Looks
&lt;/h2&gt;

&lt;p&gt;At first glance, cloud save seems simple: serialise the game state, upload it to a server, download it on another device. In practice, every step introduces complexity:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What happens when the player is offline?&lt;/strong&gt; Mobile players lose connectivity constantly. Your game must remain fully playable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What happens when two devices have divergent saves?&lt;/strong&gt; The player progresses on their phone, then opens the game on their tablet before the phone syncs. Which save wins?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What happens when you update the game?&lt;/strong&gt; The save schema changes, but the player's cloud data is still in the old format.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What happens when the platform API fails?&lt;/strong&gt; Google Play Games Services, Game Center, and Steam Cloud each have their own failure modes, rate limits, and quirks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;A robust cloud save system must handle all of these cases gracefully&lt;/strong&gt;, without data loss and without confusing the player.&lt;/p&gt;




&lt;h2&gt;
  
  
  Architecture: The Three Layers
&lt;/h2&gt;

&lt;p&gt;We recommend structuring your cloud save system as three distinct layers. This separation makes each layer independently testable and replaceable.&lt;/p&gt;

&lt;h3&gt;
  
  
  Layer 1: The Save Data Model
&lt;/h3&gt;

&lt;p&gt;Your save data should be a plain C# class (or set of classes) with no dependencies on Unity types, MonoBehaviour, or any platform SDK. This makes it serialisable, testable, and portable.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;System&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;Serializable&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;PlayerSaveData&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;schemaVersion&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="kt"&gt;long&lt;/span&gt; &lt;span class="n"&gt;lastModifiedUtc&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt; &lt;span class="n"&gt;deviceId&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="n"&gt;PlayerProgress&lt;/span&gt; &lt;span class="n"&gt;progress&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="n"&gt;InventoryData&lt;/span&gt; &lt;span class="n"&gt;inventory&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="n"&gt;SettingsData&lt;/span&gt; &lt;span class="n"&gt;settings&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Key principles:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Include a schema version&lt;/strong&gt; - you will need this for migration (covered below).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Include a timestamp&lt;/strong&gt; - &lt;code&gt;lastModifiedUtc&lt;/code&gt; is essential for conflict resolution. Use UTC epoch milliseconds to avoid timezone issues.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Include a device identifier&lt;/strong&gt; - useful for debugging and for conflict resolution UI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Separate volatile and stable data&lt;/strong&gt; - settings change rarely; progress changes constantly. Splitting them reduces sync frequency and payload size.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Layer 2: The Local Persistence Layer
&lt;/h3&gt;

&lt;p&gt;This layer handles reading from and writing to the device's local storage. It operates independently of any cloud service and is the foundation of your offline-first design.&lt;/p&gt;

&lt;p&gt;Responsibilities:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Serialisation&lt;/strong&gt; - convert the save model to bytes. We recommend JSON for debug-friendliness during development and binary (MessagePack or a custom binary format) for production. JSON is human-readable but larger; binary is compact but opaque.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Encryption&lt;/strong&gt; - if your save data contains anything the player could benefit from tampering with (currency, progression, unlocks), encrypt it locally. AES-256 with a device-derived key is a reasonable baseline. For competitive games, this is non-negotiable.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Atomic writes&lt;/strong&gt; - never write directly to the save file. Write to a temporary file, then rename it. This prevents corruption if the app is killed mid-write. On mobile, this is more common than you might expect.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Backup copies&lt;/strong&gt; - maintain the previous save as a rollback option. If the current save is corrupted, the player loses one session instead of everything.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Layer 3: The Cloud Sync Layer
&lt;/h3&gt;

&lt;p&gt;This layer manages communication with the cloud backend. It should be &lt;strong&gt;completely decoupled from the local persistence layer&lt;/strong&gt; via an interface, allowing you to swap cloud providers without touching your save logic.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;interface&lt;/span&gt; &lt;span class="nc"&gt;ICloudSaveProvider&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;Task&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;CloudSaveResult&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;UploadAsync&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;byte&lt;/span&gt;&lt;span class="p"&gt;[]&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;SaveMetadata&lt;/span&gt; &lt;span class="n"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="n"&gt;Task&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;CloudSaveDownload&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;DownloadAsync&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
    &lt;span class="n"&gt;Task&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;bool&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;DeleteAsync&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
    &lt;span class="kt"&gt;bool&lt;/span&gt; &lt;span class="n"&gt;IsAuthenticated&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="k"&gt;get&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This interface can then have concrete implementations for each platform: &lt;code&gt;GameCenterSaveProvider&lt;/code&gt;, &lt;code&gt;GooglePlaySaveProvider&lt;/code&gt;, &lt;code&gt;SteamCloudSaveProvider&lt;/code&gt;, and a &lt;code&gt;PlayFabSaveProvider&lt;/code&gt; or custom backend provider for your own infrastructure.&lt;/p&gt;




&lt;h2&gt;
  
  
  Platform-Specific APIs
&lt;/h2&gt;

&lt;p&gt;Each platform provides its own cloud save API with distinct characteristics. Here is what you need to know about each.&lt;/p&gt;

&lt;h3&gt;
  
  
  Platform Comparison
&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;Platform APIs, quotas, and behaviours change over time. Treat this as an architectural comparison and verify the current platform documentation before implementation.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Apple Game Center&lt;/th&gt;
&lt;th&gt;Google Play Games&lt;/th&gt;
&lt;th&gt;Steam Cloud&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;API&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;GKSavedGame&lt;/code&gt; (GameKit)&lt;/td&gt;
&lt;td&gt;Saved Games API (Play Games SDK v2)&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;ISteamRemoteStorage&lt;/code&gt; (Steamworks)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Storage limit&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No hard limit, Apple recommends under a few MB&lt;/td&gt;
&lt;td&gt;3 MB per save slot (multiple slots)&lt;/td&gt;
&lt;td&gt;Configurable per app (typically 100 MB-1 GB)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Conflict handling&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Detects conflicts, provides array of conflicting saves. You must resolve explicitly&lt;/td&gt;
&lt;td&gt;Conflict callback with local and server versions. You implement resolution&lt;/td&gt;
&lt;td&gt;Last-write-wins by default. Use &lt;code&gt;RemoteStorageFileConflict_t&lt;/code&gt; for custom handling&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Quirks&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Tied to Apple ID. No Game Center sign-in means no cloud save&lt;/td&gt;
&lt;td&gt;Requires Google Play Games sign-in, which some players decline. Need a fallback&lt;/td&gt;
&lt;td&gt;File-based, not structured data. Syncs based on configured file paths in Steamworks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Offline&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Local saves work independently, sync on reconnect&lt;/td&gt;
&lt;td&gt;Caches locally, syncs when connectivity restores&lt;/td&gt;
&lt;td&gt;Steam Deck and offline mode use local cache, sync on reconnection&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Custom Backend (PlayFab, Firebase, or Self-Hosted)
&lt;/h3&gt;

&lt;p&gt;For cross-platform games that need a single source of truth regardless of storefront, a custom backend is often the right choice:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Backend&lt;/th&gt;
&lt;th&gt;Description&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;PlayFab&lt;/td&gt;
&lt;td&gt;Microsoft's BaaS with Player Data APIs and automatic timestamp-based conflict resolution&lt;/td&gt;
&lt;td&gt;Games already using PlayFab for multiplayer or analytics&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Firebase / Firestore&lt;/td&gt;
&lt;td&gt;Google's offering with strong offline support and automatic sync&lt;/td&gt;
&lt;td&gt;Mobile games needing reliable cross-device sync&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Self-hosted&lt;/td&gt;
&lt;td&gt;Maximum control but maximum maintenance burden&lt;/td&gt;
&lt;td&gt;Games with server-authoritative state (like Domi Online, where the server is the canonical source of truth)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; For single-platform games, use the native platform API. For cross-platform games, use a backend service (PlayFab, Firebase, or custom) as the canonical source and treat platform APIs as optional sync accelerators.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Conflict Resolution Strategies
&lt;/h2&gt;

&lt;p&gt;Save conflicts are inevitable in any cloud sync system. The question is not whether they will happen, but how you handle them when they do.&lt;/p&gt;

&lt;h3&gt;
  
  
  Strategy 1: Last Write Wins (LWW)
&lt;/h3&gt;

&lt;p&gt;The simplest approach: compare timestamps and keep the newest save.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; Easy to implement, easy to reason about.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; The "newest" save is not always the "best" save. A player who progresses significantly on Device A, then opens Device B briefly (which uploads an older save with a newer timestamp), will lose their progress.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When to use:&lt;/strong&gt; Casual games where save data is small and progress loss is minor.&lt;/p&gt;

&lt;h3&gt;
  
  
  Strategy 2: Merge by Field
&lt;/h3&gt;

&lt;p&gt;Compare individual fields and take the "best" value from each version. For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;highScore&lt;/code&gt;: take the maximum&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;totalCoinsEarned&lt;/code&gt;: take the maximum&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;levelsCompleted&lt;/code&gt;: take the union of completed levels&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;settings&lt;/code&gt;: take the most recently modified&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; Preserves the most progress. Players rarely notice conflicts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; More complex to implement. Requires defining merge rules for every field. Some fields cannot be merged meaningfully.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When to use:&lt;/strong&gt; Mobile games with incremental progress (puzzle games, idle games, educational titles).&lt;/p&gt;

&lt;h3&gt;
  
  
  Strategy 3: Player Choice
&lt;/h3&gt;

&lt;p&gt;Present the conflict to the player with clear information: "Device A: Level 47, 3 hours ago. Device B: Level 42, 1 hour ago. Which save would you like to keep?"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; The player always gets what they expect. No silent data loss.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; Interrupts the play experience. Confusing for non-technical players. Requires UI work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When to use:&lt;/strong&gt; Games where progress is significant and reversible loss would be frustrating (RPGs, strategy games, lengthy campaigns).&lt;/p&gt;

&lt;h3&gt;
  
  
  Strategy 4: Server-Authoritative (No Conflicts)
&lt;/h3&gt;

&lt;p&gt;The server is the canonical source of truth. The client sends actions (not state), and the server applies them. There is no concept of "conflicting saves" because the server's state is always correct.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; Eliminates conflicts entirely. Prevents cheating.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; Requires a persistent server connection (or an action queue for offline play). Significantly more complex and expensive to build.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When to use:&lt;/strong&gt; Competitive multiplayer games, games with real-money economies, MMOs. This is the architecture we use for &lt;a href="https://oceanviewgames.co.uk/projects/domi" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt;, where the server-authoritative backend built with FishNet on AWS is the single source of truth for all player state.&lt;/p&gt;




&lt;h2&gt;
  
  
  Offline-First Architecture
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Mobile players will lose connectivity. Your game must continue to work.&lt;/strong&gt; This is not an edge case - it is the normal operating condition for mobile games.&lt;/p&gt;

&lt;p&gt;An offline-first save system follows these principles:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The local save is always the primary data source at runtime.&lt;/strong&gt; The game reads from and writes to local storage. Cloud sync happens asynchronously in the background.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Never block gameplay on a network call.&lt;/strong&gt; If the cloud upload fails, queue it for retry. If the cloud download fails, use the local save. The player should never see a loading spinner waiting for a cloud operation.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sync on key events, not on a timer.&lt;/strong&gt; Good sync triggers include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;App launch (download latest cloud save)&lt;/li&gt;
&lt;li&gt;App backgrounding / suspension (upload current save)&lt;/li&gt;
&lt;li&gt;After significant progress milestones (level completion, boss defeat)&lt;/li&gt;
&lt;li&gt;When network connectivity is restored after a loss&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Handle the "cold start" case.&lt;/strong&gt; When a player installs the game on a new device, the local save does not exist. The game must attempt a cloud download before showing the main menu. This is the one case where a brief loading state is acceptable.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Implement retry with exponential backoff.&lt;/strong&gt; Cloud APIs fail. Rate limits kick in. Network conditions fluctuate. A retry strategy with exponential backoff (1s, 2s, 4s, 8s, capped at 60s) prevents hammering the server while ensuring eventual consistency.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Schema Migration for Live Games
&lt;/h2&gt;

&lt;p&gt;Your save data format will change. You will add new features, remove deprecated fields, restructure data for performance, or fix bugs in how data was stored. When this happens, players will have cloud saves in the old format that your new code must be able to read.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Version Field Approach
&lt;/h3&gt;

&lt;p&gt;This is why the &lt;code&gt;schemaVersion&lt;/code&gt; field in your save data model is critical. Every time you change the save structure, increment the version and write a migration function.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight csharp"&gt;&lt;code&gt;&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="n"&gt;PlayerSaveData&lt;/span&gt; &lt;span class="nf"&gt;Migrate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;PlayerSaveData&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;schemaVersion&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt; &lt;span class="m"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="c1"&gt;// v1 -&amp;gt; v2: Added inventory system&lt;/span&gt;
        &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;inventory&lt;/span&gt; &lt;span class="p"&gt;??=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nf"&gt;InventoryData&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;schemaVersion&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt; &lt;span class="m"&gt;3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="c1"&gt;// v2 -&amp;gt; v3: Renamed 'coins' to 'softCurrency'&lt;/span&gt;
        &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;progress&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;softCurrency&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;progress&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;coins&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;schemaVersion&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="n"&gt;CURRENT_VERSION&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Migration Rules
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Migrations must be forward-only.&lt;/strong&gt; Never delete a migration function. A player who has not opened your game since version 1 must be able to migrate through v1 -&amp;gt; v2 -&amp;gt; v3 -&amp;gt; ... -&amp;gt; current in a single chain.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Migrations must be idempotent.&lt;/strong&gt; Running the same migration twice on the same data must produce the same result.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Test migrations with real data.&lt;/strong&gt; Capture save files from each version and include them in your test suite. Automated migration tests catch regressions that manual testing will miss.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Handle missing fields with defaults.&lt;/strong&gt; When deserialising an old save, new fields will be null or zero. Your migration code must provide sensible defaults.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Consider backward compatibility.&lt;/strong&gt; If your game allows older clients to connect (common in soft-launch), the server must handle both old and new save formats simultaneously.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Ship a schema version field from day one, even if you do not plan to change the format. Adding it retroactively to saves that do not have it is the single most painful migration you will ever write.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Security Considerations
&lt;/h2&gt;

&lt;p&gt;Save data security depends on your game's context:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Single-player casual games&lt;/strong&gt; - basic encryption prevents casual tampering but is not worth significant investment. Players who hack their own save data in a non-competitive game are not causing harm.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Competitive games with leaderboards&lt;/strong&gt; - encrypt local saves, validate on upload, and consider server-side verification of key metrics (scores, completion times).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Games with real-money economies&lt;/strong&gt; - server-authoritative state is mandatory. Local save data should be treated as a cache, not a source of truth. This is the approach we took with Domi Online, where the high-stakes economy demanded that all player state be validated server-side.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Common Attack Vectors
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Local save file editing&lt;/strong&gt; - players modify JSON or binary saves on rooted/jailbroken devices. Encryption and checksum validation mitigate this.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Time manipulation&lt;/strong&gt; - players change their device clock to exploit timestamp-based logic (cooldowns, daily rewards). Use server time for anything with economic impact.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Replay attacks&lt;/strong&gt; - players restore a backup save after spending premium currency to "refund" the purchase. Server-side receipt validation and sequential save versioning prevent this.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Implementation Checklist
&lt;/h2&gt;

&lt;p&gt;Before shipping your cloud save system, verify that it handles these scenarios:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Player has no internet connection at launch&lt;/li&gt;
&lt;li&gt;[ ] Cloud download fails mid-transfer&lt;/li&gt;
&lt;li&gt;[ ] Cloud upload fails mid-transfer&lt;/li&gt;
&lt;li&gt;[ ] Player opens game on two devices simultaneously&lt;/li&gt;
&lt;li&gt;[ ] Player's device clock is set incorrectly&lt;/li&gt;
&lt;li&gt;[ ] Player updates the app and the save schema has changed&lt;/li&gt;
&lt;li&gt;[ ] Player uninstalls and reinstalls the app&lt;/li&gt;
&lt;li&gt;[ ] Player declines platform sign-in (Game Center, Google Play Games)&lt;/li&gt;
&lt;li&gt;[ ] Cloud storage quota is exceeded&lt;/li&gt;
&lt;li&gt;[ ] Player's cloud save is corrupted or empty&lt;/li&gt;
&lt;li&gt;[ ] Player switches platform accounts&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each of these is a real scenario we have encountered in production games. Testing them before launch is significantly cheaper than debugging them after.&lt;/p&gt;




&lt;h2&gt;
  
  
  Choosing the Right Approach for Your Game
&lt;/h2&gt;

&lt;p&gt;The architecture you need depends on your game's characteristics:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Game Type&lt;/th&gt;
&lt;th&gt;Recommended Approach&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Single-player mobile (casual)&lt;/td&gt;
&lt;td&gt;Local save + platform API (Game Center / Google Play) with LWW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Single-player mobile (mid-core)&lt;/td&gt;
&lt;td&gt;Local save + platform API with merge-by-field&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cross-platform single-player&lt;/td&gt;
&lt;td&gt;Local save + backend service (PlayFab/Firebase) with player choice on conflict&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cooperative multiplayer&lt;/td&gt;
&lt;td&gt;Backend service with server-authoritative state for shared data, local for settings&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Competitive multiplayer / MMO&lt;/td&gt;
&lt;td&gt;Fully server-authoritative, local cache for offline resilience&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Start with the simplest approach that meets your requirements. You can always upgrade from LWW to merge-by-field, or from platform APIs to a custom backend, if your game's needs evolve.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/gamedevelopment" rel="noopener noreferrer"&gt;Unity Game Development Services&lt;/a&gt; - Our full-cycle Unity development offering&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/network-engineering" rel="noopener noreferrer"&gt;Multiplayer &amp;amp; Network Engineering&lt;/a&gt; - How we build scalable multiplayer backends&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/projects/domi" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt; - Our MMORPG project with server-authoritative cloud architecture&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/blog/posts/cross-platform-multiplayer-networking-unity" rel="noopener noreferrer"&gt;Cross-Platform Multiplayer Networking in Unity&lt;/a&gt; - Deep dive into Unity networking fundamentals&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>The True Cost of Game Development Outsourcing</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Fri, 04 Sep 2026 12:03:32 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/the-true-cost-of-game-development-outsourcing-35p0</link>
      <guid>https://dev.to/oceanviewgames/the-true-cost-of-game-development-outsourcing-35p0</guid>
      <description>&lt;p&gt;When studios compare outsourcing options, the conversation almost always starts - and too often ends - with hourly or daily rates. A provider quoting half the rate looks half the price. In practice, rate is only one variable in the cost of getting reliable, production-ready work into your game.&lt;/p&gt;

&lt;p&gt;Except the maths is wrong. Or rather, it is incomplete.&lt;/p&gt;

&lt;p&gt;The hourly rate is the &lt;strong&gt;sticker price, not the total cost of ownership&lt;/strong&gt;. The real cost of outsourcing includes communication overhead, ramp-up time, quality variance, IP risk, timezone friction, management burden, and the cost of getting it wrong. These hidden costs can erase much of the apparent saving from a lower rate - or make a more expensive partner cheaper once delivery risk and internal time are included.&lt;/p&gt;

&lt;p&gt;We write this from a particular vantage point. Ocean View Games is a UK-based &lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;co-development partner&lt;/a&gt;. We have sat on both sides of the outsourcing relationship - as the team being outsourced to, and as developers who have worked alongside outsourced teams on large studio projects. We have seen what works, what does not, and what the actual cost drivers are.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Visible Costs
&lt;/h2&gt;

&lt;p&gt;Let us start with the costs that do appear on invoices. These are the numbers procurement teams compare.&lt;/p&gt;

&lt;h3&gt;
  
  
  Hourly or Daily Rates
&lt;/h3&gt;

&lt;p&gt;The direct cost of developer time is the easiest number to compare, but quoted rates are shaped by more than geography. Seniority, specialism, contract length, whether project management is included, and how much responsibility the partner is taking all affect the number.&lt;/p&gt;

&lt;p&gt;When comparing providers, normalise the quote before drawing conclusions:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Question&lt;/th&gt;
&lt;th&gt;Why It Matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Who will actually work on the project?&lt;/td&gt;
&lt;td&gt;A senior-led team and a junior-heavy team are not equivalent purchases&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What is included in the rate?&lt;/td&gt;
&lt;td&gt;Production, QA, technical leadership, meetings, and support may be inside or outside the quote&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How much working-day overlap is there?&lt;/td&gt;
&lt;td&gt;Real-time collaboration changes iteration speed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Is the scope deliverable-based or time-based?&lt;/td&gt;
&lt;td&gt;A fixed deliverable transfers different risk than staff augmentation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What happens after delivery?&lt;/td&gt;
&lt;td&gt;Documentation, handover, warranty fixes, and ongoing support affect total cost&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The useful comparison is not "who has the lowest hourly rate?" It is "what will it cost us to get this scope integrated, accepted, and maintainable?"&lt;/p&gt;

&lt;h3&gt;
  
  
  Project Management and Coordination
&lt;/h3&gt;

&lt;p&gt;Most outsourcing providers include a project manager in their rates, but this person manages the outsourced team's internal workflow - not the integration with your team. You will still need someone on your side to manage the relationship, review deliverables, and translate requirements. Budget explicit internal time for coordination rather than assuming the provider's project manager removes the need for client-side ownership.&lt;/p&gt;

&lt;h3&gt;
  
  
  Tooling and Infrastructure
&lt;/h3&gt;

&lt;p&gt;If the outsourced team needs access to your version control, project management tools, CI/CD pipeline, and communication platforms, there may be additional licence costs. Some providers use their own tools, which creates a handover problem later.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Hidden Costs
&lt;/h2&gt;

&lt;p&gt;This is where the real total cost emerges. These costs do not appear on any invoice, but they are real and measurable.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Communication Overhead
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Communication is the single largest hidden cost in outsourcing&lt;/strong&gt;, and it scales non-linearly with team size and cultural distance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Shared language and context&lt;/strong&gt; - even when everybody communicates well, phrases like "the inventory should feel snappy" are ambiguous. External teams usually need more explicit acceptance criteria because they have less product context. Writing and maintaining that context takes time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Communication norms&lt;/strong&gt; - teams differ in how quickly they challenge requirements, surface uncertainty, and escalate blockers. The important factor is not nationality; it is whether the working relationship makes uncertainty visible early.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Asynchronous communication cycles&lt;/strong&gt; - large timezone gaps can turn a quick clarification into a next-day response. That is manageable for self-contained work, but expensive when a feature needs rapid iteration with designers and engineers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Practical impact:&lt;/strong&gt; Track coordination time during the first few weeks. If senior people on your side are spending several hours a week rewriting briefs, chasing clarifications, or reviewing avoidable rework, include that time in the effective cost of the engagement.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Ramp-Up Time
&lt;/h3&gt;

&lt;p&gt;Every new developer, whether in-house or outsourced, needs time to understand your codebase, tools, conventions, and domain. The question is how long this ramp-up takes and who pays for it.&lt;/p&gt;

&lt;p&gt;Ramp-up is driven much more by relevance than postcode. A team that already knows your engine version, platform constraints, backend pattern, and type of codebase can start making useful changes sooner. A team learning all of those things at once will need more review and context before it can work independently.&lt;/p&gt;

&lt;p&gt;That difference is worth modelling explicitly. Ask every provider what the first two weeks look like, which people will be onboarding, what they need from your team, and when you should expect the first production contribution.&lt;/p&gt;

&lt;p&gt;When we join a project as a &lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;co-development partner&lt;/a&gt;, we aim to make the first useful contribution quickly. Relevant experience on large Unity codebases, including David's previous work on RuneScape Mobile at Jagex and our work on &lt;a href="https://oceanviewgames.co.uk/projects/domi" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt;, reduces the amount of domain learning required before we can help.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Quality Variance and Rework
&lt;/h3&gt;

&lt;p&gt;The most expensive code is code that has to be written twice.&lt;/p&gt;

&lt;p&gt;Quality variance is the gap between what you expected and what you received. It manifests in several ways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Code that works but is not production-ready&lt;/strong&gt; - no comments, no tests, no adherence to your coding standards. It functions but creates technical debt that your in-house team must clean up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code that does not integrate&lt;/strong&gt; - the outsourced team built a module in isolation that does not mesh with your architecture. Integration work falls on you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Misunderstood requirements&lt;/strong&gt; - the feature was built to specification, but the specification was interpreted differently. Rework ensues.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Missing edge cases&lt;/strong&gt; - the happy path works; error handling, null checks, and boundary conditions do not. These bugs surface in QA or, worse, in production.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Practical impact:&lt;/strong&gt; Measure rework as part of the engagement. Track how often delivered work is rejected, substantially rewritten, or needs unexpected integration work. A low rate is not valuable if the same feature is effectively paid for twice.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; A lower rate is not automatically a lower cost. Calculate the effective cost of usable, production-ready output, including the time your own team spends getting it there.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  4. Timezone Friction
&lt;/h3&gt;

&lt;p&gt;Timezone differences affect more than communication speed. They affect your ability to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Iterate quickly&lt;/strong&gt; - game development is iterative. "Try this, see how it feels, adjust" is the core workflow. When each iteration cycle takes 24 hours instead of 30 minutes, the feedback loop breaks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Respond to emergencies&lt;/strong&gt; - your live game is down, and the team that wrote the server code is asleep. How long can you wait?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Participate in standups and reviews&lt;/strong&gt; - if overlap is minimal, either your team or theirs is attending meetings outside working hours. This is unsustainable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Maintain team cohesion&lt;/strong&gt; - when people never interact in real-time, they do not form working relationships. The outsourced team becomes "them," not "us."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The overlap question:&lt;/strong&gt; There is no magic number of shared hours. The right amount depends on the work. A self-contained asset task may need very little overlap; embedded engineering, debugging, and design iteration benefit from a reliable daily window where the relevant people can talk in real time. Define that window before the engagement starts.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Intellectual Property Risk
&lt;/h3&gt;

&lt;p&gt;When you outsource game development, you are sharing your source code, design documents, art assets, and business strategy with an external party. This creates IP risk that must be managed through legal, technical, and procedural controls.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Legal protections:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Non-Disclosure Agreements (NDAs) - essential, but enforceability varies by jurisdiction. An NDA governed by UK law is straightforward to enforce in the UK. Enforcing it in a jurisdiction with different IP protections is more complex and expensive.&lt;/li&gt;
&lt;li&gt;Work-for-hire agreements - ensure that all code, assets, and documentation produced are owned by you, not the outsourcing provider. This is standard but must be explicit.&lt;/li&gt;
&lt;li&gt;IP assignment clauses - separate from work-for-hire, these ensure any background IP contributed by the provider is licensed to you appropriately.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Technical protections:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Compartmentalised access - the outsourced team should only access the repositories and systems they need. Not your entire codebase.&lt;/li&gt;
&lt;li&gt;Code review gates - all contributions must pass review by your in-house team before merging.&lt;/li&gt;
&lt;li&gt;Secure development environments - VPN access, no local code storage, audit logging.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Practical risk assessment:&lt;/strong&gt; For most professional outsourcing relationships, IP theft is rare. The greater risk is IP leakage through poor security practices (unencrypted laptops, shared credentials) rather than malicious intent. Proper onboarding and security protocols mitigate this effectively.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Management Burden
&lt;/h3&gt;

&lt;p&gt;Managing an outsourced team takes more of your time than managing an equivalent in-house team. This is your time - the most expensive time in the project.&lt;/p&gt;

&lt;p&gt;Responsibilities that fall on you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Writing more detailed specifications (because you cannot explain context verbally)&lt;/li&gt;
&lt;li&gt;Reviewing code and deliverables more carefully (because the team is less familiar with your standards)&lt;/li&gt;
&lt;li&gt;Mediating between in-house and outsourced teams (integration points, merge conflicts, architectural decisions)&lt;/li&gt;
&lt;li&gt;Handling administrative overhead (invoicing, contracts, access management)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Practical impact:&lt;/strong&gt; Put a value on the client-side management burden. If your technical lead spends a day each week coordinating external work, that day belongs in the cost model just as surely as an invoice does.&lt;/p&gt;




&lt;h2&gt;
  
  
  Comparing the Models: Offshore vs Nearshore vs UK-Based
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Offshore (Large Timezone Gap)
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Often a good fit for:&lt;/strong&gt; Well-defined, self-contained work with clear acceptance criteria and a workflow designed for asynchronous delivery.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; Slow feedback loops on work that depends on frequent design or engineering decisions.&lt;/p&gt;

&lt;h3&gt;
  
  
  Nearshore (Meaningful Working-Day Overlap)
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Often a good fit for:&lt;/strong&gt; Ongoing support where real-time collaboration matters but the client is comfortable working across jurisdictions and organisations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; Assuming proximity guarantees process fit. Team seniority, communication, and ownership still matter more than the label.&lt;/p&gt;

&lt;h3&gt;
  
  
  Local / Same-Timezone Partner
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Often a good fit for:&lt;/strong&gt; Embedded engineering, architectural decisions, workshops, rapid iteration, and work where the external team must behave like part of the internal team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Watch for:&lt;/strong&gt; Paying a premium for proximity when the work is actually self-contained and does not benefit from it.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Geography is a constraint, not a quality score. Compare the collaboration model to the work you need done, then compare total cost rather than assuming one region is inherently better than another.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What to Look for in an Outsourcing Partner
&lt;/h2&gt;

&lt;p&gt;Regardless of geography, the factors that predict outsourcing success are:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Relevant Portfolio
&lt;/h3&gt;

&lt;p&gt;Have they built games like yours? Not just "Unity games" - your platform, type of codebase, and technical constraints. When we partnered with Domi Online, experience with large live-game systems and David's previous work on RuneScape Mobile at Jagex meant we were familiar with many of the architectural problems from the start.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Communication Quality
&lt;/h3&gt;

&lt;p&gt;Test this before signing. How quickly do they respond to your initial enquiry? How clearly do they explain their process? Do they ask good questions about your project, or do they just quote a rate? The pre-sales interaction is a reliable predictor of the working relationship.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Process Maturity
&lt;/h3&gt;

&lt;p&gt;Do they use version control? Do they have a code review process? Do they write tests? Do they use project management tools? These are not "nice to haves" - they are the minimum requirements for professional software development. Be wary of any provider that cannot clearly articulate their development process.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. References from Similar Projects
&lt;/h3&gt;

&lt;p&gt;Ask for references and actually call them. Ask specifically about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Ramp-up time&lt;/li&gt;
&lt;li&gt;Communication quality&lt;/li&gt;
&lt;li&gt;Code quality on delivery&lt;/li&gt;
&lt;li&gt;How they handled disagreements or scope changes&lt;/li&gt;
&lt;li&gt;Whether the reference would hire them again&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  5. Team Stability
&lt;/h3&gt;

&lt;p&gt;Will the same developers work on your project throughout, or will they be rotated to other clients? Developer rotation resets the ramp-up clock every time. Contractually binding named developers to your project is worth negotiating.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Clear IP Agreements
&lt;/h3&gt;

&lt;p&gt;The contract should explicitly state:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You own all code, assets, and documentation produced&lt;/li&gt;
&lt;li&gt;The provider will not reuse your code on other projects&lt;/li&gt;
&lt;li&gt;Background IP (frameworks, tools) is licensed to you&lt;/li&gt;
&lt;li&gt;Source code is delivered incrementally, not only at project end&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Making the Decision
&lt;/h2&gt;

&lt;p&gt;Here is a practical framework for choosing your outsourcing model:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;If your priority is...&lt;/th&gt;
&lt;th&gt;Consider...&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Lowest possible cost for well-defined tasks&lt;/td&gt;
&lt;td&gt;Offshore with detailed specifications&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Balance of cost and collaboration&lt;/td&gt;
&lt;td&gt;Nearshore with daily overlap&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Maximum integration and minimum friction&lt;/td&gt;
&lt;td&gt;UK-based co-development partner&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Surge capacity for a specific phase&lt;/td&gt;
&lt;td&gt;Short-term co-development engagement&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Long-term ongoing support&lt;/td&gt;
&lt;td&gt;Retained co-development relationship&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The worst outcome is not choosing the "wrong" label - it is choosing a model without accounting for the hidden costs. A higher-priced engagement can be cheaper overall if it reduces internal rework and protects the delivery schedule.&lt;/p&gt;




&lt;h2&gt;
  
  
  How We Approach Co-Development
&lt;/h2&gt;

&lt;p&gt;At Ocean View Games, our &lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;co-development model&lt;/a&gt; is designed to minimise the hidden costs described above:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Embedded integration&lt;/strong&gt; - we join your Slack, attend your standups, commit to your repo. We operate as an extension of your team, not a separate entity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;UK-based, UK timezone&lt;/strong&gt; - we have a full working-day overlap with UK clients, which makes real-time pairing, debugging, and iteration straightforward.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Senior developers only&lt;/strong&gt; - our experience spans David's previous RuneScape Mobile work at Jagex and our &lt;a href="https://oceanviewgames.co.uk/case-studies/domi-online-unity-mmo" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt; work, alongside mobile, educational, and legacy projects.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clean handoff&lt;/strong&gt; - all code is documented, commented, and follows your style guide. When the engagement ends, your team picks up without confusion. No lock-in.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;UK legal jurisdiction&lt;/strong&gt; - our contracts use English law, which can simplify procurement for UK clients.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We are not the cheapest option on a rate card. We are, for many studios, the most cost-effective option when total cost of ownership is considered.&lt;/p&gt;




&lt;h2&gt;
  
  
  Calculating Your True Cost
&lt;/h2&gt;

&lt;p&gt;Before engaging any outsourcing partner, build a total cost model:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Direct cost&lt;/strong&gt; - hourly rate x estimated hours&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ramp-up cost&lt;/strong&gt; - weeks to productivity x weekly rate (producing minimal output)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Communication overhead&lt;/strong&gt; - your team's time spent on specifications, reviews, meetings, and coordination&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rework budget&lt;/strong&gt; - the cost of rejected work, integration fixes, and substantial rewrites; estimate this from the provider's references or a paid trial rather than a generic percentage&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Management burden&lt;/strong&gt; - your lead's time redirected to coordination (value this at their effective rate)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Risk premium&lt;/strong&gt; - the cost of delay if things go wrong (missed market window, delayed revenue)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Add these together. Compare the totals, not the hourly rates. The answer may surprise you.&lt;/p&gt;

&lt;p&gt;Use our &lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator" rel="noopener noreferrer"&gt;game development cost estimator&lt;/a&gt; to build a baseline budget, then layer these outsourcing-specific costs on top.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/codevelopment" rel="noopener noreferrer"&gt;Co-Development &amp;amp; Staff Augmentation&lt;/a&gt; - How we embed into your team&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/game-development-cost-estimator" rel="noopener noreferrer"&gt;Game Development Cost Estimator&lt;/a&gt; - Interactive tool to estimate your project budget&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/game-studios" rel="noopener noreferrer"&gt;Game Studios Industry&lt;/a&gt; - How we support game studios with specialist capacity&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/blog/posts/co-development-vs-freelancers-vs-hiring" rel="noopener noreferrer"&gt;Co-Development vs Freelancers vs Full-Time Hires&lt;/a&gt; - Comparing the three main team-scaling models&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>Porting a 20-Year-Old Game to Mobile: Lessons from RuneScape</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Mon, 24 Aug 2026 11:16:46 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/porting-a-20-year-old-game-to-mobile-lessons-from-runescape-1d1a</link>
      <guid>https://dev.to/oceanviewgames/porting-a-20-year-old-game-to-mobile-lessons-from-runescape-1d1a</guid>
      <description>&lt;p&gt;RuneScape is one of the longest-running MMORPGs in history. First released in 2001, it had already accumulated more than 15 years of content, systems, interfaces, and player expectations when I joined the mobile effort. Bringing a game with that history to iOS and Android is a very different problem from porting a title designed with mobile in mind.&lt;/p&gt;

&lt;p&gt;I worked at Jagex from 2017 to 2019 as a Technical Developer on the RuneScape Mobile team. That put me inside the practical work of adapting a long-lived desktop game for touch devices and much more constrained hardware.&lt;/p&gt;

&lt;p&gt;This article shares the technical lessons I took from that experience and how they now inform the &lt;a href="https://oceanviewgames.co.uk/services/mobile" rel="noopener noreferrer"&gt;mobile development&lt;/a&gt; and porting work we do.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important note on attribution:&lt;/strong&gt; The RuneScape work discussed here was performed during my previous employment at Jagex Games Studio. RuneScape is a trademark of Jagex Ltd. Ocean View Games was not a contractor or agency partner on the project. I reference the experience because the lessons directly inform how we approach mobile and legacy codebases today.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Scale of the Challenge
&lt;/h2&gt;

&lt;p&gt;To understand why porting RuneScape to mobile was so technically demanding, you need to appreciate what the game actually contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Over 20 years of accumulated content&lt;/strong&gt; built by hundreds of developers across multiple generations of the codebase&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A large set of skills and activities&lt;/strong&gt;, many with their own interfaces and interaction patterns&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Years of quests and bespoke content&lt;/strong&gt; built across multiple generations of the game&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A live, persistent world&lt;/strong&gt; shared between mobile and desktop players&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A player-driven economy&lt;/strong&gt; that had to behave consistently across platforms&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An established community&lt;/strong&gt; with strong expectations about how the game should look and feel&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This was not a case of building a simplified "mobile version" of the game. The mandate was &lt;strong&gt;full cross-platform parity&lt;/strong&gt;: a mobile player needed to be able to do everything a desktop player could, in the same world, at the same time.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; When porting a legacy title to mobile, the first and most important question is scope. "Full parity" and "mobile companion app" are fundamentally different projects with different technical requirements, timelines, and budgets. Define this boundary clearly before writing a single line of code.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Lesson 1: Legacy Code Is the Real Boss Fight
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Understanding the Codebase
&lt;/h3&gt;

&lt;p&gt;RuneScape's codebase had been evolving for over 15 years by the time the mobile port began. It contained code written by developers who had long since left the company, using patterns and conventions that predated modern best practices. The game's scripting language, RuneScript, was a proprietary system unique to Jagex.&lt;/p&gt;

&lt;p&gt;The practical challenge was not just "make this run on mobile." It was "make this run on mobile without destabilising the desktop experience for an established live-game community."&lt;/p&gt;

&lt;h3&gt;
  
  
  The Lesson: Audit Before You Architect
&lt;/h3&gt;

&lt;p&gt;Before our team wrote any mobile-specific code, we conducted a thorough audit of the systems we would need to touch. This revealed:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Hard-coded screen dimensions&lt;/strong&gt; embedded deep in UI rendering logic&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mouse-specific input assumptions&lt;/strong&gt; baked into core gameplay mechanics (right-click context menus were fundamental to the game's interaction model)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Desktop-specific rendering paths&lt;/strong&gt; that assumed minimum hardware specifications far above any mobile device&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory usage patterns&lt;/strong&gt; that were acceptable on desktop (2GB+ RAM available) but catastrophic on mobile (often limited to 1-2GB total, shared with the OS)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The audit took weeks, but it saved months. Every assumption we identified and documented upfront was a crisis we avoided during production.&lt;/p&gt;

&lt;h3&gt;
  
  
  Applying This at Ocean View Games
&lt;/h3&gt;

&lt;p&gt;This experience directly informed how we approach every porting project today. When we partnered with Inferna Games to remake Nub (originally a Java app for the Ouya console) in Unity for iOS, Android, and Steam, we started with the same audit-first methodology. Even with a much smaller codebase, the discipline of cataloguing every platform assumption before writing new code prevented the kind of cascading bugs that derail porting timelines.&lt;/p&gt;




&lt;h2&gt;
  
  
  Lesson 2: Touch UI Is Not "Smaller Desktop UI"
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Fundamental Problem
&lt;/h3&gt;

&lt;p&gt;RuneScape's desktop interface was designed for a mouse and keyboard. The game relied heavily on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Right-click context menus&lt;/strong&gt; for virtually every interaction (talk to NPC, pick up item, examine, attack)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hover states&lt;/strong&gt; to preview information before clicking&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Small, dense UI panels&lt;/strong&gt; that displayed enormous amounts of information simultaneously (inventory, equipment, prayer, magic, combat stats - all visible at once)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keyboard shortcuts&lt;/strong&gt; for quick switching between interface panels&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these patterns translate directly to touchscreens. A finger is far less precise than a mouse cursor, touch has no hover state, right-click needs an alternative, and a phone cannot comfortably display the same information density as a desktop monitor.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Solution: Context-Sensitive Adaptive UI
&lt;/h3&gt;

&lt;p&gt;The important design direction was to avoid simply scaling down the desktop interface. A mobile UI needs to adapt the information and interactions to the player's current context. The core principles are:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Show only what matters now.&lt;/strong&gt; When a player is in combat, surface combat-relevant panels (health, prayer, special attack) and collapse non-essential ones (skills, quest log). When the player is skilling, swap the priority.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Give desktop-only interactions a touch-native equivalent.&lt;/strong&gt; Right-click and hover behaviours need deliberate replacements such as long-press, tap-and-hold, contextual actions, or dedicated controls.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Expand tap targets aggressively.&lt;/strong&gt; Visual elements that are easy to click with a cursor often need larger or more forgiving hit areas on touch devices.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Redesign, do not just resize.&lt;/strong&gt; Any interaction built around precision mouse input should be reviewed as a mobile design problem. Preserve the intent of the mechanic, but be willing to change how the player expresses it.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  The Lesson: Invest in a Dedicated Mobile UI Pass
&lt;/h3&gt;

&lt;p&gt;A common mistake in porting projects is treating mobile UI as a configuration change - swap out some assets, scale some panels, ship it. This produces games that technically run on mobile but feel terrible to play.&lt;/p&gt;

&lt;p&gt;My recommendation, based on that RuneScape experience: &lt;strong&gt;budget for a full UI redesign&lt;/strong&gt; as a first-class work item. This does not mean changing the visual style. It means rethinking how every interaction maps to touch input and how information is prioritised for a smaller viewport.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; The gap between "works on mobile" and "feels native on mobile" is almost entirely a UI/UX problem. Invest in dedicated mobile interaction design. Your players will notice the difference immediately.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Lesson 3: Cross-Platform Parity Requires Server-Side Discipline
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Synchronisation Problem
&lt;/h3&gt;

&lt;p&gt;RuneScape Mobile was not a separate game. Mobile and desktop players existed in the same world on the same servers. This meant:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A mobile player and a desktop player could trade items face-to-face&lt;/li&gt;
&lt;li&gt;A mobile player could participate in the same boss fight as desktop players&lt;/li&gt;
&lt;li&gt;The game's economy, driven by the Grand Exchange marketplace, operated identically regardless of platform&lt;/li&gt;
&lt;li&gt;Any content update had to work on both platforms simultaneously&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Network Packet Optimisation
&lt;/h3&gt;

&lt;p&gt;Desktop RuneScape could assume a stable broadband connection. Mobile could not. The mobile effort had to account for cellular connections as well as desktop broadband. That reinforced an important porting lesson: bandwidth, latency, reconnect behaviour, and failure recovery all need to be treated as mobile design constraints rather than tested at the end.&lt;/p&gt;

&lt;p&gt;For a mobile port, that means reviewing the network path with mobile conditions in mind: payload size, reconnect behaviour, timeout assumptions, latency tolerance, and which state is truly critical. The exact implementation depends on the game's architecture, but those questions should be answered deliberately rather than inherited from the desktop client.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Lesson: Define "Parity" Precisely
&lt;/h3&gt;

&lt;p&gt;"Cross-platform parity" can mean different things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Data parity:&lt;/strong&gt; The same account, progression, and items across platforms (essential)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Feature parity:&lt;/strong&gt; The same gameplay features available on all platforms (desirable but expensive)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Experience parity:&lt;/strong&gt; The game feels equally good to play on all platforms (the highest bar, and the most important for player retention)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We now apply this three-tier framework to every porting project we scope. For our ongoing work on &lt;a href="https://oceanviewgames.co.uk/case-studies/domi-online-unity-mmo" rel="noopener noreferrer"&gt;Domi Online&lt;/a&gt;, we designed the network architecture with cross-platform play in mind from the start, using FishNet to build lightweight server-authoritative backends that optimise bandwidth for mobile clients without compromising the desktop experience.&lt;/p&gt;




&lt;h2&gt;
  
  
  Lesson 4: Optimise for the Worst Device, Not the Best
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The Android Fragmentation Reality
&lt;/h3&gt;

&lt;p&gt;When targeting Android, you are not targeting one device. You are targeting thousands. During the RuneScape Mobile development, we had to ensure the game ran acceptably on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Flagship devices&lt;/strong&gt; (Samsung Galaxy S series, Google Pixel) with powerful GPUs and 6-8GB of RAM&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mid-range devices&lt;/strong&gt; that represented the bulk of the player base&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Budget devices&lt;/strong&gt; with as little as 2GB of RAM and GPUs that struggled with basic shader operations&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Tiered Quality Settings
&lt;/h3&gt;

&lt;p&gt;A practical response is a &lt;strong&gt;tiered quality strategy&lt;/strong&gt; so that the game can trade visual cost for stability on weaker devices. Typical controls include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Draw distance and object density&lt;/li&gt;
&lt;li&gt;Texture resolution and compression format&lt;/li&gt;
&lt;li&gt;Shadow quality (or complete shadow disabling on the lowest tier)&lt;/li&gt;
&lt;li&gt;Particle effect density&lt;/li&gt;
&lt;li&gt;Frame-rate targets or caps appropriate to the device and thermal budget&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Whatever the detection strategy, the default should be conservative enough that supported devices start in a playable state rather than making the player diagnose performance themselves.&lt;/p&gt;

&lt;h3&gt;
  
  
  Battery and Thermal Management
&lt;/h3&gt;

&lt;p&gt;Mobile games face constraints that desktop games never consider:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Thermal throttling:&lt;/strong&gt; When a phone overheats, the OS forcibly reduces CPU/GPU clock speeds, causing frame rate drops and stuttering&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Battery drain:&lt;/strong&gt; Heavy CPU/GPU use can make a technically smooth game unpleasant to play for long sessions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Background interruptions:&lt;/strong&gt; Phone calls, notifications, and OS memory pressure can suspend or kill the game process at any time&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The practical lesson is to test sustained sessions, not just a five-minute benchmark. A build that starts at 60fps can perform very differently after the device heats up. Profile frame time, loading spikes, memory pressure, and thermal behaviour on real hardware.&lt;/p&gt;




&lt;h2&gt;
  
  
  Lesson 5: Your Existing Players Are Your Toughest Critics
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Managing Community Expectations
&lt;/h3&gt;

&lt;p&gt;RuneScape's player community had been playing the game for years, sometimes decades. They had strong opinions about every UI element, every interaction pattern, and every visual detail. Any change made for mobile that visibly affected the desktop experience generated immediate and vocal feedback.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Lesson: Isolate Mobile Changes
&lt;/h3&gt;

&lt;p&gt;Wherever possible, mobile-specific behaviour should sit behind &lt;strong&gt;platform abstraction layers&lt;/strong&gt; rather than leaking platform checks throughout shared gameplay code. For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Input handling was routed through an abstraction that returned platform-appropriate interactions&lt;/li&gt;
&lt;li&gt;UI layouts used a responsive system that adapted to screen size without changing the underlying data model&lt;/li&gt;
&lt;li&gt;Performance optimisations that benefited both platforms (reduced draw calls, better batching) were implemented in shared code; mobile-only compromises (reduced texture quality) were isolated behind platform checks&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That extra structure costs some time up front, but it reduces the risk that a mobile-specific compromise accidentally degrades the desktop experience.&lt;/p&gt;




&lt;h2&gt;
  
  
  How These Lessons Inform Our Work Today
&lt;/h2&gt;

&lt;p&gt;Every project we take on at Ocean View Games is shaped by this experience. Whether we are building a new title from scratch or porting an existing game to mobile, we apply the same principles:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Audit first.&lt;/strong&gt; Catalogue every platform assumption in the existing codebase before writing new code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Design for touch natively.&lt;/strong&gt; Never treat mobile UI as a scaled-down version of the desktop interface.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Define parity levels explicitly.&lt;/strong&gt; Agree with the client on exactly what "cross-platform" means before scoping the work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Optimise for the floor, not the ceiling.&lt;/strong&gt; Target the weakest supported device first. If it runs well there, it will run well everywhere.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Isolate platform-specific code.&lt;/strong&gt; Use abstraction layers to prevent mobile changes from breaking the existing experience.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you are considering a mobile port of an existing title, our &lt;a href="https://oceanviewgames.co.uk/case-studies/mobile-game-porting-ui-optimization" rel="noopener noreferrer"&gt;mobile game porting case study&lt;/a&gt; provides a detailed technical breakdown of this approach. For new projects where you want to target mobile from Day 1, our &lt;a href="https://oceanviewgames.co.uk/services/mobile" rel="noopener noreferrer"&gt;mobile game development services&lt;/a&gt; page outlines how we architect for cross-platform from the start.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/case-studies/mobile-game-porting-ui-optimization" rel="noopener noreferrer"&gt;RuneScape Mobile Porting Case Study&lt;/a&gt; - A detailed technical breakdown of the porting challenges and solutions&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/mobile" rel="noopener noreferrer"&gt;Mobile Game Development Services&lt;/a&gt; - Our end-to-end mobile development capabilities&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/projects/runescape" rel="noopener noreferrer"&gt;RuneScape Mobile Project&lt;/a&gt; - Full project details and gallery&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/porting-feasibility-checker" rel="noopener noreferrer"&gt;Porting Feasibility Checker&lt;/a&gt; - Assess the complexity of porting your game.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/resources/platform-readiness-checklist" rel="noopener noreferrer"&gt;Platform Readiness Checklist&lt;/a&gt; - Verify your game meets platform requirements.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
    <item>
      <title>SCORM vs Custom API: Integrating Games with Learning Management Systems</title>
      <dc:creator>Ocean View Games</dc:creator>
      <pubDate>Mon, 17 Aug 2026 13:43:48 +0000</pubDate>
      <link>https://dev.to/oceanviewgames/scorm-vs-custom-api-integrating-games-with-learning-management-systems-2j0o</link>
      <guid>https://dev.to/oceanviewgames/scorm-vs-custom-api-integrating-games-with-learning-management-systems-2j0o</guid>
      <description>&lt;p&gt;When an educational institution commissions a game, one of the first questions on the requirements document is: "Will it integrate with our LMS?" The answer is almost always "yes." The follow-up question - how - is where the real engineering decisions begin.&lt;/p&gt;

&lt;p&gt;Our educational work ranges from &lt;a href="https://oceanviewgames.co.uk/projects/stoneyvocabbuilder" rel="noopener noreferrer"&gt;The Language Conservancy&lt;/a&gt; (Vocab Builder) to projects delivered during previous agency tenures for institutions including Cambridge University Press, the BBC, and European university consortia through the EU Horizon 2020 programme (&lt;a href="https://oceanviewgames.co.uk/projects/navigo" rel="noopener noreferrer"&gt;Navigo&lt;/a&gt;). Institutional projects repeatedly raise the same integration questions: where the game runs, how identity is passed in, what progress must be reported, and which system owns the learning record.&lt;/p&gt;

&lt;p&gt;This post compares the two primary approaches to LMS integration - &lt;strong&gt;SCORM (the established standard) and custom APIs (the flexible alternative)&lt;/strong&gt; - and provides practical guidance on when each approach makes sense.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Problem Are We Solving?
&lt;/h2&gt;

&lt;p&gt;Before comparing solutions, it is worth being precise about what LMS integration actually needs to accomplish:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Launch&lt;/strong&gt; - the LMS needs to open the game in the right context (correct student, correct assignment, correct lesson).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Track progress&lt;/strong&gt; - the LMS needs to know how far the student has progressed through the content.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Report scores&lt;/strong&gt; - test results, quiz scores, and performance metrics need to flow from the game back to the LMS gradebook.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Record completion&lt;/strong&gt; - the LMS needs to know when the student has finished the activity so it can unlock the next one or mark the assignment as done.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Resume&lt;/strong&gt; - if the student stops mid-session, the game should pick up where they left off when they return.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These five requirements are common to virtually every educational game integration. The question is which technology best delivers them for your specific context.&lt;/p&gt;




&lt;h2&gt;
  
  
  SCORM: The Established Standard
&lt;/h2&gt;

&lt;p&gt;SCORM (Sharable Content Object Reference Model) is the most widely adopted e-learning standard. Maintained by ADL (Advanced Distributed Learning), it defines how learning content communicates with an LMS.&lt;/p&gt;

&lt;h3&gt;
  
  
  SCORM 1.2
&lt;/h3&gt;

&lt;p&gt;Released in 2001, SCORM 1.2 is still widely encountered in established e-learning environments. Major LMS products commonly support it, although the exact launch, reporting, and packaging behaviour varies by platform and configuration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it works:&lt;/strong&gt; The LMS launches your game in an iframe. Your game communicates with the LMS via a JavaScript API (&lt;code&gt;API&lt;/code&gt; object on the &lt;code&gt;window&lt;/code&gt;). You set and get data model elements using standardised keys.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key data model elements in SCORM 1.2:&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Element&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;th&gt;Example Value&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.core.lesson_status&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Completion state&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;completed&lt;/code&gt;, &lt;code&gt;incomplete&lt;/code&gt;, &lt;code&gt;passed&lt;/code&gt;, &lt;code&gt;failed&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.core.score.raw&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Numeric score&lt;/td&gt;
&lt;td&gt;&lt;code&gt;85&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.core.score.min&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Minimum possible score&lt;/td&gt;
&lt;td&gt;&lt;code&gt;0&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.core.score.max&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Maximum possible score&lt;/td&gt;
&lt;td&gt;&lt;code&gt;100&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.core.lesson_location&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Bookmark / resume point&lt;/td&gt;
&lt;td&gt;&lt;code&gt;level-3-question-7&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.suspend_data&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Free-form string for game state&lt;/td&gt;
&lt;td&gt;JSON string (4096 char limit)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;cmi.core.session_time&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Time spent in session&lt;/td&gt;
&lt;td&gt;&lt;code&gt;00:15:32&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Strengths of SCORM 1.2:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Broad LMS support&lt;/strong&gt; - SCORM 1.2 remains a common compatibility target across established LMS products&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Simple to implement&lt;/strong&gt; - the API surface is small. A basic integration can be built in a few days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Proven and stable&lt;/strong&gt; - the standard has not changed in over two decades. It will not break.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No backend required&lt;/strong&gt; - communication happens entirely client-side between the game and the LMS&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Limitations of SCORM 1.2:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;4096-character limit on &lt;code&gt;suspend_data&lt;/code&gt;&lt;/strong&gt; - this is the biggest practical constraint for games. A complex game with significant state (inventory, progress across multiple mini-games, per-question analytics) will quickly exceed this limit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single score model&lt;/strong&gt; - SCORM 1.2 supports one score per content object. If your game has multiple assessments, you must either aggregate them or package each assessment as a separate SCO (Sharable Content Object).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No detailed interaction tracking&lt;/strong&gt; - there is no standard way to report individual question responses, time per question, or attempt history.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;iframe dependency&lt;/strong&gt; - the game must run inside the LMS iframe. This introduces CSP (Content Security Policy) constraints, cross-origin issues, and limits your ability to use fullscreen or certain browser APIs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  SCORM 2004 (Editions 1-4)
&lt;/h3&gt;

&lt;p&gt;SCORM 2004 addresses many of SCORM 1.2's limitations with a richer data model and a sequencing engine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key improvements over 1.2:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;cmi.interactions&lt;/code&gt;&lt;/strong&gt; - a structured array for recording individual question-level data: question type, correct response, learner response, latency, and result. This is invaluable for educational games with assessment components.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Larger &lt;code&gt;suspend_data&lt;/code&gt;&lt;/strong&gt; - the 4096-character limit is increased to 64,000 characters in most SCORM 2004 implementations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multiple objectives&lt;/strong&gt; - track progress against multiple learning objectives within a single content object, each with its own score and completion status.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sequencing and navigation&lt;/strong&gt; - define prerequisite relationships between content objects. The LMS can enforce that Level 1 must be completed before Level 2 unlocks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Limitations of SCORM 2004:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Less universal LMS support&lt;/strong&gt; - while major platforms support it, some older or specialised LMS installations only support SCORM 1.2.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;More complex to implement&lt;/strong&gt; - the sequencing engine is powerful but adds implementation complexity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Still iframe-dependent&lt;/strong&gt; - the same hosting constraints apply.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Overkill for simple games&lt;/strong&gt; - if you only need a completion flag and a score, SCORM 2004's additional capabilities add complexity without proportional value.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; If the target LMS is already known, test against that platform first rather than choosing a standard in the abstract. SCORM 1.2 is a strong compatibility option for simple completion/score reporting; richer tracking may justify SCORM 2004, xAPI, or a custom integration.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  xAPI (Tin Can API): The Modern Alternative
&lt;/h2&gt;

&lt;p&gt;Before discussing custom APIs, it is worth mentioning xAPI (also known as Tin Can API), which sits between SCORM and a fully custom approach.&lt;/p&gt;

&lt;p&gt;xAPI uses a "statement" model: &lt;code&gt;Actor&lt;/code&gt; + &lt;code&gt;Verb&lt;/code&gt; + &lt;code&gt;Object&lt;/code&gt;. For example: "Student 42 completed Level 3 with score 92%." These statements are sent to a Learning Record Store (LRS) via HTTP.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Strengths:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rich, flexible statement model without SCORM's small suspend-data constraint&lt;/li&gt;
&lt;li&gt;Works outside the browser (mobile apps, VR, offline with deferred sync)&lt;/li&gt;
&lt;li&gt;Excellent for analytics and learning data research&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Limitations:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Requires an LRS (not all LMS platforms include one natively; Moodle requires a plugin)&lt;/li&gt;
&lt;li&gt;More complex client-side implementation than SCORM&lt;/li&gt;
&lt;li&gt;Less institutional familiarity - IT teams at schools and universities are often less comfortable with xAPI than SCORM&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;xAPI is a strong choice when you need detailed learning analytics and your client's infrastructure supports it. In our experience, many institutional briefs still ask for SCORM because it is familiar to procurement and L&amp;amp;D teams, even when a richer integration would be technically possible.&lt;/p&gt;




&lt;h2&gt;
  
  
  Custom API: The Flexible Alternative
&lt;/h2&gt;

&lt;p&gt;A custom API approach means building your own backend service that sits between the game and the LMS. The game communicates with your API via standard HTTP REST calls, and your API translates the data into whatever format the LMS expects.&lt;/p&gt;

&lt;h3&gt;
  
  
  Architecture Overview
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Game Client] &amp;lt;--REST/WebSocket--&amp;gt; [Your Backend API]
                                          |
                                   [Your Database]
                                          |
                              [LMS Integration Layer]
                                    /     |     \
                              [Moodle] [Canvas] [Blackboard]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  What Your Backend Handles
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Authentication&lt;/strong&gt; - the LMS passes a token or session identifier when launching the game. Your backend validates it and associates the session with the correct student and assignment.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Data storage&lt;/strong&gt; - all game telemetry (progress, scores, interaction logs, time-on-task, attempts) is stored in your database. No character limits. No schema constraints.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Score and completion reporting&lt;/strong&gt; - your backend pushes aggregated results back to the LMS gradebook via the LMS's API (Moodle Web Services API, Canvas REST API, Blackboard REST API).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Analytics dashboard&lt;/strong&gt; - because you own the data, you can build teacher-facing dashboards that provide richer insights than the LMS's built-in reporting. When we worked on educational projects, the ability to show educators which specific concepts students were struggling with - not just a percentage score - was consistently cited as the most valuable feature.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Resume and state management&lt;/strong&gt; - game state is stored server-side with no size constraints. The game can resume exactly where the student left off, regardless of device or browser.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Strengths of a Custom API
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No data limits&lt;/strong&gt; - store as much telemetry as you need. Per-question timing, hint usage, retry counts, learning path analytics.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Platform independence&lt;/strong&gt; - the game communicates with your API, not the LMS directly. Adding support for a new LMS means adding a new integration adapter, not rewriting the game.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native mobile support&lt;/strong&gt; - Unity games deployed as native iOS/Android apps cannot use SCORM (which requires a browser runtime). A custom API works identically for web, mobile, and desktop builds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Richer analytics&lt;/strong&gt; - build teacher dashboards, export data for research, generate per-student reports that go far beyond a single score.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real-time data&lt;/strong&gt; - WebSocket connections allow the teacher to see student progress in real-time during a classroom session.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Limitations of a Custom API
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You build and maintain the backend&lt;/strong&gt; - this is additional engineering cost, infrastructure cost, and ongoing maintenance. SCORM is essentially "free" at the integration layer because the LMS provides the backend.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-LMS integration work&lt;/strong&gt; - every LMS has a different API. Moodle's Web Services API is different from Canvas's REST API. Each integration must be built and maintained separately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Procurement friction&lt;/strong&gt; - educational institutions have established procurement processes for SCORM content. A custom integration requires IT involvement, security reviews, and potentially custom hosting arrangements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data privacy compliance&lt;/strong&gt; - you are now a data processor handling student data. GDPR (and GDPR-K for children), COPPA (US), and FERPA (US education) all apply. Your backend must be compliant.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Decision Framework: Which Approach Should You Use?
&lt;/h2&gt;

&lt;p&gt;The choice between SCORM and a custom API depends on answering four questions:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. What platforms will the game run on?
&lt;/h3&gt;

&lt;p&gt;If the game runs only in a web browser and is launched from the LMS, SCORM is the path of least resistance. If the game runs as a native mobile app (iOS/Android) or a desktop application, you need a custom API because SCORM's JavaScript API is browser-only.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. How complex is the data you need to track?
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Data Complexity&lt;/th&gt;
&lt;th&gt;Recommended Approach&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Completion flag + single score&lt;/td&gt;
&lt;td&gt;SCORM 1.2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Completion + score + 5-10 interaction records&lt;/td&gt;
&lt;td&gt;SCORM 2004&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Detailed per-question analytics, time-on-task, learning paths&lt;/td&gt;
&lt;td&gt;Custom API or xAPI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Real-time teacher dashboard, adaptive difficulty&lt;/td&gt;
&lt;td&gt;Custom API&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  3. How many LMS platforms must you support?
&lt;/h3&gt;

&lt;p&gt;If your client uses a single, known LMS, a custom integration is manageable. If your product must work with any LMS the customer happens to use, SCORM's universality is a significant advantage.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. What is your maintenance budget?
&lt;/h3&gt;

&lt;p&gt;SCORM is a fire-and-forget standard. Once your SCORM wrapper works, it works everywhere, indefinitely. A custom API requires hosting, monitoring, security updates, and per-LMS compatibility maintenance. This is an ongoing cost.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key Takeaway:&lt;/strong&gt; Use SCORM when universality and low maintenance are priorities. Use a custom API when data richness, mobile deployment, or real-time analytics are requirements. In many projects, the best answer is both - SCORM for basic LMS compliance, plus a custom backend for analytics.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Integration Approach Comparison
&lt;/h2&gt;

&lt;p&gt;Here is how the three main LMS integration approaches compare across the factors that matter most:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Factor&lt;/th&gt;
&lt;th&gt;SCORM&lt;/th&gt;
&lt;th&gt;xAPI&lt;/th&gt;
&lt;th&gt;Custom API&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;LMS compatibility&lt;/td&gt;
&lt;td&gt;✅ Universal (1.2 supported everywhere)&lt;/td&gt;
&lt;td&gt;⚠️ Requires LRS (not always native)&lt;/td&gt;
&lt;td&gt;❌ Per-LMS integration required&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Granular tracking&lt;/td&gt;
&lt;td&gt;❌ Limited (single score, 4K suspend_data)&lt;/td&gt;
&lt;td&gt;✅ Rich statement model, no limits&lt;/td&gt;
&lt;td&gt;✅ Unlimited, schema-free&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Offline support&lt;/td&gt;
&lt;td&gt;❌ Browser-only, no offline&lt;/td&gt;
&lt;td&gt;✅ Deferred sync supported&lt;/td&gt;
&lt;td&gt;✅ Local queuing with batch upload&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Implementation effort&lt;/td&gt;
&lt;td&gt;🟢 Low (days for basic integration)&lt;/td&gt;
&lt;td&gt;⚠️ Medium (LRS setup + statements)&lt;/td&gt;
&lt;td&gt;🔴 High (backend + per-LMS adapters)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Standards compliance&lt;/td&gt;
&lt;td&gt;✅ Widely recognised for procurement&lt;/td&gt;
&lt;td&gt;✅ IEEE standard (9274.1.1)&lt;/td&gt;
&lt;td&gt;❌ No standard, custom documentation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Real-time data&lt;/td&gt;
&lt;td&gt;❌ No live data flow&lt;/td&gt;
&lt;td&gt;⚠️ Near-real-time via LRS&lt;/td&gt;
&lt;td&gt;✅ WebSocket for live dashboards&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The Hybrid Approach
&lt;/h2&gt;

&lt;p&gt;In practice, we often recommend a hybrid architecture that provides the best of both worlds:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Package the game as a SCORM object&lt;/strong&gt; for LMS compatibility (completion, basic score, resume via &lt;code&gt;suspend_data&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Simultaneously send detailed telemetry to your own backend&lt;/strong&gt; for analytics, teacher dashboards, and research data.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The SCORM layer ensures the game "just works" in any LMS. The custom backend provides the rich data that SCORM cannot capture. The game client simply fires data to both endpoints.&lt;/p&gt;

&lt;p&gt;This hybrid pattern is often worth considering in &lt;a href="https://oceanviewgames.co.uk/services/educationalgames" rel="noopener noreferrer"&gt;educational game development&lt;/a&gt;: use the LMS-facing standard for launch, completion, and core reporting, while a separate backend captures the richer telemetry needed for dashboards or research. Whether that is appropriate depends on the client's data-governance and procurement requirements.&lt;/p&gt;




&lt;h2&gt;
  
  
  Implementation Tips for Unity Developers
&lt;/h2&gt;

&lt;h3&gt;
  
  
  SCORM from a Unity WebGL Build
&lt;/h3&gt;

&lt;p&gt;Unity WebGL builds run inside a canvas element, which the LMS wraps in an iframe. To communicate with the SCORM API:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create a JavaScript plugin (&lt;code&gt;.jslib&lt;/code&gt; file) that accesses the SCORM API on the parent window.&lt;/li&gt;
&lt;li&gt;Call the JavaScript functions from C# using Unity's &lt;code&gt;[DllImport("__Internal")]&lt;/code&gt; interop.&lt;/li&gt;
&lt;li&gt;Wrap the SCORM calls in a C# class that implements a common interface (so you can swap to a custom API for non-SCORM deployments).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Key gotchas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cross-origin issues&lt;/strong&gt; - ensure the Unity build is served from the same origin as the LMS, or configure CORS headers appropriately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WebGL memory&lt;/strong&gt; - educational institutions often use low-spec devices (Chromebooks). Keep your WebGL build's memory allocation conservative.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fullscreen&lt;/strong&gt; - SCORM iframes may prevent fullscreen API access. Design your game's UI to work within a constrained viewport.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Custom API from a Unity Native Build
&lt;/h3&gt;

&lt;p&gt;For iOS and Android deployments:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Use &lt;code&gt;UnityWebRequest&lt;/code&gt; for HTTP communication with your backend.&lt;/li&gt;
&lt;li&gt;Implement local queuing for offline resilience - educational environments often have unreliable Wi-Fi.&lt;/li&gt;
&lt;li&gt;Authenticate via OAuth 2.0 or a signed JWT token passed from the LMS at launch.&lt;/li&gt;
&lt;li&gt;Batch telemetry events and send them periodically (every 30-60 seconds) rather than on every interaction, to reduce network overhead.&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Compliance and Privacy
&lt;/h2&gt;

&lt;p&gt;Educational game developers handling student data must navigate several regulatory frameworks:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GDPR (EU/UK)&lt;/strong&gt; - requires a lawful basis for processing, data minimisation, right to erasure, and a Data Processing Agreement between you and the institution.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GDPR-K / Age-Appropriate Design Code (UK)&lt;/strong&gt; - additional protections for children's data, including restrictions on profiling and data sharing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;COPPA (US)&lt;/strong&gt; - requires verifiable parental consent for children under 13. Applies to any game used in US schools.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FERPA (US)&lt;/strong&gt; - protects student education records. Your backend becomes a "school official" if it accesses student data on behalf of the institution.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Privacy compliance is not optional and should be designed into the architecture from day one&lt;/strong&gt;, not bolted on before launch. We factor compliance requirements into the initial architecture design for every educational project.&lt;/p&gt;




&lt;h2&gt;
  
  
  Choosing the Right Path
&lt;/h2&gt;

&lt;p&gt;To summarise, here is our recommended decision path:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Browser-only, single LMS, simple tracking&lt;/strong&gt; --&amp;gt; SCORM 1.2&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Browser-only, multiple objectives, detailed interactions&lt;/strong&gt; --&amp;gt; SCORM 2004&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native mobile app, any platform&lt;/strong&gt; --&amp;gt; Custom API (SCORM is not available)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Complex analytics, teacher dashboards, research&lt;/strong&gt; --&amp;gt; Custom API or xAPI&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Universal LMS compatibility + rich analytics&lt;/strong&gt; --&amp;gt; Hybrid (SCORM + Custom API)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Future-proofing for modern infrastructure&lt;/strong&gt; --&amp;gt; xAPI with LRS&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The worst outcome is choosing an approach that does not meet your requirements and having to re-engineer mid-project. Invest the time upfront to understand your client's LMS landscape, data needs, and deployment platforms.&lt;/p&gt;




&lt;h2&gt;
  
  
  Related Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/services/educationalgames" rel="noopener noreferrer"&gt;Educational Game Development Services&lt;/a&gt; - How we build games that teach&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/education" rel="noopener noreferrer"&gt;Education Industry&lt;/a&gt; - Our work across the education sector&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/industries/corporate-training" rel="noopener noreferrer"&gt;Corporate Training Industry&lt;/a&gt; - Gamified training and L&amp;amp;D solutions&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://oceanviewgames.co.uk/blog/posts/gamifying-language-learning-edtech" rel="noopener noreferrer"&gt;Gamifying Language Learning: Lessons from EdTech Development&lt;/a&gt; - Our approach to turning curriculum into gameplay&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gamedev</category>
      <category>unity3d</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
