The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Questions and Doubts in HoloLens Development: "Creating an Idea"
Here I'm not going to dive deeply into some technical details which refer to problems during the process of HoloLens development. So let's talk about the right way "How to Create an Idea for this cool device".
Recently, I've found a great post about envisioning, prototyping and building HoloLens applications from AfterNow company's view. The name of it is: "Case study - AfterNow's process - envisioning, prototyping, building" (you will be able to find the link further). So what do you think about this one? As for me, that article is very clear and useful but except one thing (I've highilighted that one on the image below):
Now, with my team I'm gathering different ways what we can actually do and implement for HoloLens based on our skills. So we wanted to use all advices from that article (developer.microsoft.com/en-us/windows/mixed-reality/case_study_-afternow%27s_process-_envisioning,_prototyping,_building) which I've mentioned later. But I couldn't understand the approach to the "flow map". Who has already made something like this? Can someone explain from what does this process consist of in more deatils?
Thank you in advance,