1. REPOSITORY
1.1. gitlab
2. Goal
2.1. 3 different platforms
2.1.1. VR Content Creation
2.1.1.1. Front End for Mobile capture device
2.1.1.1.1. Is this an internal-only tool or is this a public tool for everyone to be able make a VR experience of their home?
2.1.1.1.2. THETA RICOH PLUS (360 camera) link these images together
2.1.2. Dashboard / Back office for Realtors
2.1.2.1. ?
2.1.3. Front End
2.1.3.1. Web
2.1.3.1.1. See above discussion
2.1.3.2. Mobile experience
2.1.3.2.1. Will it be for commercial use in a company based subscription?
2.1.3.2.2. Anyone can create an account
2.2. Dashboard / Back office to manage all the VR photos, sound, and information
2.2.1. This will then be on a different database where other services will be able to pull data from here
2.2.2. Creation of public API
2.2.2.1. Requirements
2.2.2.1.1. Authentication
2.2.2.1.2. Privilege to different data
2.2.2.2. Privacy Concerns
2.2.2.2.1. Who can get access to this data?
2.2.2.2.2. Does this data remain in the database forever?
2.2.2.2.3. What if data is used outside of its intended purpose?
2.2.2.2.4. How much of the data is accessible?
2.2.2.2.5. Possible solution, upon creation of the VR experience, customer/user can allow and disallow access to the data via dashboard.
3. Goal interpretation #2 internal only
3.1. All the VR creation is created in house
3.2. All the VR experiences require our devices / software bundle
3.3. Devices will be either iPhone / Samsung smart phone with custom app
3.4. Outside users will not be able to download such app
3.5. Begs the question, so where will you be showing these experiences? Who will show them to you? How will they show them to you? And will buyer require to go here to experience every time?
3.5.1. This means that buyers will not be able to go home and browse these experiences in their own time.
4. Goal interpretation #3 internal with account based subscription?
4.1. All the VR is created in house
4.2. App and Web services are available to everyone via account
4.3. accounts require subscription, therefore only the real-estate people will purchase such subscription to embed 3D VR into their website, and have access to an app that will have their logo/brand image upon login.
4.3.1. What if only 1 business buys such license/subscription and everyone else leeches from that business. ie. Realtor Company A purchases such service, so now they have 3DVR in their website. Realtor Company B,C,D and E access their website for the 3DVR experience for free.
5. Server Technology
5.1. Server Side languages
5.2. Database
5.2.1. MySQL
5.3. Hosting
5.3.1. AWS
6. Web Technologies
6.1. Google's VR Viewer
6.1.1. Open Source
6.1.2. Easy to use
6.1.3. Easy to host on your own server
6.1.4. Ability to use hotspots
6.1.4.1. vrView.addHotspot('dining-room', { pitch: 30, // In degrees. Up is positive. yaw: 20, // In degrees. To the right is positive. radius: 0.05, // Radius of the circular target in meters. distance: 2 // Distance of target from camera in meters. });
6.1.4.1.1. The default center of view is at (0, 0). The pitch range is [-90,90] with positive values corresponding to up. The yaw range is [-180, 180] with positive values corresponding to the right.
6.1.4.1.2. https://s3.amazonaws.com/static.oculus.com/website/2013/05/oculus_head_model.jpg
6.2. PlayCanvas
6.2.1. https://playcanvas.com/plans
6.2.2. Supports Cardboard and Samsung Gear VR
6.3. babylon.JS
6.4. WebVR
6.5. aframe.io
6.5.1. https://aframe.io/examples/showcase/sky/
6.6. Panotour
6.6.1. Panotour Viewer
6.7. Livepano
6.7.1. (addon to Panotour, give live to virtual tours. ie. it allows videos)
6.8. ForgeJS
6.9. omnivirt
6.9.1. https://www.omnivirt.com
6.10. WondaVR
6.10.1. http://www.wondavr.com
6.11. https://roundme.com
6.12. Guy who makes lots of VR stuff
6.12.1. https://risonsimon.com/days-in-vr/