What we do
Tools
Industries
Department
How we workLet's talk →
Home/Unity Developer for Stalled Builds and Sims
Unity Development

Hiring a Unity Developer to Finish a Project Someone Else Started

A Unity project is more than its C# scripts. It's scenes, prefabs, an exact editor version, packages and store accounts, and a new developer needs all of them to even open it cleanly. Before you ask anyone for a timeline, make sure you have the pieces below.

Collect these before anyone quotes the rest of the build

Most Unity handovers stall on something missing from this list. Ask for each item in writing while the old developer still answers email.

  • The exact Unity editor version

    It's recorded in ProjectSettings/ProjectVersion.txt. Opening the project in a different version can quietly upgrade files, and that's hard to undo once it's saved.

  • The whole Assets folder, with every .meta file

    Each .meta file holds the ID Unity uses to link scripts, prefabs and materials. Lose them and scenes open full of "Missing" references that someone has to reconnect by hand.

  • Packages/manifest.json and every third-party plugin

    That file lists the packages the project depends on. Asset Store purchases and SDKs (ads, analytics, purchases, headset SDKs) also need to be licensed to an account your company controls.

  • Scenes and prefabs saved as text, in version control

    With Asset Serialization set to Force Text, a new developer can see what changed and when. A single zip of binary scene files makes that much harder.

  • Build settings and signing for each platform

    The Android keystore, the Apple developer account, and any console developer access. A lost Android signing key can stop you updating an app that's already live.

  • The last build that actually ran, on real hardware

    An installable build, or even a screen recording, shows what "working" meant last time and gives the next developer something to compare against.

Games, training simulations and AR/VR are different jobs in the same engine

What you are building What usually decides the schedule Check early
A mobile game Performance on older phones, store review, and the ads or purchase SDKs. Whether the SDK versions in the project still meet both stores' current rules.
A PC or console game Content volume, save systems, controller support and certification for each console. Who holds the console developer access. That's a business agreement, not a file.
A training simulation Scoring, scenario logic and getting results out to the people who track training. Where results have to land, such as a learning system or a spreadsheet someone reports from.
An AR or VR app Holding a steady frame rate on the headset, and changes in the headset maker's SDK. Testing on the actual headset every week, not only in the editor.

Stay on the Unity version it was built on, or upgrade first?

Stay

When you are close to shipping

  • The project runs, the packages are pinned, and the remaining work is features and content.
  • Upgrading now would mean retesting everything just before a deadline.
  • Plan the upgrade as its own job after release.
Upgrade

When the old version is in the way

  • A store now requires newer SDK targets than that editor version can produce, such as Google Play's target API level.
  • A package, render pipeline feature or headset SDK you need only supports newer versions.
  • The editor version no longer gets fixes for a bug that's blocking you.

Either way, upgrade on a branch, one step at a time, and rebuild for every target before merging. It's one of the first calls we make when we pick up someone else's project.

Where a Unity build that works on one platform breaks on another

These only show up on real target hardware, which is why a build that was easy to test on a desktop can still be weeks from shipping.

Bright magenta materials on mobile or headset

How you'll know: Objects look fine in the editor and turn solid magenta on the device.

Fix: A shader the target can't use. Swap it for one that supports that platform and render pipeline, then check every scene, not just the first.

Fine on PC, killed on older phones

How you'll know: The app closes without an error after a few minutes, usually on lower-memory devices.

Fix: Profile memory on the device itself. Oversized textures and assets that never unload are the usual causes.

Controls written for one kind of input

How you'll know: Mouse and keyboard work, but touch, gamepad or hand controllers behave oddly or not at all.

Fix: Put input behind one layer that each platform maps to, rather than separate code paths that drift apart.

A plugin only set up on one side

How you'll know: Purchases or ads work on Android and fail on iOS, or the other way round.

Fix: Finish that SDK's setup for the second platform. iOS builds also need a Mac with Xcode, so check who has one before launch week.

Why a Unity project is hard to hand over

Much of a Unity project's logic isn't in the scripts at all. It's in how scenes are wired, which prefabs nest inside which, and what was dragged onto each component in the Inspector, and often only the person who built it knows why. n-frames keeps more than one Unity developer able to read someone else's scenes, so the project doesn't stall a second time.

Unity is scripted in C#, so engine work often overlaps with back-end code that serves the game or simulation. For the C# side on its own, see C# developer; for apps that aren't built in an engine, see mobile app developer and full stack developer.

Let's talk

A Unity build carried through to every platform it ships on

n-frames takes Unity projects on with its own developers: games, training simulations and AR/VR apps. We open what you have, list what's missing, give you a timeline you can plan around, and test on the phones, PCs or headsets you're actually shipping to. If the project needs a web portal or a back end around it, that's part of the same custom software development work.

Map what's left of the build →

Questions people ask

Do you build games, or also training and AR/VR simulations?

Both. The Unity work that reaches us splits fairly evenly between games and non-game simulations, and the engine skills carry across. What changes is the part around it: store rules for a game, results reporting for a training simulation, frame rate on a headset.

What happens if our Unity developer disappears mid-build?

We've taken over partly built Unity projects before. Reading someone else's scenes and prefabs takes time, but it's recoverable. Gather the files in the checklist above first, and we'll tell you how long the reading-in will take before any new work starts.

Can you support multiple target platforms, not just one?

Yes. We build and test on each target platform you ship to, because a Unity build that passes on one often doesn't on another.

Should we upgrade the Unity version before you continue?

Only if the old version blocks you, for example a store's newer SDK requirement or a package you need. Close to a deadline, we usually finish on the current version and upgrade afterwards on a separate branch.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.