gfwilliams
commented
5 years ago There may be two parts to this - a 'backend' thing (leaderboards,user data,etc) and a front-end to make creating nice VR experiences easier, so people actually want to use it and publish:
So in the front-end I could imagine:
- Initialising WebVR/WebGL in a way that allows games to still be viewed on PCs/phones without WebVR.
- go to
https://url?webvrand have WebVR automatically initialise rather than needing another click - Simple 3D menu system, with the ability to change simple themes (eg. colour)
- A 'just works' leaderboard that pops up and handles usernames/etc
- 'just works' advert popup if we're doing that (maybe even in-game billboard ads at a later date)
- VR controller models/hands for common VR devices (maybe just one simple model initially)
- Later: avatar?
There's a bit of an issue over what you build this all with - WebGL is the lowest common denominator, but I guess THREE.js would work with THREE.js and AFrame (just not Unity) and would definitely be easiest, so it might be best to work with that.
Sounds like a lot of work but should be quite quick and if I added one or two games then it's something I'd end up building out anyway, so I might as well publish it.
Something we really want to keep in mind IMO is multiplayer. While it's likely too much to do anything at first, we want to make sure we don't implement anything in a way that would make it harder to add later.
ISNIT0
TODO: split into multiple issues: