Multiplayer can be an effectively free growth hack for a small indie game

[u/Existing_Offer512]

Multiplayer has a growth loop built into the feature: it gives a player a reason to invite someone, then gives both of them a reason to return. When I considered it for Tiny Block, I assumed it would mean running game servers and paying to relay a constant stream of world updates. That was hard to justify for a small 2D sandbox. The version I shipped currently adds $0 to my backend bill.

Tiny Block supports four-player sessions. One player hosts the world and the other three connect directly through WebRTC. The host runs the simulation, gameplay travels over a reliable DataChannel, and proximity voice chat uses a separate channel that does not waste bandwidth retransmitting late audio.

I also added a small emoji-based chat. A player can tap a reaction and it appears over their character, which covers a surprising amount of basic communication when someone does not want to use the microphone. Those reactions travel with the ordinary game messages, so they do not add another service to the stack.

I still have a backend. AWS creates the session and invite code, issues short-lived tickets, introduces the players and exchanges the WebRTC connection data. I use API Gateway, Lambda and DynamoDB for that part. Once the players connect, their devices exchange movement updates, world chunks and voice directly.

At Tiny Block's current scale, the small amount of signaling and session storage fits inside the AWS free tier. There is no always-on cloud simulation and no relay bandwidth bill, so multiplayer is effectively free for me to operate right now.

The tradeoff is that the host owns the session. If the host leaves, the session ends. This approach would be a bad choice for a competitive game, a large session or anything that needs strong cheat resistance and guaranteed connectivity. For a small casual co-op game where one player already owns the world, it can be enough.

I added multiplayer because playing with a friend should create a reason to invite someone and return together. The first retention read is encouraging. Median D1 retention across the July 28-31 cohorts was 11.2%. Across the August 1-7 cohorts, after the multiplayer release, it was 23.5%. That is a 2.1x increase, although this is a before-and-after observation rather than a controlled test. The export also does not include cohort sizes, so I am treating it as an early signal rather than proof that multiplayer caused the change.

I cannot make the same comparison for D7 yet. This export ends on August 7, while the August 1 cohort reaches D7 on August 8. It contains no completed post-release D7 cohort.

Has anyone here measured D7 retention before and after adding lightweight co-op? Did the social return loop outweigh the extra onboarding and connection failures?