wormhoudt

Love this. Unfortunately it doesn't work for us. The DCR endpoint at /oauth/register rejects redirect URIs from custom domains — only claude.com, chatgpt.com, and localhost are accepted. So our self-hosted LibreChat cant connect. Fingers crossed this is just a short term issue.

I will say that we at Dream, hold a pretty contrarian point of view on this. So let me start by saying, it is an opinion, but one we hold pretty strongly. I can talk a little bit about locomotion, but this sort of philosophy applies to many of the design decisions we made, for better or worse.

Dream doesn't allow for locomotion by design. Dream is meant to be a place where people meet to be productive. The environments are intentionally pretty but not distracting. The focus is on interaction with the other participants and the shared content. We feel that removing locomotion and reducing dimensionality is how we will make the interactions with Dream simpler, especially for new users. Mechanisms like teleportation are super fun and certainly add to immersion and are the right choice for all sorts of VR experiences. However, Dream has been built from the perspective that users are here to collaborate and then go back to real life. In that context, something like teleportation is fun and novel the first time you use it, but the 10th time, we feel like most users would just prefer a menu. The overall idea being, reduce dimensionality to increase precision and simplicity.

I'm happy to hear a critique of this philosophy. Ultimately we have to create software people love to use, and we certainly understand that we might be proven wrong about this.

We were definitely anticipating the movie. We saw it as a team. We had hoped it would do more for general recognition and understanding of VR, but I think that was not the effect. Obviously that was in no way the job of the filmmakers. They are there to make an entertaining movie, not advance the adoption of VR.

I will say though, the book itself was a big part of me personally deciding to get into this project after I left my last one.

I don't take this as overly critical. We need and welcome feedback.

Looking at layers for text is something we will definitely do. We are happy with SDF text in our UI, but text inside of Chromium is miles from acceptable and will continue to be a focus.

As far as scalable and user positional UI, we currently hold the opinion that it doesn't offer enough value to compensate for the complication that it introduces, especially for novice users. At the same time, we realize that is a contrarian point of view and user frustration may force us to change it. We have to remain open to changing opinions like these.

Hey! I'm Doug, one of the founders of Dream.

Thanks for taking the time to leave detailed feedback like this. We need as much of it as we can get.

A few of your points come down to discoverability / help. You are correct. We agree that before the app comes out of early access we have to drastically increase that. Once we understand that the core functionality is serving its intended purpose, we will turn our attention to onboarding, help and discoverability.

It's also fair to point out that pixel density in the headsets aren't really great yet. We are of the opinion that legibility will be a problem that solves itself in the near future. User frustration might force us to reconsider that opinion sooner rather than later.

Lastly, with regard to the position of UI, it is something we have worked on quite a bit and there is still plenty of room for it to get better. We have shied away from infinitely adjustable UI size and positioning and instead tried to make something that positions itself automatically. Right now, the UI positions itself based on where your head and hands are and how long we think your arms are. The implementation is pretty naive and we intend to improve it over time. This might be another area where we have to get more mechanical to decrease frustration.