Design Challenge: Starcraft PC to Mobile

Every two weeks a UX designer is selected to present a topic they are interested in. It can be a new discovery, game design breakdown or design challenges.
For one of my presentations, I decided that it would be an interesting exercise for me to redesign a PC game for mobile.

I chose Starcraft!

Why Starcraft you may ask, I wanted to find a game that has not been translated from PC to mobile. At the time, I was actively playing Heroes of the Storm, however I noticed a surge in mobile MOBA so HOTS is a no-go for me. As for Starcarft, I have yet to see a mobile game of its genre (at least to that level of complexity) So to me, this is an open canvas with endless possibilities!

THE PROCESS:
· 1 week playing Starcraft (mostly campaign and only Terrance)
· 1 week designing

[Disclaimer] The design solutions shown are based on my understanding of the game during the 1 week play session with Terrance without any consideration of how the other races play and strategize.

  • Date 2018 (2 weeks)

Disclaimer: This is only an exercise

Before sharing the design solution, I walked through all the possible builds and upgrades a Terrance player can do while in combat.
This helps give the audience (especially those that have not played Starcraft) some framework of the game.

By breaking down the builds by its functionality, I identify that some of the things can be simplified for mobile.

SCV/Supply Depot are required to build, upgrade and repair, however it requires a lot of micro management. Instead, converting it into a currency (Ruby) that increases overtime. Players will require the currency to create more infantry/vehicles or repair damaged buildings and since the currency is limited, players will need to strategize on how they want to spend the resource.

Another thing that I removed is the Refinery to gather gasoline. How I imagine this to work is by building a Command Center, players are given a set amount of workers that will take time to build, repair, upgrade and gather resources. Players will need to spend the Ruby if they choose to add more workers.

Lastly, I merged Engineering Bay, Ghost Academy and Armoury into one building. How I imagine this to work is that this is a late game expansion that players can choose upon building if they want the building to specialize in the engineering bay, ghost academy or armoury.

Once the system is simplified, the next step is to figure out the flow.
Since Starcraft requires players to micro and macro all things from economy and resource management (what to invest in), building, unit management, map awareness and opponent. I wanted to break them down into 2 steps to help reduce cognitive overload.

PLAY and BUILD
(Players can go back and forth from build & play with a tap of a button)

PLAY is where I anticipate players to be most of the time. Building up their units, assigning them to location to defend/attack. Repair any damaged buildings if required.

BUILD is where players are able to build more buildings, relocate, upgrade for add-ons or destroy the buildings

·
SITE MAP
Because I only had one week to design the solution, I was not able to complete the design to cover all the necessary functionalities. Below is the Play and Build site map to help visualize what the players should be able to do.

Below are mockups created for this exercise.