Assumptions
This is a list of all our assumptions. Some of them will be valid, some won’t. It’s important to know which one need to be valid for us to succeed, and how can we validate them.
That will also allow me to prioritize research to validate the most pressing ones.
Assumption | Confidence (Scale 0-5, 0 is bad) | How do we validate? | Risk if not valid |
|---|---|---|---|
People will buy XR headsets | 5 | - Market share data | Our market will be small, our growth will be slow. |
Devs will build content for XR | 4 | - Growth of webXR app marketplaces? | Our market will be small, our growth will be slow. |
Devs will build apps that are not games | 4 | - find people building apps for quest / VP | Our product would not be relevant. |
Devs will want better tools than Unreal or Unity to build spatial apps | ??? | - User interviews | Our product would not be relevant. |
Devs would prefer to spend hours in headset while building their app | 3 | - Ethnographic study? | The in-headset app development part of our product will be irrelevant |
Devs will want to debug in headset for periods of time (30 min) | 4 | - Ethnographic study? | The code-writing part of our product will be irrelevant |
Devs will be OK to forgo VIM, VSCode, Github Copilot, etc to use our editor | - Ethnographic study? | The code-writing part of our product will be irrelevant | |
Creators will be OK to forgo VIM, VSCode, Github Copilot, etc to use our editor | |||
Devs will find a bluetooth keyboard + phone + XR headset a sufficient to work away from home | - Ethnographic study? | Our marketing positioning of “build anywhere” will not resonate | |
Devs will be OK to forgo Git for source management, and go with something like what WebFlow has | 0 | ||
Devs are OK learning a new framework to build web apps, alongside Svelte, React, etc. | - Survey? | MR.js will not be the right foundation to build the editor on | |
Enough devs care about fully standard web components, and an open source library | - compare with other similar projects | Things like React XR would become defacto tools and the editor will have to support it. | |
A community will be formed around MR.js | - no idea yet | The MR.js framework will only be built by employees, which will put us behind faster moving frameworks | |
Teams will not use our product because they will not have direct access to the codebase outside of our platform (ie not having vercel style of github actions etc) | |||
Users want version controlling (backups) | 5 | -wait for them to screw up | |
We can be capitalistic without being evil | 3 |