Articles about UX - Nasty Rodent - Page 2

Question 1

What is the main difference between UI/UX co-development and outsourcing for games?

Accepted Answer

Co-development embeds an external UI/UX team inside your production pipeline — they participate in sprint cycles, shared design decisions, and ongoing feature work as a functional extension of your studio. Outsourcing delivers defined work against a completed brief, with your studio reviewing at milestone checkpoints. The key test: if your UI brief is stable and complete before production starts, outsourcing works. If the interface must evolve alongside gameplay systems that aren't fully defined yet, co-development is the correct model.

Question 2

Which model costs less — outsourcing or co-development?

Accepted Answer

Outsourcing has a lower entry cost per deliverable. Co-development carries a higher continuous cost through retainer or dedicated team pricing. The total cost comparison depends on scope stability. When scope drifts significantly — as it often does in live-service and evolving productions — full outsourcing can exceed co-development cost in rework cycles. The rate card is the wrong metric; total production cost including revision overhead is the correct one.

Question 3

Can we start with outsourcing and switch to co-development later?

Accepted Answer

Technically yes, operationally expensive. Onboarding a co-development partner mid-production means they spend three to six weeks building the production context your internal team already holds. The later the switch, the higher that catch-up cost. If co-development is likely to be the correct long-term model, entering it before full production locks is significantly more efficient than correcting the model mismatch at milestone 3.

Question 4

Who owns the IP and deliverables in both models?

Accepted Answer

In both models, full IP ownership transfers to you as the client upon milestone acceptance. Work-for-hire clauses and IP assignment language should be explicit in the MSA before production begins. For co-development agreements, the IP clause should cover not only final assets but intermediate design documents, wireframes, and UX specifications produced during the engagement. Confirm this explicitly — don't assume it defaults to you.

Question 5

How do we ensure UI/UX quality when outsourcing to an external studio?

Accepted Answer

Three structural requirements make the difference: a technically specific brief (target resolution, engine constraints, localization requirements, performance budgets for draw calls), a paid pilot project before full commitment, and a defined first-pass approval rate benchmark in your vendor scorecard. A studio with a tracked first-pass approval rate above 70% has a QA process. A studio that describes quality verbally without measurement is running on intention, not process.

Question 6

What does the vendor onboarding process look like for a co-development engagement?

Accepted Answer

A structured co-development onboarding runs four to eight weeks. Week one and two: pipeline orientation, tooling alignment, access provisioning, and a sprint observation period. Week three and four: the partner takes on defined feature work with close review. By week five, the team is operating inside your sprint cycle with standard accountability. Studios that skip the calibration phase — treating co-development partners as immediately autonomous from day one — consistently report higher friction through the first quarter. The onboarding investment is the mechanism that makes the integration model work.

Blog - Page 2

UI/UX Co-Development vs Outsourcing for Game Production: How to Choose the Right Model

How to Choose a Game UX/UI Design Studio: 5 Technical Checks Before Signing

Diegetic and Non-Diegetic UI in Games: Design Principles and Use Cases