Freelance, studio, or asset store: who should design your game's UI?

The three options at a glance

The row that decides most projects is the third one. A kit is a set of components; it contains no opinion about your game, because it was made before your game existed. Everything a kit cannot do follows from that.

Asset store kits: what you actually get

You get components. Buttons, panels, sliders, tabs, icons, sometimes a demo scene wiring them together. On a good kit these are internally consistent, which solves a real set of problems: mixed corner radii, missing states, inconsistent spacing. Those are three of the eight causes in why your game UI looks amateur, solved for the price of a lunch.

What you do not get: a flow, a hierarchy, an answer for your specific systems, or any relationship to your art direction. A kit cannot tell you that your inventory has one screen too many, because it has never seen your inventory.

When a kit is genuinely the right answer

This is not a consolation prize. In these cases a kit is the correct professional decision and spending more would be waste.

• Prototypes and playtest builds. You are testing whether the game is fun, and interface polish is noise in that signal.
• Jam games and demos with no commercial life.
• Games with genuinely tiny interfaces. Two menus and a pause screen does not need a designer.
• Internal and debug tools. Nobody is being sold anything.
• When the budget is genuinely zero. A consistent kit plus the free pass in indie game UI on a budget beats an inconsistent original every time.

Freelance: what you are really buying

You are buying a specific person's judgement applied to your specific game, without overhead. The rate is lower than a studio's because there is no producer, no account manager and no office in the number.

• You talk to the person doing the work. No brief passing through two people before it reaches a designer.
• Decisions happen in one conversation rather than in a change-request process.
• The scope can be a slice. Four screens, a HUD, a review. Studios rarely want engagements that small.
• You can start in a week or two, not after a procurement cycle.

When a freelancer is the wrong call

Worth saying plainly, because the honest cases are easy to spot.

1. The volume genuinely exceeds one person. Eighty screens on a hard deadline is not a freelance job, it is a team.
2. You need guaranteed cover. One person gets ill and takes holidays. If a two-week absence would sink your milestone, buy redundancy.
3. You have no one to direct the work. A freelancer needs a decision maker. A studio can supply direction as part of the service; that is a real part of what the multiple pays for.
4. Procurement requires a company, insurance, or a legal structure a sole trader cannot provide.
5. The work is continuous for more than a year. At that point an in-house hire is usually cheaper per screen.

Studios and agencies: when the multiple is worth it

Two to four times the hourly rate buys things that are invisible on a quote and very visible when a project is large.

• Capacity. Several designers on parallel workstreams, coordinated by someone whose job that is.
• Continuity. Illness, holidays and departures do not stop the project.
• Art direction as a service. Someone senior holding quality across everyone's work.
• Process. Documented handoff, QA, version control, a producer chasing your feedback so you do not have to chase theirs.

For a large team with a publisher, a hard date and eighty screens, that is worth paying for. For a six-person indie with twenty screens, most of it is overhead on something a freelancer would do faster.

Same project, three ways

A worked example: an indie title, roughly 20 screens plus a HUD, one platform, needed in ten weeks.

That last row is the one most indie teams should look at hardest, and it is the one almost nobody asks about.

What happens when it goes wrong

Compare the failure modes, not just the prices. This is where the real difference in risk sits.

The freelance risk is mitigated almost entirely by structure: fixed milestones, payment per milestone, and source files delivered as you go. Insist on those and the worst case becomes a delay rather than a loss.

The honest recommendation, by project size

1. 01

   Under 10 screens, or pre-launch prototype

   Kit plus the free pass. Spend the money on the game instead. If one screen carries your hook, commission that single screen.

2. 02

   10 to 30 screens, commercial release

   Freelancer, or the hybrid. This is the band where a designer changes the commercial outcome most per dollar, and where a studio's overhead buys you the least.

3. 03

   30 to 60 screens, or two platforms

   An experienced freelancer on a retainer, or a small studio. The deciding factor is whether you have someone in-house able to direct the work.

4. 04

   60+ screens, hard deadline, publisher

   Studio, or a team. One person cannot absorb that volume without becoming the bottleneck, and no rate makes that a good trade.

The hybrid most teams should run

The answer is rarely one of the three. The version that gets the most out of a small budget looks like this:

1. Buy a kit for components, and restyle its typeface, radius and palette so it stops being recognisable.
2. Commission the flow and the four screens that decide your game's first impression: the main menu, the HUD, your signature system screen, and settings.
3. Take the component set the designer produces and apply it yourself to everything secondary.
4. Buy one review at the end, once your own screens are in, to catch what you cannot see any more.

That lands most indie projects between $3,000 and $4,500, which is a fraction of the full-service number and considerably better than the kit-only outcome. The priority order behind it is set out in indie game UI on a budget.