:no_upscale())
Client
Adult Swim Games
Pocket Mortys
Six years as Adult Swim Games' development partner on Pocket Mortys — owning live ops, content and backend for a mobile title with millions of players.
Year
2017
Service
Live Ops
Platforms
:no_upscale()){kind=icon}
:no_upscale()){kind=icon}
:no_upscale()){kind=icon}
:no_upscale()){kind=icon}
:no_upscale())
The Challenge
Pocket Mortys arrived as a mobile phenomenon, built on the back of the Rick and Morty universe. Adult Swim Games needed a partner who could keep it growing years after launch, at the pace of the show itself — which meant working from unreleased episodes months ahead of air, with everything that entails. We took full ownership of live ops: new content, new features, the server architecture behind it, and a release cadence that put features in players' hands the week an episode landed.
10M+Players
800kMAU
550+Mortys
90+Updates
Our Role
What We Owned
01
Content
Dropping weekly content directly tied into the shows’ episodes
02
Server Architecture
Building a bespoke AWS stack that could scale to hundreds of thousands of players
03
Compliance
Keeping compliant with Google and IOS alongside changing privacy standards
04
Game Design
Designing features, characters and dimensions from scratch inside and expanding on the established IP
The Stack
Full Platform Technical Stack
What We Deliver
Platforms
:no_upscale()){kind=icon}
iOS
:no_upscale()){kind=logo}
Android
Backend
:no_upscale()){kind=logo}
AWS
Engine
:no_upscale()){kind=logo}
Unity
Stack
:no_upscale()){kind=icon}
Node JS
:no_upscale())
Rabbit MQ
:no_upscale())
Redis
:no_upscale()){kind=logo}
Postgres
Technical
What Made This Hard
01
Shipping To A TV Schedule
Content had to land with episode air dates. We published an advert directly after the episode landed and content needed to be live then, no earlier.
02
An Evolving Mobile Market
The phones, the store policies and the privacy landscape all changed underneath us. Every one of those changes had to be absorbed without disrupting a game already in players' hands.
03
Traffic that spikes with the show
Backend had to hold under sudden load when an episode aired, we needed build an architecture that could economically grow when the show did
What Studios Say
Let's Work Together
Ready to ship something great?
We partner with studios that need technical depth and production confidence.
:no_upscale())