Game Development 101: What We Learned Building the Banana Game

Building Banana has been a wild ride. Behind the memes, bananas, and... more bananas, is a small team learning a lot about game development, community management, and what happens when a simple idea turns into something much bigger.

In this post, each of us from the Banana dev team is sharing one key thing we learned along the way. Whether you're a fellow indie dev, a curious player, or someone watching from the sidelines, we hope these insights give you a peek behind the curtain.

Sky

“That players are like the Customers from McDonalds or from other restaurants. They wan't everything the instant they ask for it, and don't expect things to take time. They give all the input, and the next day they think things should be instantly done. “

“We should phase out versions and features instead of chunking it all together. First off to hear the feedback and secondly to fix any issues there may appear regarding the released feature, rather than releasing 20 features at the same time, and then being stressed out that the 20 features are all throwing errors and there's people left and right asking for "fix dis"

Sky’s advice? Pace yourself. The community’s enthusiasm is awesome, but trying to deliver everything at once can lead to chaos. 

Fuzu

“One of the biggest lessons we learned:
 Listening to the community is key to guiding the project — but not every idea should be followed.”

Fuzu hit on something every dev learns sooner or later. Community input is golden, but you still have to steer the ship. Not every suggestion fits the game’s vision (or is remotely feasible).

O’Brian

“Keep it simple. The dumbest ideas often work best. We learned to listen to the community, test fast, and not overthink features.”

O’Brian reminds us that overthinking can kill the fun. Quick feedback loops and wild ideas sometimes produce the best results.

Outrem

“Working on Banana, I learned a little more about how the Steam gaming world works. I was able to understand a little about the Steam market economy, something I had no idea about until now. As a team, I think we realized that a big boom doesn't mean there's no work to be done. We've always tried to take on the challenges associated with game and community development. As someone who works on the web side, most of my work was already something I was familiar with, but the context of being connected to a game made everything better.”

Outrem came into Banana with web dev experience, but working on a game changed everything. Even as the game exploded in popularity, the team learned there’s no “coast mode”, just new challenges to solve.

Thanks for being part of the Banana journey. We’re still learning, still clicking, and still trying to make this community-powered game something special.

🍌 Stay peeled