search

Hubs-Foundation / hubs

Duck-themed multi-user virtual spaces in WebVR. Built with A-Frame.
https://hubsfoundation.org
Mozilla Public License 2.0
2.14k stars 1.41k forks source link

Discoverability and usability of in-world functionality #3128

Open misslivirose opened 4 years ago

misslivirose commented 4 years ago

Is your feature request related to a problem? Please describe. There are features in Hubs that are only surfaced when a certain criteria is met. Examples of these are waypoints (which only appear when you are in 'pause mode') and media frames, which only appear when you are holding media. There are also shortcuts like 'inspect' mode, which happens when you right-click an object or avatar. However, these features are not always discoverable, and may have additional context that we might want to surface (e.g. if you hover over an avatar in pause mode, you can change their audio level)

Describe the solution you'd like We should have an exploration into how these features can be consolidated, surfaced, and taught to new users. The 2D UI redesign may give us additional places where we could surface or change these interactions.

This also relates back to #3110 and the other ways that we showcase information about an in-room element (in the case of 3110, avatars and avatar menus). There is an inconsistency where avatars do not have a hover effect and there is no menu in regular mode, while other objects do have a hover effect and menu in pause mode, and some objects have a hover effect and controls in regular and pause modes.

Example Detail
Hovering on an avatar image
Hovering on an object - standard image
Hovering on an object with additional controls (standard) image
Hovering on an avatar - pause image
Hovering on an object - pause image
Hovering on an object with additional controls (standard) image

Additional context Our current interactions are grounded in our earlier desire to keep the interactions in 2D and VR similar. The new redesign will likely grant additional affordances to interact with in-world content through a 2D UI instead of a 3D UI for those devices.

We have a reasonable ability to detect what device that a user may be on (e.g. if they are on desktop, mobile, or VR). Therefore, different devices could have different defaults. Users may also want to set preferences for how things appear in the room.

┆Issue is synchronized with this Jira Task

misslivirose commented 4 years ago

CC @mbransn - following up from our product design meeting today to explore in more detail down the road. Especially worth considering when we are able to test with the new 2D UI.

misslivirose commented 3 years ago

Understanding how to trigger these menus (and if they should even live in 3D) is also an open question. Our current functionality (tab/space) will need to change for keyboard navigation and screen reader functionality, which is something we will be tackling more explicitly in the redesign. Additional conversational context from a Discord conversation can be found here.

djay commented 3 years ago

I think it particular for presentations its really import to surface inspect mode as without it you can't hold a presentation properly https://github.com/mozilla/hubs/issues/3720