yego.me
💡 Stop wasting time. Read Youtube instead of watch. Download Chrome Extension

YC Tech Talks: MMOs in the Instagram Era: Highrise (S18)


3m read
·Nov 5, 2024

Processing might take a few minutes. Refresh later.

Um, hi everybody. I'm Jimmy. I'm the co-founder and CTO of Pocket Worlds, where Highrise is. We built Highrise, the app which is available on iOS and Android, and I think to date it has over 5 million downloads, and we're grossing over a million a month in revenue.

So today, I'm going to walk you guys through the process of designing and building an MMO game in this era of mobile apps and social networks. I'll talk about the architectural design decisions that we made that enable Highrise to feel simultaneously like an app and also a game, and why that's really important. I'll also talk about our vision as Pocket Worlds and how we plan to leverage the Highrise architecture to create more exciting social-first game experiences and worlds.

So for those that are not familiar, Highrise is a social-first design MMO. Players come in, they design an avatar, they build an apartment, they go into this fully user-generated world to visit other people's spaces and take part in challenges. The unique part of Highrise and the Highrise experience compared to the multitude of games that you see in the app store is our design philosophy that we call social first.

With traditional game design, you often have a game designer that would come up with a game, a mini-game concept, and then would build out a metagame loop and finally sprinkle in some social features like clans, inbox, marketplace, as almost an afterthought. Under the social-first philosophy, what we do is we start with the messenger, a news feed for community, guilds, profiles, an economy, and a vibrant world, and then we add in the game.

In the case of Highrise, that game is a straightforward fashion contest where you design outfits and compete with other players. The core part of why social first works is that it solves the critical piece that's missing in most mobile games today, which is the issue of long-term attention. A player joins Highrise for the design game, but they really ultimately stay for the friends they meet in our world.

But as you can see, kind of from the screenshots on the left, our heavy focus on social features really requires us to feel like an app, very much like Snapchat or Instagram. Otherwise, users will come in, play the game, make their friends, and then really move to those other platforms once they're done and kind of gotten everything they can out of the game. And that's precisely what we saw in the early days of Highrise.

So to achieve that user experience, we really realized that we must leverage the UI capabilities native to iOS and Android and could not rely on anything that game engines like Unity can offer. There's just really no way that Unity could compete with Apple's 40 years of experience perfecting fonts and UI animations.

So the architecture that we came up with actually mirrors our product's position of being percent app and fifty percent game. It is fifty percent Swift and Kotlin on the Android side and fifty percent C++. The Swift component handles all UI to create the silky smooth native feel, and the C++ component handles the game engine, the world, the avatars, business logic, and is shared as a sub-module between iOS and Android.

The components are seamlessly integrated via a system of bridges that are separated by feature, which creates a nice little microservices architecture that we can swap components in and out of. The bridging between the components is achieved using Objective-C++ on the iOS side and JNI on Android. The secondary objective here is, of course, to offload as much of the heavy lifting as possible into the core to help with cross-platform development, which we were able to achieve.

So I think what's more interesting is that this architecture really enables us to create different games and products that offer different experiences by swapping out the mini and the metagame of Highrise with something else. So maybe, I'm thinking like a hero collector where you're walking around in our virtual world collecting monsters to do battle with, with the exact same avatar world messenger guild system as Highrise, or an adventure...

More Articles

View All
Michael REVEALED !!!!
Hey, Vsauce! Michael here, and I’m flying to Dallas today to see my sister. But until then, I thought it might be fun to show you a handful of the over 200 videos I made before Vsauce. That way, you can get to know me a little bit more intimately. The fi…
Why Military Veterans Are Turning to Archaeology | National Geographic
Most people think of archaeology as telling us about the past. What we’re trying to do is actually use archaeology to improve people’s lives in the present. In this particular program, we’re aiming that specifically at military veterans and trying to use …
YC SUS: Kat Mañalac and Eric Migicovsky discuss Week 2 SUS Lectures
Good morning everyone, and good evening. It could be anywhere actually. I’d like to start somewhere. My name is Eric, and I’m the facilitator, of course, facilitator here at Startup School. It’s a pleasure to be joined by Kat. “Hi everyone, I’m Kat, a pa…
My Investing Plan for 2022...
So it’s that time of year. Time to start making plans and setting goals for 2022, because yes, we only have two weeks left in 2021. It’s pretty ridiculous if you ask me. But in this video, I’m going to be running through my full investing plan for next ye…
Mars 101 | MARS
[Music] In the early formation of the solar system, when all the planets were being formed, Mars and Earth were actually surprisingly similar. Mars at one time was once fertile, temperate, much like Earth. And, uh, something happened to it. There are mas…
Units of the rate constant | Kinetics | AP Chemistry | Khan Academy
[Voiceover] In this video, we’re going to be talking about how you can find the units for your rate constant k. So the two things you should know before we get started are that, one, rate constant k has units. So this isn’t always true of constants in c…