Unity Performance Audit & Architecture Review

A Unity code review is not a style guide enforcement exercise. My reviews focus on correctness, robustness, performance, and maintainability. The deliverable is a written report with findings categorised by severity (Critical, Major, Minor, Suggestion), each with a specific code reference, explanation of the problem, and a recommended fix.

I review C# Unity code, shader code (HLSL/ShaderGraph), editor scripts, and build pipeline scripts.

Performance problems in Unity games rarely live where developers expect them to. My performance audit process uses the Unity Profiler, Frame Debugger, Memory Profiler, and platform-specific tools (Xcode Instruments for iOS, OVR Metrics Tool for Meta Quest, RenderDoc for GPU debugging).

I measure before recommending anything, so each finding in the report is tied to a profiler capture on your target device rather than a guess about where the time goes.

Architecture consulting typically happens at two points: at the start of a project (greenfield architecture design, technology selection, pipeline planning) or mid-project when scaling problems emerge.

Topics I cover: scene and GameManager patterns, dependency injection vs service locator, ScriptableObject-based event systems, data-driven design, save system architecture, addressables and content pipeline design, and CI/CD pipeline setup.

• Discovery call (30 minutes, free): the symptoms you are seeing (frame drops, long load times, crashes, slow iteration), your target platforms and frame budget, and which parts of the project matter most.
• Written proposal within 48 hours: what will be reviewed, the deliverables, and the timeline. I sign an NDA before receiving any proprietary code or assets.
• Audit: profiling on the target hardware and reading the relevant code. On longer audits you get weekly progress updates, and anything critical is flagged as soon as I find it rather than held back for the final report.
• Report and walkthrough: you receive the written report, and we go through it together so your team understands the reasoning behind each recommendation. Implementing the fixes is optional and scoped separately.

• A written report with findings categorised as Critical, Major, Minor, or Suggestion.
• Specific references to the file, system, or profiler capture behind each finding.
• A prioritised fix list ordered by impact and effort, so you know what to tackle first with the time you have.
• Architecture recommendations with an incremental migration path, not a request to rewrite the project.
• Optional implementation of the highest-priority fixes, by me or alongside your team.

Performance and architecture work from my portfolio that shaped how I audit other projects:

• Crazy Coaster: a solo VR project targeting a stable 72 FPS on standalone Meta Quest hardware, using LOD management, GPU instancing for repeated track segments, and baked lighting to stay within the mobile GPU budget.
• A Long Journey to an Uncertain End: as a contracted lead developer with Crispy Creative, I worked on the Nintendo Switch port, including texture atlas optimisation, draw call batching, and memory management for the Switch hardware.
• GEO Master: a multi-resolution texture streaming system that keeps an interactive 3D globe within mobile memory limits across iOS, Android, PC, and Mac.

Audits use the same published rates as my other services, detailed on the hire page:

• Time and materials at $500 to $1,500 per day suits a focused review of one system, which typically takes one to two days.
• Fixed-scope projects start from $5,000 and suit a whole-project performance audit or architecture review with a defined report.
• Monthly retainers suit teams that want a recurring review cadence or regular access to a senior developer.