A Six-Person Team Built an AI Game That Teens Say They Prefer Over Real Social Media

Most AI gaming stories right now are about tools: engines, asset generators, voice models. Status is a story about what happens when a tiny team points those tools at something nobody had really tried before, an entire social media platform where every other user is an AI character.

What Status Actually Is

The pitch is disarmingly simple: The Sims, but it's social media. Players create a persona, pick a fandom or build an original character, and drop into a Twitter-style feed and DM system where AI-driven characters post, reply, and message back. Founder Fai Nur has described the goal plainly, building something for her own teenage self, the kind of person who was deep into fandom and fanfiction and wanted a space to live that out.

It's built by WishRoll, a six-person team that met on social media during the pandemic, went through Y Combinator together, and spent three years building toward this before Status took its current shape. Since public launch in early 2025, the app has passed 500,000 daily active users and multiple million registered accounts, with players spending an average of roughly an hour and a half a day inside it.

Why It's Actually Sticking

The most interesting result isn't the growth number, it's what players say when asked why they keep coming back. Nur has said users repeatedly tell the team they prefer Status to real social media, specifically because it isn't toxic and they feel in control of their own story. Players can even self-localize the experience just by writing something like "everyone in here speaks Spanish" into their profile, and the AI adjusts accordingly.

That's a genuinely different value proposition than most AI-in-gaming stories, which tend to be about making existing kinds of games cheaper or faster to build. Status isn't really competing with other games. It's competing with Instagram and Twitter, using AI to build something that scratches a similar itch without the parts people say they hate about those platforms.

The Part Every Small Team Should Pay Attention To

Status nearly got crushed by its own success. The game launched on Claude 3.5 Sonnet, and as it scaled toward its DAU peak, the AI inference bill turned into a genuine survival-level problem for a team this size. They partnered with Inworld AI and restructured how the game actually talks to its models, splitting one general-purpose prompt into specialized categories for character posts, random content, and news updates, then built custom evaluation systems to check things like content variety and tone before responses ever reached a player. The result, according to Inworld's own case study on the partnership, was a 90 to 95 percent cut in AI costs without a drop in quality. Worth noting that figure comes from Inworld promoting their own product's results rather than an independent audit, though the broader story of a small team hitting a cost wall and needing to re-architect their AI pipeline to survive is corroborated separately by a GDC presentation on the game.

For solo devs and small teams, that's arguably the most useful part of the whole story. It's not the Twitter-for-AI-characters concept, replicable or not, it's proof that the biggest threat to a hit AI-native game isn't running out of ideas, it's running out of budget the moment people actually show up.

The Honest Downsides

It's not a spotless success story. Players have flagged real friction: AI drift, where characters lose consistency and start repeating themselves over long sessions, and an energy system limiting how much you can play at once, which lands especially hard given the core audience skews teenage and doesn't always have spending money to bypass it. According to a GDC talk from the team, Status also didn't retain users from its initial peak the way they'd hoped, growth and staying power turned out to be two separate problems.

Worth being clear-eyed about that rather than treating this as an unqualified win. AI-native games are still genuinely new territory, and Status is as much a lessons-learned case study as it is a success story.

Why It's Worth Knowing About

Status is proof that a small team without a AAA budget can build something in a completely new format and actually find an audience for it, not by making a better traditional game faster, but by making something that couldn't have existed without AI at its core. Whether that model holds up long-term is still an open question. But as a data point for what's possible outside the usual asset-pipeline and NPC-dialogue stories, it's one of the more genuinely novel things to come out of this space.

Would something like Status appeal to you as a player, or does it feel like a step too far from what a "game" should be? Let us know your thoughts in the comments. And if you've got a game you'd like us to review, send it over to editor@gamevibe.io.

Leave a Reply

Your email address will not be published. Required fields are marked *

Share with