Kick It Multiplayer

About Kick It Multiplayer

For Curwen, tackling the problem therefore means changing the risk-reward equation behind game creation. If creators can develop and test ideas more quickly and at significantly lower cost, an unsuccessful experiment becomes less consequential – and taking a chance on something genuinely different becomes easier to justify.

“Technology changes the equation,” he says. “If we can make development faster and significantly more cost-efficient, creators can afford to experiment again.

“I’ve said before that I think we’re moving towards the end of the traditional reskin model. Players don’t need another 100 versions of effectively the same game.”

What is Kick It Multiplayer?

Retention has provided another encouraging signal. Depending on the market, Yashin says day-one, day-seven and day-30 retention can range from around the crash-game benchmark to between five and 10 times higher. The number of rounds played during a session can also be significantly greater.

The explanation, he believes, comes back to the behaviour that inspired Swipe Games in the first place. Crash players may experience a different outcome each time, but visually they repeatedly encounter much the same thing. Social media has conditioned its users to expect something new with every swipe.

“People are not playing it just as a quick crash game,” Yashin says. “They play it more like they are betting. It is a different pattern.”

What is Kick It Multiplayer?

That raises a question about how future developers will enter the industry. If Cubeia no longer needs front-end traditional junior Java developers in the same way, the traditional path from junior programmer to senior engineer becomes less clear.

“How do we avoid ending up with lots of old Java developers and nobody who understands Java because the juniors were never hired? That’s a super-interesting question. How do we fill up with younger people over time? That’s something we’ve been discussing.”

Cubeia is also moving away from the traditional process in which a developer builds something and then hands it to QA.