Personas
This page defines the set of personas that are used by the Mixed Reality Toolkit are used to scope discussions by target audience and to help in the decision making process.
Developer personas are intended to represent categories of developers rather than individuals. In fact, many developers and projects are likely to span multiple personas.
Creators are more interested in the final product than in the tools used to achieve it. They possess a strong design sense and the experience of the end user is always their first priority. They may have moderate-to-strong scripting skills, and they're willing to customize a tool when it impedes their design goals, but they don't enjoy tinkering for its own sake. Anything they release is always highly polished.
Hobbyists have a wide variety of skill levels. They may be a novice developer with strong design skills, an experienced developer who is prototyping a project or have no coding background and are creating their first project. They are often interested in seeing results quickly (at a hackathon, for example). Generally use the Mixed Reality Toolkit components without modification and add experience specific assets.
Experience developers are generally employed to build applications. They have experience with the tools and languages and write a significant amount of code for their experiences. These developers will likely use the default MRTK system implementations and customize the presentation layer (controls, visuals, behaviors) extensively in their applications.
Expert developers are well versed in the tools and languages needed to build well performing, high quality experiences. They likely also have extensive Mixed Reality platform experience, though that is not a criteria of this persona.
Description coming soon.
Project personas define the starting point for experience development. Over time, it is anticipated that projects may move from one persona to another.
Green field projects are new projects that do not have pre-existing code. They are begun by importing and configuring the Mixed Reality Toolkit. As these projects evolve, customization of the MRTK components may occur.
Pre-existing projects have one or more scenes of code and assets. They may have been started as flat (2D) applications or using other toolkits (ex: HoloToolkit). These projects will leverage the Mixed Reality Toolkit to enable one or more scenarios and may require some integration work (ex: implementation of one or more interfaces to enable communication with MRTK components).
Hand tuned projects are heavily customized. They may or may not have begun as a Green Field or Pre-existing project. These projects have been extensively tuned and optimized for one or more platforms and may have specific requirements for their development and maintenance.
Project Management
Contributing