Suppose you're a VR app and you invoke a picker to open a... I don't know... you want to open a sound file. How should the picker's UI be to fit into your general VR interface?
If a sound file is particularly badly suited, then some other kind of file (but in that case I'm interested in why that's easier/better than sound).
Not sure I understand the question exactly. Generally, a file picker UI could look exactly the same in VR as it does out of VR, just projected on a flat surface.
The crucial point is to remain inside the stereoscopic VR view since exiting VR is very disruptive.
Boxes and drawers. A sound file could be in a collection of records or CDs or tapes. Making it just like real life is like having your users start off with the manual already read.
I’m afraid a general Android VR item picker will be a lot more boring though.
Rather older versions of Macs! With binders where you put files into, and dragging items around, and most of the applications being items on an office desk.
Nowadays I guess the surface studio is a good example. Being laid out like a drawing table and interacting with it like a drawing table.
Any chance this PoC file browser is open source and available? I've been looking at these changes and I'm not sure how I should handle discovery of new devices, e.g. insertion of a new SD card, or an OTG USB device.
This is not a good thing for VR apps. Unless there's a VR system file picker in the works that I'm unaware of..