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.
Should the HoloToolkit-Unity primarily focus on the HoloLens Platform?
Cross Platform support is nice, but should the HoloToolkit-Unity primarily focus on the HoloLens platform, or should we have a separate branch or project that supports only communication to/from the HoloLens as HoloToolkit companion applications?
I suppose the main HoloToolkit project addresses this, but this is more directed to Unity based HoloLens projects.
One alternative is that we can have a specific .unitypackage that includes just the basics for cross platforms apps to communicate with HoloLens apps that only includes bare necessities like the sharing SDK.
Because of the drastic differences in input systems, UI layouts, and capabilities, I don't really see why the HoloToolkit-Unity master branch should have cross platform support.
Microsoft HoloLens Agency Readiness Program
Virtual Solutions Developer at Saab