3 ms·
I was considering getting into HoloLens development a few years ago. It seemed like they were still pushing developers toward UWP even when UWP was obviously ne
by ripley12 4y ago
I was considering getting into HoloLens development a few years ago. It seemed like they were still pushing developers toward UWP even when UWP was obviously nearly dead, and that killed any interest I had.
Did the developer story for HoloLens ever get better or did it just die a slow death?
- N1ckFG 4y agoHoloLens 2 switched to <strike>Android</strike> ARM and UWP apps running on heavily modified Android, but imo the insistence on hand tracking as the primary interface still walled it off from the other Android XR developer communities.
- wucaworld 4y agoHoloLens 2 did not switch to Android. I have one and it is uwp and unity/unreal.
- ripley12 4y ago> running on heavily modified Android What? No it doesn't, HoloLens 2 runs "Windows Holographic" which is based on Windows Core OS.
- N1ckFG 4y agoYeah y'all are right, I can't find anything to support the notion the HoloLens 2 uses an Android fork for its OS. (Possibly the person who told me this had it confused with Magic Leap...?)
- pjmlp 4y agoIt focused on using Unity, and MRTK is based on Win32 and Khronos XR standard. The problem with Project Reunion (nowadays known as WinAppSDK + WinUI 3.0), is that it is clearly managed by people without big background on Microsoft UI stacks (watch a couple of community calls), and it is years away to achived parity to UWP, let alone what Windows Forms and WPF offer in API surface.