Open Beta

Post about the current Open Beta. Post logs to Gist/Pastebin! One item per post!
Non-constructive and off-topic posts will be moved or deleted.
[1984] New Instance UI Design Rework
I want to start off by saying that I really like the attempt at what the new UI changes are going for overall. Giving users more power to add information to their instances is a good thing. However, in its current state in the beta, things didn't land too well with the "Create New Instance" UI. Let's look at the old UI first to discern what's going on. In the old UI flow, the user is prompted to choose their instance type and region, they were then taken to a second menu where they could choose the instance name and drop a portal or join directly. It's important we keep this common functionality easy to access and make sure we are improving it when we add new features or move something around. The most important thing in this rework mockup is user flow. We want the users to be able to quickly get things done and a world made. The main "overview" should be enough for the user to take in all of the important information about the instance at a glance and then they can go deeper if they choose something that needs to be changed. More detail-oriented users will go and add extra information for their meetups and events but the average user just wants to create a world and go. Think about the 99% of the time that you are making a new instance, what are you changing? The first thing we can do is eliminate the scroll bar. While scrolling is a good way to show more information, it's a pain for fast menuing, especially whilst in VR so we want to reduce the amount of scrolling a user has to do. With this, the UI will also become a lot more digestible to view all information about your instance at a glance. Particularly the “save these settings” and “drop as a friends only portal” checkboxes are now a lot more visible to a user so they know the options are actually there. With the current beta UI, those settings really fall through the cracks as you have to scroll all the way to the bottom to find them. Also putting them next to one another instead of stacking them reduces the amount of wasted space. Flipping the join and drop portal buttons around is also a must as it’s currently backwards in the open beta which is a regression. (It also maps nicely putting the place portal for friends only right above the drop portal button) Putting things behind a minimal amount of submenus should be more than enough for a comprehensive design. Beyond this we want to communicate the actively selected options in the user directly from the main "overview" menu instead of just descriptions. This can effectively communicate what is within these menus whilst also allowing users to skip over them if things are already configured to their liking. The best way to do this in this new UI flow is probably with the chips being used in many places already. It's important that we keep Instance Type and Region accessible in the updated UI as these are likely the two most common things changed by the average user. You want to be able to easily change where the instance is hosted each time you create a new one so people can have the best possible ping. Having it pushed into the "Advanced Options" that most of the time will have nothing else in it doesn't particularly make sense so we're going to move it out of there and have it stand on its own. All of the other options are exclusive to the group instance flow so we're going to keep them with that. On the topic of group instances, the flow of making them now needing the "who's hosting" to be changed has more friction than the original UI. This is directly linked with group instances and has no real reason being a separate option. Moving it back into the to be with group instance permissions would make more sense as it's what users would expect and are already used to. We're going to be pretty much entirely reverting back to the old functionality on this front but making some important changes to reduce the amount of menus people have to switch back and forth between. Group Instance Flow now looks similar with a cleaner UI. You select the instance type as group. You go into a submenu where you choose the represented group, the group type (group, group+, group public) and then the related group instance only permissions. Once users are done selecting these options, they will have a “confirm” button to bring them back to the “overview” page. This “confirm” button change is important as it skips having to go back to the instance types menu and just brings the users straight to the “overview”. This allows them to see their group details and settings chosen as little chips in the “instance type” section and also look at the world details and region set to make sure that everything looks correct before creating the instance. Now onto the new additional world details. This is all going to be compressed into a single widget in the overview panel that shows the user, the instance name, a truncated description and chips for any other information. This allows the user making the world to see all of the most important information at a glance without having to go into a menu to edit any of it. It compresses it all so that it fits on one page that does not need to be scrolled through. While this information is helpful to let your friends know what the instance is about, using your saved settings is going to work for the majority of the time so you only actually need to edit the information for when you’re hosting an event or gathering. In terms of the titles for everything. I understand the attempt that is being made with the who, what, when, where to be more friendly and appealing to users. However this just makes the UI feel more cluttered and repetitive. If I’m going through a details or settings menu I just want a direct description of what each thing is. This is why all of the titles are being reverted/changed in this mockup. It makes it a whole lot more readable at a glance. See the images below on how all of these changes come together. Users can at a glance see all of the important information about their instance and easily click into a section to edit it. The example instance here is a Group Public with queuing, 18+ Verified accounts only, and medium performance avatars or better. We can see the name of the instance, a short description of the event and the tags for what the vibes are. The region is easily selected and now we can create the instance or drop a portal. Apologies for such a long writeup about this whole UI situation but it becomes a lot more complex than it seems at a glance. I hope my in depth explanation and reasoning gives more insight to what needs to be changed and why. While I think the mockup below is the best visual example I can give, I hope whoever is working on the UI can take a look at it in addition to all of the explanation and use the understanding of why each change “works” to make something that actually gets shipped. P.S. VRChat plz hire me for UI/UX….. jkjk…. unless?
5
·
Feature Requests
[1948] New world creation UI is cluttered
Having created several new instances already I have to say the new create instance UI is, well, terrible. It's a great example of the traditional engineer UI. Contrast is bad. This isn't an assistance thing, it's a help the brain recognize where the divisions are. The existing menus have good contrast making the buttons obvious. The new one, the difference is much less distinct meaning it's slower to scan. General clutter (with two possible ideas, but there are others. "Who's hosting" and "Who can join" are tied together in an unexpected way - you need to change who's hosting to change the "Who can join" to group. "Category" / "What's it about" / "What's the vibe" are all conveying a very similar concept - the social content of the instance. - Category is the very approximate grouping - What's the vibe is a more specific, but still select from a list - What's it about is a highly detailed version. So we're providing the same information in three different ways from very rough to very fine. There is some use here, but the way it's presented is clutter, and Vibe is functionally a sub category (from a user pov), so having vibe immediately after "Category" would make sense I'd be inclined to: Move "Vibe" immediately after "Category", and change it to a single line (Though this is different from anywhere else on this page). I'd do the same thing to language and put it on a single line as well: Category: CatA CatB CatC ... Vibe: Vibe1 Vibe2 Add+ Language: Any I'd move "What's it about" to "Advanced Options" and default it to blank. There's no reason to repeat the world description which is already visible on the instance page (are you planning on removing it?) "Drop Portal" and "Create & Join" feel reversed. This may just be due to knowing the locations before, but I think swapping would be good. Already a canny on this one: https://feedback.vrchat.com/open-beta/p/1948-please-swap-the-positions-of-the-join-and-place-portal-buttons "Drop Portal" and "Create & Join" have more visual contrast, than anything else on the page, but "Drop Portal" could still have a little more. Having to scroll is a poor experience, though even with condensing it that may not be possible to avoid. But condensing it would help. Now, for #2 I have two potential ideas and putting them down here for the tl;dr aspect. I also realize these are not the only solutions: 2a. Adjust the display such that "Who can join" is visually dependent on "Who's hosting". Perhaps put the two in a box and indent the "Who can join", which then shows they're tied together. 2b. Remove "Who's hosting", add "Group ▲" (expand arrow) to "Who can join", where it then brings up the Select group -> Instance type (the new group type menu is fine here). In this situation, once a group is selected we could add the following to the "Who can join" menu: Public Friends+ Friends Group ▼ My Group Group / Group+ / Group Public / [Role] Invite+ Invite With this, selecting "My Group" would let you change the group and perms, and the "Group / Group+ / Group Public / [Role]" line would let you keep the group but change the perms.
2
·
Feature Requests
Load More
→