Our Philosophy - Buttonmash

Our Foundation

We started making arcade games because we wanted to create experiences where people play together in the same physical space. That core motivation still drives everything we do.

Over time, we've developed specific beliefs about how to do this work well. These aren't abstract ideals but practical principles that emerged from making games, watching people play them, and learning what works in real arcade environments.

Our values guide our decisions when we face trade-offs. They help us stay focused on what matters when projects get complicated. They're the reason we turn down work that doesn't align with how we think games should be made.

Philosophy & Vision

We believe arcade games should bring people together through shared experiences that are accessible, reliable, and genuinely engaging.

Our Approach to Transformation

We're not trying to revolutionize arcade gaming. We're trying to do the foundational work well: building games that function reliably, respect players' different skill levels, and create opportunities for meaningful interaction.

This means sometimes choosing proven approaches over novel ones. It means prioritizing what works for players over what's technically impressive. It means being honest about limitations rather than overpromising.

What We Believe Is Possible

We think arcade games can offer experiences that other platforms don't provide. The physical presence of other players, the immediate feedback of shared space, the social dynamics of public play—these create possibilities that home gaming can't replicate.

But realizing these possibilities requires designing specifically for arcade contexts rather than treating them as just another platform. It requires understanding player behavior in these spaces and building games that work with those patterns rather than against them.

Core Beliefs

Players Come First

Every design decision should consider how it affects the people who will actually play the game. Not the people we wish would play it, but the actual humans who will interact with it in arcade environments.

This influences everything from control schemes to difficulty curves to visual feedback. We test with real players and adjust based on how they actually behave, not how we think they should behave.

Reliability Matters

Games that don't work consistently aren't just technical failures—they damage player trust and operator confidence. We build for continuous operation because that's what arcade deployment requires.

This means sometimes choosing less ambitious technical approaches if they're more reliable. It means extensive testing under stress conditions. It means writing code we can actually maintain.

Cooperation Over Competition

We're drawn to cooperative experiences because they create different social dynamics than competitive ones. Players helping each other, communicating, figuring things out together—this interests us more than zero-sum competition.

This doesn't mean cooperative games are inherently better, just that they align with what we want to create. We think there's room for more thoughtful cooperative design in arcade spaces.

Context Shapes Design

Arcade environments have specific characteristics—noise levels, lighting, physical layout, social dynamics. These aren't obstacles to work around but factors to design for.

A game that works beautifully in a quiet testing environment might fail on a busy arcade floor if it relies on subtle audio cues. We design with the actual deployment context in mind from the start.

Honest Assessment

We'd rather tell clients when something isn't feasible than take their money for work we can't deliver properly. This means turning down projects sometimes, which isn't always comfortable but feels right.

It also means being upfront about challenges, limitations, and uncertainties. Projects go better when everyone has realistic expectations from the start.

Accessibility Through Design

We want people with different skill levels to play together effectively. This requires thoughtful design, not just difficulty settings. It means creating systems where different players can contribute in different ways.

Accessibility isn't an add-on feature. It's a fundamental design consideration that shapes how we approach cooperative systems, control schemes, and feedback mechanisms.

Principles in Practice

How Beliefs Become Features

Our belief in player-first design translates to specific development practices. We test games in conditions that mirror actual deployment rather than idealized testing environments. We watch how real players interact with systems and adjust based on observed behavior.

When we say we prioritize reliability, that means architectural decisions that favor proven approaches over cutting-edge ones. It means building in redundancy. It means extensive stress testing before deployment.

Design Choices That Reflect Values

Our focus on cooperative play means we design asymmetric systems where different players can take different roles. Less experienced players might handle support functions while skilled players manage more complex tasks. Everyone contributes; no one gets carried.

Context-aware design means we consider noise levels when implementing audio feedback, plan for various viewing angles, and structure sessions around realistic play durations for arcade environments.

When Principles Create Constraints

Our commitment to honest assessment means we sometimes can't take projects we'd like to work on. If we don't think we can deliver what a client needs within their constraints, we say so even when it costs us business.

This approach has trade-offs. We work on fewer projects. We probably make less money than we could. But the projects we do take on tend to go better because expectations are realistic from the start.

Human-Centered Approach

We make games for people, which sounds obvious but shapes our work in specific ways.

Respecting Individual Needs

Players come to arcade games with different backgrounds, skills, and expectations. We can't serve everyone equally well, but we can design systems that accommodate variation rather than requiring everyone to play the same way.

This influences control schemes, difficulty systems, and how we structure cooperative mechanics. It's about creating space for different approaches rather than enforcing a single correct way to play.

Client-Centered Development

When working with clients, we focus on understanding their actual needs rather than selling them our preferred solutions. Sometimes this means recommending against features they think they want because we don't think those features would serve their goals.

We'd rather have difficult conversations early than deliver something that technically meets specifications but doesn't actually solve the client's problem.

Empathy in Design

Understanding player perspective requires more than demographics or personas. It requires watching how people actually interact with games, noticing where they get confused or frustrated, and adjusting accordingly.

This means being willing to change elements we're attached to if players consistently struggle with them. Our preferences matter less than player experience.

Communication That Connects

We try to explain technical decisions in accessible terms because clients deserve to understand what we're doing and why. If we can't explain something clearly, that's often a sign we haven't thought it through properly ourselves.

Clear communication builds trust. It helps clients make informed decisions. It reduces misunderstandings that lead to project problems later.

Innovation Through Intention

How We Approach New Ideas

We're interested in innovation that serves players rather than innovation for its own sake. New approaches need to offer real advantages over existing ones, not just novelty.

This means we're sometimes conservative in our technical choices. Proven approaches that work reliably often serve players better than cutting-edge techniques that introduce risk without clear benefit.

Continuous Improvement Within Constraints

We try to get better at our core work rather than constantly expanding into new areas. Deep expertise in arcade development serves our clients better than shallow knowledge across many domains.

This doesn't mean we never try new things. It means new directions need to align with our focus on arcade experiences and cooperative gameplay.

Balancing Tradition and Progress

Arcade gaming has established patterns that work. We respect these patterns while looking for opportunities to improve them. Sometimes that means doing things the traditional way. Sometimes it means finding better approaches.

The key is having reasons for our choices rather than following tradition blindly or pursuing novelty for its own sake.

Integrity & Transparency

Honest About Capabilities

We tell clients what we can and can't do. This includes admitting when we're uncertain about something or when a project pushes the edges of our expertise. Pretending to know more than we do helps no one.

Open Process

Clients can see how we work and ask questions about our decisions. We explain our reasoning even when that reasoning is "we tried three approaches and this one worked best" rather than some elegant theory.

Accountability for Results

When things don't work as planned, we take responsibility for finding solutions. Sometimes that means extra work we didn't bill for. That's part of standing behind our work.

Building Trust Over Time

Trust comes from consistent behavior more than promises. We try to deliver what we said we would, communicate clearly about challenges, and handle problems responsibly when they arise.

Community & Collaboration

Arcade games exist in community contexts. We think about how our work affects those communities.

Working Together

We approach client relationships as collaborations rather than service transactions. Clients often know their specific contexts better than we do. Our expertise works better when combined with their knowledge.

Supporting Operators

Arcade operators keep games running and maintain player communities. We try to make their work easier through reliable implementation and clear documentation.

Player Communities

When games work well, they become part of arcade communities. Regular players develop relationships around them. We think about these social dimensions when designing.

Collective Growth

We learn from other developers, from operators, from players. The arcade community has accumulated knowledge we benefit from. We try to contribute back when we can.

Long-term Thinking

Beyond Launch Day

A game's launch is the beginning of its operational life, not the end of development work. We build for sustained operation rather than impressive demos.

This influences technical architecture, maintenance considerations, and documentation. Games need to work reliably months and years after deployment.

Sustainable Practices

We try to work in ways we can maintain long-term. This means not overcommitting, not burning out our team, and not taking shortcuts that create problems later.

Sustainable work produces better results than cramming everything into unrealistic deadlines. We'd rather deliver quality work on a reasonable timeline than rushed work that needs extensive fixes.

Building for Lasting Impact

We want to create games that people remember positively, that contribute something worthwhile to arcade spaces, that operators feel good about running.

This isn't about creating masterpieces. It's about doing solid work that serves its purpose well and stands up over time.

What This Means for You

Our philosophy translates into specific things you can expect when working with us.

Honest Communication

We'll tell you when something isn't feasible rather than promising things we can't deliver. We'll explain technical decisions in accessible terms. We'll keep you informed about progress and challenges.

Player-Focused Design

Your game will be designed specifically for arcade contexts, accounting for how players actually behave in these environments. We'll test with real players and adjust based on observed behavior.

Reliable Implementation

We prioritize technical reliability because arcade games need to run continuously without constant intervention. You'll get something that works consistently, not something that impresses in demos but fails in operation.

Collaborative Process

We'll work with you to understand your specific needs rather than imposing our preferred solutions. Your input shapes the final product because you know your context better than we do.

Our Promise

We'll give your project the attention and expertise it deserves. We'll be honest about what we can deliver. We'll build something that works reliably and serves your needs.

We won't always be the cheapest option or the fastest. But we'll do the work properly, and we'll stand behind it.

Does This Resonate With You?

If our approach aligns with what you're looking for in a development partner, we'd like to talk with you about your project. If it doesn't, that's fine too—we'd rather have that clarity upfront.

Start a Conversation

What We Believe About Making Games