Indie Check List
Did you think about [ ... ]
Last updated
Did you think about [ ... ]
Last updated
Consider supporting us as a GitHub Sponsor and get instant access to all our Unity assets, exclusive tools and assets, escalated support and issue tracking and our gratitude. These articles are made possible by our GitHub Sponsors ... become a sponsor today!
The following are major areas that you should seriously think of how you will staff. These are the major functions that you will need to staff internally, contract someone to do for you, or select a partner to help you with.
Read over every entry here, but don't panic yet.
There are indie-friendly ways to account for every aspect of this journey, it's not free, it's not easy but it is worth it if this is your passion.
In many regions, you are legally required to register a business, even if it's just you. In most cases, it's strongly advised that you incorporate and not simply "DBA" (doing business as). The specifics of this are highly dependent on region, deal with legal matters and are not appropriately advised on via a community forum or even this article.
Go see a professional that deals with Company Formation in your region and understand what your obligations are, and seek advice on what options might best work for you. Finding a local advisor or partner to help you here is key. Most regions will have state/government ran programs and initiatives meant to support new businesses, this is particularly common with new arts, technical and consequently game businesses.
If you're going to be buying anything or making any money then you need an accountant. You will always need an accountant so rather you staff this or partner, this will be a permanent relationship for you and your company. It's worth noting that many accounting firms also handle company registration and can advise on administration aspects. This is also highly specific to each region and deals with legal matters so taking the advice of some community forum or even this article is insufficient. Seek a local professional for advice.
As a game developer, even before you have a game ready to publish, you will be creating and using other people's creations. Making sure you're complying with any legal requirements and registering any IP, names, marks, etc. as required by your local regulations is critical and often overlooked. This is usually something that your Registration and Administration and/or Accounting partner may handle; that is you can usually find a partner that is suitable to advise and guide on all three of these aspects.
We strongly recommend Steam as your first and core platform. Steam is the gaming platform for PC, it has a low barrier to entry and you build your game on a PC so it's the most native to the project ... there is no reason to not launch on Steam.
How will you distribute your product? This is something you should think about early. It will dictate many other aspects of your organization and likely have a significant impact on the design and implementation of any apps/games you create.
You will need to choose a trusted platform or multiple platforms. While it is technically possible to distribute your games and apps yourself, platforms do much more than just distribution. A key aspect of choosing a platform is the "Trust and Security" aspect. Why should a customer trust your app? How do they know it's not malware? Simple, if it's on a trusted platform it's "safe" or at least there is recourse if things go sideways.
For "PC" games (that is Windows, Mac and Linux games) the Steam platform is the largest and most dominant by a very long shot. If you plan to release a game on PC then you should plan to release that game on Steam. Steamworks is a feature available freely to all Steam games and can add a lot of value to your game for your players. Heathen of course provides great tooling around Steamworks.
Do be careful of the platforms you choose, especially if you're considering exclusivity.
Our biased opinion is that you should treat Steam as your primary platform and then add additional platforms to your supported list as your bandwidth (skill and resource availability) allows. This recommendation applies to console games and "major" mobile games as well. PC is the most "native" platform to any bit of software and Steam is king on PC. There is little to no reason to not release on Steam and in general, your Steam release should be the easiest to accomplish.
Small studios can often land some much-needed funding via exclusive deals, however, some platforms especially when you are available exclusively on them can be harmful to your project and organization. In general PC gamers have an active hate of "exclusivity" to the point that some do track this behaviour and actively avoid developers and publishers that avail of it.
Another commonly outsourced aspect of game development as a business, especially for small studios and solo developers. Marketing requires time, expertise and scale to be effective. The marketing needs of small indies are unique to the needs of other businesses and even other forms of game development (mobile, AA and AAA). Be sure to consider the unique challenges of marketing and understand that developing your marketing strategy should generally happen before the production of your game.
Marketing for note involves much more than advertising your game. Your marketing strategy will include an assessment of the market, audience targeting and other factors that will influence your design process and in particular will influence any potential investors. Engaging a professional marketing firm early to help establish a sound marketing strategy doesn't cost as much as you might think and will greatly improve your chances of success.
Community is an ever-evolving requirement of game development. In the early days, games were a matter of "fire and forget", released into the wild and not so much as a post-release update. One-way community management via "Blue Posts" ... looking at you Blizzard ... are likewise no longer viable. The current market effectively demands rich community engagement. A happy community can prop up a small scrappy game and a pissed-off community can tank a AAA title with ease.
Classically community management has been handled by a "go-to-man" in each studio acting as a sort of "frontman" like one sees with rock bands ... and that is a major problem.
Good business will tell you that having any system depend on a "go-to-man" is a critical point of failure that will go wrong, it's only a matter of time. Treat the community and its management as you would any other important part of your business, and project and invest in it wisely.
These are the major aspects of production that you simply cannot get away with cutting corners on.
As "indie game dev" has grown in popularity, some tools, guides and articles might have led you to believe that you can just buy the solution on the Unity Asset Store or DIY with some magical tool that trivializes it.
This however is not reality. In reality, each of these areas is skilled creative functions that involve more work than the uninitiated realizes, and so require consideration on how you will source these needs.
Seems obvious right? This is usually the one common thing we all (game developers) do or are interested in. That however doesn't mean we are all game designers and that we have a passion for it as our core skill. If you're not the game designer, you need to source for this fundamental requirement. Staffing up is usually the preference here but it is possible to contract or even outsource your game design.
Keep in mind having a "great idea" is not game design, game design is devising all those little hidden and often obscure factors that work together to create an experience that the user wants to pay you money for. This is often held up as the "rock star" role in a studio but in reality, its the most thankless and difficult job usually done by a team of dedicated people who most people don't even realize exist.
It just so happens that a couple of influential people in the industry at current are people who started as designers, they however are no longer designers they are now executives (full-time job), managers (full-time job), or otherwise not dealing with the day to day design of given areas of the project.
No, you cannot create a professional fully featured game without dealing with engineering. I don't care what XXXX tool says on the box, that is not reality.
Engineering is not typing words into a compiler to "make the computer go". 'The act of analyzing requirements, designing, building, testing and integrating tools and systems to resolve those requirements.' That is engineering. Or at least the main part of it you need an engineer for.
Visual scripting tools, blueprints, "code free" development tools ... they can all help your prototype. However, they are not a replacement for an engineer. Even if your project never requires a single line of code to be typed out, you will still require engineering as a skill to complete your project.
If you want to release a professional game you cannot be releasing it with Unity Asset Store artwork in it. Art assets on the Unity Asset Store and similar marketplaces are wonderful placeholders, inspiration pieces or even as a base or bash kit to work from when creating custom works. UAS Art Assets however are not production-ready regardless of what is said on the store page. You might get away with it as a passion project done by a hobbyist but the moment you put that professional hat on and try to be a business, your clients and probably some of your peers are going to rip you apart.
Visuals (usually just called art but audio guys get offended 😉)
Rather it's for your UI, world design, characters, VFX ... just like Engineering is more than "type words make the computer go", visual art is a lot more than 2D images and 3D models. Sourcing a solution to create your visual design style and then producing the content in that style to meet your project's requirements is an obvious requirement for any game project.
As with visual assets, grabbing some royalty-free SFX and music off some asset store, while perfectly fine for that passion project you did as a hobby, just isn't appropriate for a professional game.
Audio assets tend to be even harder to hide or mask in your project, even infrequently played sounds tend to be very memorable to players. Couple that with the comparatively smaller pool of assets to choose from, the risk of using off-the-shelf audio assets is high.
Beyond the fact that a solid portion of your user base is likely to identify your off-the-shelf audio selection. Audio design and direction is an art unto itself that has less to do with the recording of noise you purchased and more to do with how they are used. A well-thought-out audio design for your game can not only save some egg on the face but also reduce the cost and need for custom audio. Proper use of less will get you more than throwing a lot of off-the-shelf content at the problem.
No, community testing and public beta are not even close to sufficient.
This is one of the factors that separates the hobbyist game from the professional game. Nothing wrong with being the passion project of a talented hobbyist, but a professional game is held to a stricter standard.
If you outsourced your engineering that firm probably also provides for testing. If you're handling engineering needs in-house, then you're going to need to solve for testing as well. Testing is one of those areas that only works at scale. That is to say, it requires a larger entity to do well. Consequently, small studios, even ones specialized in engineering, will outsource some or all of their testing. Even "testing studios" who are the ones often contracted to be that outsourced testing solution are typically leaning very heavily on contractors to meet the demand.
Do not auto-translate
As with every other aspect of production, you cannot cut corners here. You are far better to support just 1 common language than you are to auto-translate your game in the modern market. Aside from a lack of professionalism, some regions and cultures can be easily offended by naïve attempts and in some cases that offence can bring real consequences.
Localization is perhaps the most commonly outsourced requirement a game will have, as it requires local cultural expertise for each location. Localization more so than other aspects simply shouldn't be corner-cut. Poor translation can be offensive and result in harm to your product and company. It simply isn't excusable in the modern market. If your budget is tight and you can't afford a professional localization of your project, simply skip it. You are better off having fewer localizations than you are letting auto-translate shoot you in the foot.
So much more than keeping the lights on, but often thought of that way. Operations cover the factors of, well, operating whatever it is.
DevOps, sometimes confused for ALM or even simply called "source control", encompasses a lot of your day-to-day operations as a software development house.
Make no mistake, if you build video games, whether you like it or not you are a software development business, and need to be aware of and conform to that reality.
DevOps is largely an internal process with some tooling sprinkled in, so not something you will be outsourcing unless you outsource all of your development. DevOps is however a concept you're likely new to, not to mention its parent concept ALM. Finding a consultancy that can help you ramp up these concepts and tools is key to the healthy operation of your business. No amount of good ideas or even great production will save you if you fail at DevOps.
DevOps is a collection of practices, and the tooling to support them. It defines and enables the creation of your "content" be that source code, art assets, audio files or anything else for that matter. It defines how they will be logged, backed up, reviewed, tested, built and deployed.
In short, it defines how you will "operate" your "development", hence DevOps.
No this is not just for your code monkeys, it covers all of your "dev" so art, audio, testing, and design. The entire "production" process as we would typically call it in game development is driven through your DevOps tools according to your DevOps processes.
LiveOps or "Live" "Operations" deals with the processes and tools you employ to operate your released game. What exactly this includes depends on your game and truly standalone games have a very minimal "LiveOps" requirement whereas something more "live service" such as an MMO or MOBA would have a very complex "LiveOps" requirement.
As with DevOps, this is a matter of processes and the tools that enable them so not something you would "outsource" though consultancy firms can help you understand the concepts and apply them to your specific project.
