Overview
A visitor centre might start with a 3D object that people explore before arriving, then offer an AR explanation beside the object at the venue. Each route needs a clear purpose and a text alternative for essential information. The commissioning team selects and tests the routes its audience needs.
Choose a format for the audience's task
Extended reality, or XR, covers experiences including virtual, augmented and mixed reality. These formats differ in how they relate to the physical setting and how people interact with them. AR and MR terminology can overlap, so describe the behaviour you need: what will the user see, what can they change, and does their position affect the task? 1
| Audience task | An option to test |
|---|---|
| Watch an explanation or turn an object to inspect its shape | Video or a 3D viewer on a screen |
| Explore a photographed setting from selected positions | A 360 tour with readable information |
| Perform an activity inside a digital environment | VR with movement and interaction suited to the activity |
| Read an explanation tied to a physical object or location | AR with a defined reference and display method |
| Interact with digital elements in relation to the room | An MR application tested for the required spatial behaviour |
Test the proposed option on the audience's devices and in representative conditions. Access and input methods should work for the intended users, with another way to reach essential information when the experience is unavailable to them. 2
Decide whether one route is enough
Start with a task whose success you can describe. A visitor may only need a phone viewer to understand an object's shape. On-site AR becomes a separate option when it explains a detail in context or a relationship that the visitor needs to see at that location.
When considering AR and VR services together, identify the purpose of the virtual environment. It might let visitors explore a space they cannot enter, provided approved content exists for it. Give each route its own output and acceptance test, then test the additional route before extending it to more venues.
Describe the transition between routes. Does the visitor open another link, or must the next experience receive their language choice, activity result or account details? The development and operating work depends on what must carry forward. Sharing a 3D model does not establish a transfer of user data.
Applications and useful measures
Culture and tourism
A project can explain a detail of a collection object or a building's relationship to its surroundings. The collection owner approves the interpretation, names and visual references. Ask visitors to explain the intended detail afterwards. For the visitor-centre example, assess whether the on-site route adds understanding beyond the material seen before arrival.
Education and training
Select an approved teaching procedure and compare its presentation on a screen with another format where there is a reason to do so. Specify the steps learners should perform and the errors the instructor will record. The organization's specialist defines the experience's role in training; completing a digital activity does not establish competence to perform sensitive work.
Engineering and property
A model may support discussion of component relationships or spatial layouts. Identify the approved reference version and its owner, and document how the model may be used in a review. Where a task involves measurement or an engineering decision, the responsible specialist defines the reference, required accuracy and verification method.
Exhibitions and marketing
An experience can present two product or configuration options in a context visitors understand. Test whether they can explain the intended difference, and record session time and assistance. For a staffed exhibition, screen placement, the queue and device handover between visitors belong in the operating trial.
Prepare content and shared assets
Inventory the available models, photographs, drawings, text and audio. Identify ownership, permitted uses and the version the project will approve. Where dimensions affect the interpretation, record their reference and review them with the relevant specialist.
A reference asset can supply different outputs. A phone viewer may need a smaller file, while another route may require separate model parts or different controls. Check reuse rights and each output's requirements before assuming savings from a shared asset.
For the visitor centre, approve the object model and interpretation first. Review both the browser and AR versions against that reference. The version record should identify what they share and which outputs need updating when information changes.
Test Arabic in the actual display: text direction, label length, names, units and audio timing. Review the English version for meaning, terminology and interaction instructions. Assign responsibility for content approval and for checking how it appears and works on the required devices.
Define implementation requirements and compatibility
Record each route's device, operating system or browser version, application build, input method, connection needs and permission-dependent features. Include venue conditions where the experience uses a camera, movement or spatial relationships.
OpenXR provides common interfaces for XR development on supporting configurations. WebXR describes interfaces for access to VR and AR capabilities on the web and is a W3C Candidate Recommendation Draft. Using either interface does not replace feature testing on the intended device, browser and runtime. 3 4
| Scope item | What to specify before development |
|---|---|
| Shared content | Reference asset, rights and outputs for each route |
| A transition between routes | Entry point and what the user sees next |
| Data exchange | Fields, interface, permissions and reason for transfer |
| Lost connection | Functions available locally, interruptions and recovery |
| Permission refusal or unsupported device | A clear alternative for essential information |
If the project needs accounts, progress or measurement results to move between systems, define the integration and failure behaviour explicitly. Offline operation applies only to the functions designed and tested for it.
An external study comparing formats
Eiris and colleagues: two desktop training formats
A 2020 study compared a 360 panorama with static VR on desktop for construction hazard identification among students and professionals. Average identification scores were higher in the VR condition. Students rated the panorama as more realistic; professionals reported no realism difference. These findings concern that desktop experiment. 5
For a Saudi training centre, an instructor could approve one teaching scene and the items learners should identify, then compare two formats on the same task. Record correct selections and assistance for each audience group. This provides a local basis for choosing a format without assuming the study's result will recur or that the scene replaces approved training procedures.
Test the investment before expanding
Document the current way of performing the task. Choose limited content and representative users, then agree what the prototype will measure: understanding an explanation, completing a step or identifying an item. Record errors and assistance as well.
For the visitor centre, test the object viewer first if it meets the basic need. Then assess the visit with the on-site explanation added, including setup time and operator workload. The expansion decision needs evidence about the visitor and the venue's ability to run the experience.
Agree continuation and revision criteria before the trial. Keep a record of the device, content version and conditions. If the second route adds no required benefit, the first can remain the delivery scope. Address content or access problems before repeating them across venues.
Extended reality cost and comparable proposals
Marafei prices projects according to the requested scope. Ask extended reality providers to quote for the same task and separate shared work, route-specific delivery and operating commitments. The number of technologies in a proposal is not enough to compare value.
| Cost group | Items to define where applicable |
|---|---|
| Shared preparation | Task assessment, content review, reference asset production and rights |
| Each delivery route | Interaction, asset preparation, localization, testing and release |
| Integration | Interfaces, permissions, error handling and data checks |
| Equipment and operation | Devices, licences, hosting, operator training and agreed updates |
The visitor centre could request a browser viewer as the base scope and price AR as an optional extension with its own task and tests. State the number of objects, venues and languages, and which devices the client will supply. Agree review rounds, content approval dates and access to the venue for testing; these affect the delivery plan.
Prepare the brief with the audience task, available materials and rights, venues, target date, alternatives to compare and approval owners. Ask what the price includes, which costs recur after launch and how scope changes will be handled. Use those details to compare proposals for extended reality development services.
Delivery stages and outputs
- Define the audience task and acceptance criteria with the project owner.
- Compare formats and record why each proposed route is needed.
- Build a limited prototype to test the assumption that most affects the decision, such as understanding a detail or opening the experience at the venue.
- Approve the trial result, production scope, reference asset and version plan.
- Develop each route and review content and interaction on the agreed operating configurations.
- Test the routes separately, their transition and alternatives when access fails.
- Hand over the agreed outputs, operating instructions, test record and update and support responsibilities.
A phased release can be agreed when the first route is ready and performs its intended function. Record each route's status and dependencies, including content approval, integration or venue preparation still required.
Accept the delivery and assess the user task
Acceptance covers both operation and the intended audience outcome. Opening content on the specified device is a technical result. A visitor's ability to explain the intended detail requires a separate user assessment.
For each test, record the device, build, language, venue, result and approval owner. Check the pre-visit content and on-site explanation separately, then the transition. Include the alternative route when a visitor declines camera permission or a device cannot run the experience. 2
Describe what the visitor should see and do, what counts as correct completion and where operator assistance is needed. Agree acceptance thresholds before testing, and record issues and retest results. Visit counts alone do not establish understanding or task completion.
Operation, updates and accessible alternatives
Assign an operator for each route and an approval owner for shared content. When text or a model changes, use the version record to identify affected outputs and retest the changed parts and their dependencies before release.
Discuss licences, hosting, administration accounts and support in the proposal. Operators need to know how to start and end a session and what to do when equipment or a dependent platform is unavailable. Handover documents should state maintenance responsibility and any agreed support scope and term.
Review camera use, spatial maps, accounts and measurement data where applicable. Define the necessary data, who processes or accesses it, what is retained and for how long, and refer those decisions to the organization's data owner. Data exchange between routes is not required for every project.
Provide a clear exit or stop option, readable essential information and alternative audio or input methods suited to the audience. Test these alongside the experience. W3C's accessibility user requirements can guide that review; they do not certify a project's compliance. 2
Scope your project with Marafei
Marafei plans and delivers experiences using VR, AR or MR individually or together within an agreed scope. The discussion starts with your audience's task, available content and operating environment, then defines what will be produced, tested and handed over.
For an extended reality project in Saudi Arabia, specify the city, venue, languages, audience and target opening date, along with available equipment and materials. A project in Riyadh, for example, needs its own venue-access and operating arrangements confirmed in the proposal. Geographic coverage, equipment and delivery dates require agreement for the project.
Send a description of the first task you want to test and identify who will approve content and delivery. Use that information to define the initial scope and compare options, including the cost of expansion where needed.
Discuss your extended reality project.
