Overview
A pilot might ask one trainee to select a virtual component and another to check the choice before the facilitator releases the next step. The first deliverable is a limited session that tests this dependency and can be reset for the next group.
When the task needs a shared session
Start with what the group must accomplish. Parallel individual sessions may be enough when everyone can meet the objective independently. A guided display may suit a single explanation for the whole audience. Test multi-user virtual reality when a participant needs a colleague's decision, change or feedback to continue.
| Activity format | A question to test its suitability |
|---|---|
| Watching together | Can the audience understand the material without changing the scene? |
| Parallel individual VR | Can each person complete the objective independently? |
| A shared session | Does one person's action affect another's work, and can they coordinate it? |
Compare formats on the same task before expanding the scenario or purchasing equipment. In the component-selection pilot, observe whether the reviewer has a necessary contribution and knows when and what to confirm. Base the choice of format on what the participants need from each other.
Shared virtual reality use cases
Team training
An approved procedure can assign execution to one trainee and review to another, while an instructor observes the handoff. The instructor defines correct completion, records errors and checks whether the group can proceed without help. Professional competence remains subject to the organization's training and assessment process.
Education
A team might build a virtual model and explain what each student added or reviewed. Give each role an observable contribution so that one person does not simply watch while another completes the activity. The teacher reviews the exercise against its learning objective.
Museums and visitor centres
A guide can lead a group through approved material or a virtual exhibit. Test whether participants can find and interpret the intended detail, and whether the guide can direct attention and manage transitions. Consider a captured virtual tour when the task is simply to view an existing place.
Exhibitions and experience venues
Visitors might make a collective choice that changes the scene. Test whether roles and entry instructions are clear, then observe the group leaving and the operator preparing another session. Include briefing, waiting and staff intervention in the operating trial.
Design review
One person can propose a model change for another to inspect and confirm. The responsible specialist approves the source version, editing permissions and decision record. A model's presence in VR does not establish engineering accuracy or suitability for construction.
Design roles, permissions and communication
Specify what each person can do and what they see as a result. The component-selection pilot could use these agreed roles:
| Role | Action to define and test |
|---|---|
| Operator of the task | Selects a component and sees that review is pending |
| Reviewer | Sees the same choice and confirms it or requests a change |
| Facilitator | Checks completion, releases the next step and pauses the session when needed |
| Observer, if included | Sees assigned information without editing permission |
Test two people selecting the same item, a participant leaving before confirmation and a late arrival. The interface should make control ownership and the current decision status clear.
Review Arabic role labels and entry instructions inside the headset, then the English version where required. If a step depends on an audio cue, evaluate a visual signal or short text that can serve the same purpose for the intended audience. 3
Choose the venue model and session capacity
Consider a shared physical area, separated stations at one venue or participants at different sites. Each changes movement, supervision and connectivity requirements. Meta's documentation describes group formation and a shared spatial reference for aligning users' coordinate frames on its platform. This is a technical example, not a platform commitment for your project. 1
Keep three measures separate: people in one session, sessions running at the same time and visitors served per hour. A successful limited session does not demonstrate a venue's ability to handle successive groups throughout an event.
Observe the full cycle of briefing, fitting, activity, exit and reset. Record stations, staffing and bottlenecks, then use the observed cycle to estimate throughput and verify it in a venue trial. Approve the count and space for the tested configuration; the service name does not imply a standard capacity.
Devices, connectivity and shared state
Record the headset and controller, operating system or runtime, application build, venue, network and target count. Define the state that must agree across devices: roles, the selected item, the confirmed step and the outcome that allows the task to continue.
In the component trial, the first participant makes a choice and the second verifies the correct state. Test simultaneous actions and agree how conflicts are resolved. Assess update timing against the task's needs without promising a response time before testing.
Check invitations, role assignment and late entry. For an interruption, define what the group sees and when it pauses, and whether the user returns to the last approved state or another starting point. Test that behaviour with the facilitator at the intended count and configuration.
Scope voice, hosting and connections between sites explicitly. After the connection returns, inspect the state on each device to verify recovery, then run a fresh session.
Movement, accessibility and session data
Have the venue operator review the activity area, obstacles, entry, exit, waiting and intervention when tracking is lost or someone leaves. Meta's guidance for shared activity spaces addresses movement and entry or exit, including pausing the shared experience when a user leaves to allow safe exit and re-entry. Apply relevant guidance alongside device instructions and the venue's procedures. 2
Evaluate seated participation, a screen-based contribution or an observer role where it serves the task. Users need a clear way to stop and an appropriate alternative for essential information. W3C's accessibility user requirements can guide that review; they are not a compliance certificate. 3
List only the names, voice, movement and session measurements the design uses. Distinguish processing during operation from recording, storage or spectator display. The organization's data owner reviews purpose, access, retention and required notices before those functions are approved.
Two research examples and local pilots
Stanford Virtual People: shared learning activities
Stanford documents 263 students across two courses in 2021, with activities including group discussions and virtual world-building. The number describes participation across the courses, not concurrent session capacity or evidence by itself of improved learning. 4
A Saudi university could test a short activity with Arabic onboarding and separate model-building and review roles. The teacher records each role's contribution and asks the group to explain its change. Use that assessment to choose the activity format without assuming an unreported learning outcome from the original case.
TeamPortal: sharing a collaborator's perspective
Two studies reported in the 2025 TeamPortal paper involved 72 participants in 36 pairs overall. In the first study's complex task, TeamPortal produced higher accuracy than ShaView and the baseline, alongside higher reported physical demand than both. The results concern the studied task and configuration. 5
A Saudi training centre could compare an audio cue with a shared view during a component-selection handoff. Record correct choices, clarification requests and reported effort before deciding whether the additional view serves the task. These are external examples, not Marafei project references.
Shared virtual reality cost and comparable proposals
Pricing depends on the project scope. Give each shared virtual reality company the same task, roles, count and venue, and ask what its pilot will deliver and test before expansion.
| Proposal item | What to specify |
|---|---|
| Scenario and assets | Steps, roles, scenes, languages, content rights and review rounds |
| Shared interaction | Permissions, shared state, conflicts, entry and recovery |
| Configuration and venue | Equipment, network, space, setup and client-supplied inputs |
| Testing and handover | Target count, acceptance cases, operator instructions and agreed training |
| Recurring costs | Hosting, licences, support and updates where applicable |
Request a pilot for one group with a separate expansion price for more devices or sites. The expansion option should identify the testing and operating work it requires. Separate initial development from event operation and state who supplies equipment and staff.
Prepare the brief with the task, each role's contribution, target concurrency and parallel sessions, layout and connectivity, assets, equipment and dates. Name the operating and acceptance owners. Site access, content approval and review rounds affect the delivery plan and should be discussed before fixing the schedule.
From an interaction prototype to the venue trial
- The content owner approves the task, roles and correct completion.
- A limited interaction, such as selecting and confirming a component, tests whether participants need each other and understand the handoff.
- A facilitator and representative users try the session while the team records errors and assistance.
- The team reviews scope before producing the remaining content and approves changes and expansion tests.
- The build is tested on the agreed equipment, network, venue and count, including interruption and reset.
- Agreed outputs, operating instructions, configuration records and acceptance responsibilities are handed over.
Use the early prototype to test the dependency most likely to disrupt the task. That might be transferring control to a colleague or restoring a participant while the group awaits their confirmation. Define continuation and acceptance criteria before the trial.
Acceptance and evidence of collaboration
Run a complete cycle: participants enter in their assigned roles, one selects the component, the other sees and confirms it, and the facilitator releases the next step. Test a controlled interruption under the operator's plan, followed by the agreed recovery or restart. Finally, reset for a new group.
| Acceptance case | Result to record |
|---|---|
| Entry and role assignment | Each user arrives with the correct permissions |
| State change and confirmation | Devices agree on the choice and approved step |
| Conflict or late entry | Behaviour matches the approved design |
| Interruption and recovery | Group state, returning user's state and facilitator action |
| Reset | The next group starts without state left by the previous session |
Attach the build, device, count, venue, network and approval owner to each record. Agree thresholds, exceptions and retesting after fixes.
To assess teamwork, observe each role's contribution, correct handoffs, errors, help requests and task completion. Connectivity and synchronization are technical checks; the value of the partner's participation needs this separate assessment.
Session management, updates and support
Assign responsibility for equipment preparation, briefing, queues, starting, pausing, restoring and resetting sessions. Operators need to know when to handle a problem themselves, when to escalate it and what the group can do during an interruption.
Define the delivered build, tested configurations, operating procedures, asset rights, administration access and update ownership. Agree support hours, response times, staffing and training explicitly where the project needs them.
When a device, network, venue or scenario changes, review its effect on roles, synchronization, movement and recovery. Run a complete cycle before admitting a group on the changed setup and record the approved version.
Scope your shared VR project with Marafei
Marafei's shared virtual reality services cover a multi-participant experience under an agreed scenario and interaction model. Start with the group's task, target count, roles, venue and available devices, then define operation and acceptance outputs.
For a project in Saudi Arabia, specify the city, instruction languages, venue conditions and who will run sessions. A Riyadh project, for example, needs venue, connection and supervision arrangements confirmed in its proposal. The service name does not establish geographic coverage or availability to book an existing experience.
Send the step that requires participants to cooperate, together with the target count, venue, timing and task approval owner. Discuss your shared VR project.
