Indie Games That Remember You're Playing
SkyLine Corp is a small game studio in Phoenix, Arizona. We build narrative-driven indie games where your decisions actually matter — not the kind where you pick dialogue option B and get the same ending anyway. Currently in early-stage development for our first commercial title. No investors, no ads baked into our games, no microtransaction dark patterns.
This site is for people curious about what we're building, indie developers looking for honest writing about the craft, and potential collaborators who want to understand how we work before reaching out. If you're looking for AAA spectacle or free-to-play mobile stuff, that's not our lane.
We're not charging for anything right now. Our blog posts and development updates are open to read, and our games — when they ship — will be sold at a fixed price with no hidden costs.
Read our latest thinkingI keep coming back to something that happened during a game jam in 2018. There were maybe forty people crammed into a university classroom in Tempe, all trying to build something playable in 48 hours. The team that won didn't have the best art or the most polished mechanics. They had a three-minute interaction where you played as a voicemail system. Just a voicemail. You listened to messages from someone you used to know, and at the end you could delete them or save them. That was the whole game. And people sat there staring at the screen afterward because the weight of that small choice hit different.
That moment stuck with me for years, and it eventually became the reason SkyLine Corp exists. Not because voicemail games are the future — obviously they're not — but because the constraint of having almost nothing forced a design decision that no big studio would ever greenlight. There was no market research behind it. No focus group said "we want more voicemail mechanics." It worked because someone cared about one specific feeling and built everything around it.
The Entertainment Software Association reports that over 65% of Americans play video games. The vast majority of revenue goes to a few dozen publishers. But here's what that statistic misses: the games people talk about ten years later, the ones that change how they think about the medium, almost always come from teams small enough to fail. And that's not a coincidence. Small teams can't afford to play it safe, and playing it safe is exactly what makes most games forgettable.
How We Actually Make Games
Our process is not glamorous. There's no war room with mood boards and synergy diagrams. Most of our early design work happens in shared documents and voice calls where someone inevitably has a bad connection. The unsexy truth about indie development is that 80% of the work is just deciding what not to build.
We start every project with what we call a "feel target" — a one-paragraph description of what the player should feel at the game's most important moment. Not a feature list. Not a genre label. A feeling. Everything else gets measured against that paragraph. If a mechanic or a story beat doesn't serve the feel target, it gets cut, even if someone on the team spent weeks on it.
Sounds harsh? It is, a little. But I've seen too many projects collapse under the weight of good ideas that didn't fit. Feature creep kills more indie games than bad code ever does.
One thing I always tell new collaborators: we prototype in days, not months. If an idea can't be tested with placeholder art and a janky build within a week, the scope is wrong. The best prototype I ever worked on was literally colored rectangles moving around a gray screen. It proved the core loop worked, and that was all we needed.
What We Do (and Don't Do)
Narrative Game Development
We design and build interactive experiences where story and gameplay aren't separate layers duct-taped together. Our focus is on games where the narrative emerges from what you do, not just what you're told between cutscenes. This means branching systems, environmental storytelling, and mechanics that carry thematic weight.
- We don't write linear visual novel scripts without interactive mechanics
- We don't work on projects requiring real-time multiplayer infrastructure
Game Design Consulting
Sometimes a project doesn't need a full development partner — it needs a second set of eyes. We review design documents, prototype core loops, and help teams figure out why something feels off even when all the pieces seem right on paper. Most consulting engagements run two to six weeks.
- We don't provide art asset production or animation services
- We don't consult on monetization strategy or ad integration
Writing About Games
This blog exists because we think the indie game space needs more honest writing — not listicles or hype pieces, but actual analysis from people who build these things. We write about design decisions, development realities, and the gap between what players expect and what developers can actually deliver.
- We don't accept paid reviews or sponsored content deals
- We don't write guides or walkthroughs
From the Blog
Why Most Game Stories Fall Flat — And the Few That Don't
Honestly, most game writing is mediocre — but the exceptions taught me more about interactive storytelling than any textbook.
How to Prototype an Indie Game When Your Budget Is Basically Zero
A practical look at prototyping tools and methods that work when you can't afford to waste time on the wrong approach.
Going Solo or Building a Small Team? A Honest Comparison for Indie Devs
Neither path is universally better. Here's what actually changes when you add people to the mix.
Questions People Actually Ask
Fair question, and honestly the answer depends on what you need. Small studios tend to be more hands-on and responsive because there is no middle management layer between you and the people doing the work. Our track record is transparent — we share our process openly on the About page and keep communication direct. That said, if you need a team of 50 and guaranteed SLAs, a larger outfit is probably the better call.
For a narrative-focused indie game with a small team, expect 18 to 36 months from initial concept to public release. That includes prototyping, production, testing, and launch preparation. Smaller scope projects like game jams or short interactive pieces can wrap in weeks. We wrote more about this in our prototyping guide.
We primarily work with Godot for 2D projects and Unity for anything requiring 3D or cross-platform deployment. Engine choice depends on the project, and we're honest about which tool fits best rather than defaulting to one option. For a breakdown of engine trade-offs, the r/gamedev community has ongoing discussions that are genuinely useful.
Yes, selectively. We take on a limited number of contract projects each year, provided the scope aligns with our strengths in narrative design and interactive storytelling. We turn down projects that fall outside our wheelhouse — see the "what we don't do" section on our Services page for specifics.
Yes, but with caveats. Solo development is viable for certain genres and scopes — puzzle games, narrative adventures, and short-form experiences. It becomes much harder for content-heavy genres like RPGs or open-world games. The key is scoping honestly. We break this down in detail in our solo vs. team comparison.
We run internal playtests weekly during production, bring in external testers at major milestones, and use structured feedback forms rather than casual impressions. Testing starts early — we'd rather find a design flaw in a paper prototype than in a nearly finished build. Structured usability testing methods influenced how we run our sessions.