21 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You’ll split time between design work, coding, and coordination. Morning might be writing or updating design documents and level specs (XML or plain text).
Afternoons often mean prototyping in C# or JavaScript, tweaking UI/UX, playtesting builds, and logging bugs or tasks in Atlassian JIRA. Evenings can be art checks with Photoshop/Illustrator files, polishing audio direction, or iterating after feedback.
Expect version control like Git, a code language such as C# (Unity) or JavaScript/HTML for web games, and XML for data or config files. Use Adobe Photoshop and Illustrator inside Adobe Creative Cloud for sprites, UI, and icons.
Project work and bug tracking happen in Atlassian JIRA. Design documents and specs are plain text or structured XML. You’ll also prototype levels and interactions in the engine editor (e.g., Unity) and iterate from playtests.
Use AI to generate quick drafts: story beats, item names, dialogue variants, or mock UI text. Treat these as starting points, then edit heavily to match your vision and voice.
Don’t paste proprietary code, internal art, or private game logic into public AI tools. Keep licensed assets and unique mechanics in your repos (Git) and document changes in JIRA to keep ownership and traceability.
According to the U.S. Bureau of Labor Statistics (BLS), 113,330 people were employed in this role. The median annual wage is $104,000; the lowest tenth is $53,750 and the top tenth is $201,550.
Indie roles vary a lot: small teams may pay below the median, while experienced leads or successful studio owners can reach the top tenth.
Start by learning one engine and one language—like Unity with C# or web games using HTML, JavaScript, and CSS. Build small prototypes that focus on a single mechanic and iterate.
Practice writing simple design documents and level layouts, store code in Git, and track tasks in JIRA (you can simulate JIRA with free tools). Learn basic Photoshop/Illustrator for UI and art tweaks.
Indie developers often wear many hats: design, prototype, UI, some coding, and collaborate closely with artists. You write specs, handle level layouts, and guide production staff directly.
At big studios roles are narrower—separate designers, systems designers, UI people, and producers. Indies need broader skills (C#, JavaScript, Git, Photoshop, JIRA) and more direct responsibility for the final vision.
The ability to prototype quickly and iterate from playtests. That means turning a rough idea into a working gameplay prototype in C# or JavaScript, running playtests, then balancing mechanics and levels.
Couple that with clear, maintainable design documentation (specs, XML for data) and disciplined version control (Git). Rapid, repeatable iteration plus clear docs wins games.