Competitive Events UI
After months of development, we were able to slate the greatly anticipated Competitive Events feature into MS13. This would replace the arduous process of handling Live Ops manually in Discord, which included handing out rewards to Users individually at the end of each event.
At the time (13 milestones in), the Product's interface was fairly mature and design and integration happened in the same step. To save time on engineering, we decided to reuse elements that had already been resolved of all navigation code, including basic tabs, scrollers, and rankings.
The team's size had also been reduced and I was the dedicated UI designer and mostly an Individial Contributer at this point. I cobbled together multiple dialogs and prefabs in Unity and presented them to the team for Review in Confluence.
After getting Product and Engineering sign off, I made some minor changes, checked in all the assets, and sent along instructions for development.
Implementation notes can be a lot to take in despite efforts at precision, so there are usually several discussions. Sometimes, certain prefabs need to be rebuilt or refactored in a way that can utilize a different script or so that a new script can be more easily hooked in. After engineering, we reviewed with the product team once again, using their test data, ensuring that all information was being fed in correctly from the backend as well.
Art templates are also created concurrently so that the production team can continue to support this feature with promo images delivered independently of client updates via AWS servers.
Event Promo images by Michael Tran.
