USE CASE – DEEP DIVE
Code named…
…our team set up shop on a vacant floor within the Disney building, much like a start-up company.
We were challenged to design the first ever interactive toys that would sync to a tablet app and communicate with "smart" toys, hence Playmation was born.
Playmation is a new line of wearables, connected toys, and apps that use Bluetooth wireless technology, cloud computing, and the voices of Marvel characters to immerse players in an augmented reality battle between super heroes and super villains.
I have a very purposeful approach to business requirements, functional requirements and workflows.
We had multiple development teams and design teams across several time zones. It becomes extremely important to keep business requirements and functional requirements well documented.
Listing out all the requirements in an organized fashion, when aligning to the wireframes, we can be certain our blueprints solve everything.
Initial framework started with Disney ID sign in, which enables cloud connectivity between all Disney products and services.
I became somewhat of the liaison between the Seattle development teams, and the creative teams in Glendale.
By creating a synchronized list of workflows, I associated the Seattle originated API calls, with the Glendale originated UI designs, mapping out each user flow of the app with the appropriate API calls. This enabled both teams to communicate efficiently with each other.
