Five days into our official existence as Hair Fall Studios, and we've already made the leap from concept discussions to actual development. Today, we want to share our process, our early decisions, and what it's like to start building a game from absolute zero.
From Whiteboard to Workstation
Last week, our game existed only as sketches on whiteboards, late-night Discord calls, and a shared Google Doc filled with increasingly ambitious ideas. This week, we have actual code running, placeholder art appearing on screens, and the first glimmers of what might become our debut game.
The transition from "wouldn't it be cool if..." to "okay, how do we actually implement this?" has been both exciting and humbling. Turns out, making games is harder than talking about making games. Who knew?
Our Development Philosophy
Before writing a single line of code, we established some core principles that guide every decision we make:
"Build something we'd genuinely want to play, even if we weren't the ones making it."
This sounds simple, but it's surprisingly easy to lose sight of during development. Every feature, every mechanic, every UI element gets filtered through this question: Would we actually enjoy this if we encountered it in someone else's game?
Technical Decisions
Choosing our tech stack felt like the first "real" decision we had to make as a studio. After extensive research and some heated debates (ask us about the Great Engine Wars of January 2026), we settled on:
Unity 2D
While some team members advocated for building a custom engine or exploring other options, we ultimately chose Unity 2D for several practical reasons:
- Mobile-first optimization: Unity's mobile deployment pipeline is mature and well-documented
- Team familiarity: Most of our developers have Unity experience, reducing the learning curve
- Asset ecosystem: Access to a vast library of tools, plugins, and community resources
- Platform flexibility: Easy porting to multiple platforms if we decide to expand beyond mobile
The "2D" part was never really in question - our game concept is inherently 2D, and we want to focus on gameplay depth rather than visual complexity.
The Prototype Process
We're following what we're calling the "Minimum Viable Fun" approach. Instead of building out complete systems, we're creating the smallest possible version of each mechanic that can demonstrate whether it's actually enjoyable.
Current Prototype Status (Week 1)
Early Challenges
Even one week in, we've encountered some interesting challenges that we didn't anticipate:
The Perfectionism Trap
Our biggest enemy so far has been the urge to make everything perfect before moving on. We spent three days debating the "right" way to structure our player movement code when we could have had five different working prototypes to test.
Lesson learned: Ugly code that works is infinitely more valuable than beautiful code that doesn't exist yet.
Decision Paralysis
Having complete creative freedom is both a blessing and a curse. When you can build anything, how do you decide what to build first? We've had to become comfortable with making "good enough" decisions quickly rather than perfect decisions slowly.
Remote Collaboration
Coordinating seven developers across different schedules and time zones requires tools and processes we're still figuring out. We've already switched version control workflows twice and are on our third project management system.
What's Actually Fun?
The most encouraging discovery this week has been how quickly certain mechanics feel "right" when you get them working. There's a moment when placeholder rectangles moving around a screen suddenly feel like they have weight and personality - that's the moment we're chasing with every system.
We had our first "oh, this is actually fun" moment on Wednesday when our core movement system clicked into place. It's hard to describe, but you know it when you feel it - that satisfying sense of control and responsiveness that makes you want to keep playing just to experience the movement itself.
Community Feedback
We've been blown away by the response to our studio announcement. Having people excited about what we're building adds pressure, but it's the good kind - the kind that motivates you to validate their trust in what you're creating.
Several community members have already reached out with offers to help, feedback on our approach, and encouragement that means more than we can express. If you're one of those people, thank you. It makes a difference.
Looking Ahead
Next week's goals are focused on expanding our prototype from "interesting" to "playable":
- Implement the first iteration of our core game loop
- Create basic placeholder audio to support the experience
- Build the simplest possible UI that supports our mechanics
- Start user testing with friends and family (brace yourselves, folks)
Developer Insights
From Our Lead Developer
"The hardest part about indie development isn't the coding - it's maintaining momentum when no one is telling you what to do next. We're learning to be our own producers, testers, and cheerleaders."
From Our Designer
"Every design decision feels massive when you're starting out. We're learning to prototype our way out of analysis paralysis - build it, test it, iterate on it."
Want to Follow Along?
We're committed to documenting this entire journey - the successes, failures, breakthroughs, and setbacks. If you're interested in the nitty-gritty details of indie game development, consider joining our community.
Next week, we'll be sharing more details about our actual game concept (we're getting close to being ready!), some early gameplay footage, and our first user testing results.
Join Our Development Journey
Get weekly development updates and behind-the-scenes content on Instagram, plus monthly newsletters.