Congratulations on making it to the end of the Unity Mixed Reality course. Hope at this point, you are excited to start building your own projects.

Read through some of the case studies and discuss the lessons learned. If you already have an idea, consider some of the limitations and experiments in terms of how they might apply to your own project.

• Mozilla Mixed Reality Case Studies

• Google ARCore Case Studies

• AfterNow's process - envisioning, prototyping, building

• Chacmool: Augmented reality in Chrome Canary

• Representing humans in mixed reality

• Lessons from the Lowe's kitchen

• My first year on the HoloLens design team

• Capturing and creating content for HoloTour

• The pursuit of more personal computing

• Building HoloSketch, a spatial layout and UX sketching app for HoloLens

• Expanding the design process for mixed reality

• Expanding the spatial mapping capabilities of HoloLens

• HoloStudio UI and interaction design learnings

• Looking through holes in your reality

• The Making of Galaxy Explorer for HoloLens 2

• Scaling Datascape across devices with different performance

• Spatial sound design for HoloTour

• Using spatial sound in RoboRaid

• Using the stabilization plane to reduce holographic turbulence

• Providing access to captivating experiences through immersive augmented reality

• 7 Inspiring Case Studies on VR and AR

• Augmented Reality Case Studies & Examples - INDE

• Immersive Performance Training - STRIVR

Is there a demand for the application you want to build?

It is fun and useful to build an application for learning purposes, although there are some advantages to consider the user base if your application. Having a target audience might help you:

• Make better design decisions.

• Makes it easier to sketch out minimum viable product(MVP).

Deciding on a project, investing your time and effort into it, and finding out a crucial feature you wanted to have is not possible is the disappointing. Nevertheless, it happens all the time. Teams lose their motivation, time, and resources: sometimes projects are abandoned. It is wise to invest 1/3 of your time into research and design process, since it is going to have the most effect on your application.

Check out the what could go wrong list before you start your brainstorming session.

Your idea might not be possible technically

List the features and APIs that you need before you start thinking about the details of your application.

For example, if you are planning to use both front facing and back facing camera of a mobile device, check the device developer documentation to see if it is possible. Having 2 cameras on a device does not mean you can have access to it at the same time as a developer.

Check out the SDK and API documentation for the functionality you need. A device might have a capability that you want to use, but sometimes the developer of the SDK or API makes a decision to not enable it for external use.

Another reason an API might not be available to you might be because the product team did not have a chance to make it available. If that is the case, you might be able to find the product road map. If the API or functionality will be available soon, you can sign up to be a beta user to get access to it earlier.