Virtual reality Simulation Custom

Custom VR application development

Appfront builds custom VR applications for situations that are difficult, expensive or dangerous to practise in real life. Think of an emergency procedure, a machine that doesn't exist yet or a space that has yet to be built. We design the scenario, build the application for the headsets you use and make sure the results flow back into the systems you already work with. Get in touch to discuss feasibility.

What is a custom VR application?

A VR application places the user in an environment that is entirely rendered by software. Unlike augmented reality, where information is overlaid on the real world, in virtual reality everything the user sees is created. That makes it ideal for practice: you decide exactly which situation occurs, how often, and what goes wrong.

We build VR not as a demo but as a working application. That means thinking about who manages the headsets, how someone logs in, what happens to the results and how you adjust a scenario when the procedure changes. These questions determine whether a VR project is still being used after the first enthusiastic month.

Appfront builds the application as custom software and connects it to your existing environment, for example your e-learning platform, so that a VR session is simply part of a learning path rather than an isolated island.

Scenarios you manage yourself

A procedure changes. That's why we build a management environment in which steps, texts and assessment criteria can be adjusted without the application having to be released again.

Results that end up somewhere useful

Who has completed which scenario, how long it took and where it went wrong. This data goes to your own system, so that VR counts towards the training record.

Rollout on the hardware you have

We build for the headsets you use or plan to use, and arrange how devices are rolled out, updated and managed by your own IT team.

VR or AR? Where the line lies

Virtual and augmented reality are often mentioned in the same breath, but they solve different problems. The choice almost always comes down to one question: does the user need to keep seeing the real environment?

This page

Virtual reality: a created world

The user is in an environment that is entirely rendered by software. Suited to practising, simulating and experiencing something that doesn't exist yet. The user stands still in a safe space and the world comes to them.

Different page

Augmented reality: information over the real world

The user sees their own surroundings with information overlaid: instructions on a machine, a fault diagnosis, an assembly step. In that case, see industrial AR software development.

Our development process for your VR application

VR is more expensive to change than regular software, so we invest early in getting the scenario right before any 3D work begins.

1
Discovery & analysis

We establish which learning objective or process the VR should serve, who the users are, what hardware is or will be available, and which results need to be recorded. We also test whether VR really is the best format — sometimes video or a standard simulation is more effective and cheaper.

2
Design

We design the scenario step by step, with decision points, error situations and assessment criteria, and build a playable prototype early on so you can experience the idea before the environment is fully developed.

3
Build and iteration

We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.

4
Go-live & maintenance

A controlled go-live with validation and a safety net, followed by ongoing management, monitoring and further development as your procedure or learning objective changes.

What a custom VR application delivers in practice

What we build depends heavily on the goal. These are the components that come up most often.

Scenario training with assessment

A procedure that is worked through step by step, with mistakes that have consequences and an assessment afterwards based on criteria that you define yourself.

Safety and emergency situations

Situations you cannot recreate in real life: a disaster, an evacuation, a malfunction under time pressure. Repeatable as often as needed, without risk.

Space and design experience

Experience a building, space or installation before it has been built, so that clients and users can make choices based on experience rather than a floor plan.

Machine and product simulation

Practise operation and maintenance on a virtual version of a machine that cannot be taken out of production, or that has yet to be delivered.

Multiple users at once

Scenarios in which several people go through a situation together, each with their own role, so that collaboration and communication are practised too.

Management and rollout

A management environment for devices, users, scenarios and versions, so that your own team can roll out a new group or an adapted procedure.

Typical use cases in practice

VR pays off where practising in real life is expensive, dangerous or practically impossible — or where you need to experience something that does not yet exist.

Industry and engineering

Practise operating and maintaining installations without halting production, and familiarise new employees with an environment before they enter it.

Healthcare and training

Practise procedures and conversations in a safe environment, with scenarios that can be repeated as often as someone needs.

Safety and emergency services

Recreate disasters, evacuations and incidents with multiple participants, including communication and decision-making under pressure.

Construction and real estate

Let people experience a design before it is built, so that clients and users make well-founded choices about layout, materials and lighting.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology we use

For the VR application itself we work with a game engine; we build the surrounding management and reporting environment as a standard web application. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, without dependence on per-user licences.

Unity / Unreal OpenXR React / Vue management environment Node.js / Python / .NET PostgreSQL REST & webhook APIs

Why Appfront for your VR application?

Appfront builds custom software for a wide range of organisations in the Netherlands. With VR, our first question is not which headset, but what exactly needs to be practised and how you will know whether it works. Without an answer to that, a VR project becomes a demo that ends up gathering dust after three months.

We treat VR as software, not as a gimmick: version control, tests, a management environment and an integration with your existing systems. It is precisely this invisible side that determines whether the application is still being used and maintained two years from now.

On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.

Also take a look at our broader services around custom software, industrial AR and our e-learning platform. Not sure whether VR is the right fit? Get in touch — we will give you honest advice, even if the answer is no.

Security and privacy in your VR application

A VR training records who did what and how well. That is personal data, and sometimes assessments that can have employment-law consequences. Appfront builds in line with the OWASP ASVS and with the GDPR as the starting point: data minimisation, role-based access and an audit trail on who views results.

VR hardware can measure more than is needed, from gaze direction to movement patterns. We only record what the learning objective requires and document it, so your processing register is accurate and employees know where they stand.

More about our approach to security: information security policy and CVD policy.

  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access following least privilege
  • Audit trail of views and changes
  • Secrets in a secure vault, not in code
  • Documented data flows for your processing register
  • Recording only what the learning objective requires

Frequently asked questions about building a VR application

Answers to the questions we get asked most often.

When the situation to be practised is dangerous, expensive or impossible to recreate in real life, or when spatial awareness is decisive. If it is about knowledge transfer, looking up procedures or a test, a regular application or e-learning is almost always more effective and cheaper. We will tell you so even if you come to us with a VR request.

With virtual reality, everything the user sees is generated; they stand in a safe space and the world comes to them. With augmented reality, the user sees their real surroundings with information overlaid, for example instructions for a machine they are standing next to. VR is for practising and experiencing, AR is for support during the work.

We build on OpenXR, the open standard supported by the mainstream headsets. That means you are not tied to a single manufacturer. We decide together which devices to use, based on ease of management, comfort during longer use and whether users stand still or move around.

For texts, steps, decision points and assessment criteria, we build a management environment as standard, so you can change them yourself without a developer. Changing the 3D environment itself is a different matter: that requires modelling work. We discuss in advance which parts we make variable and which stay fixed, because that is one of the most important cost decisions in a VR project.

Through an integration with your learning platform or HR system, in practice often using xAPI or an API integration. That way a VR session counts towards the training record and nobody has to retype results. You decide exactly which data is passed on, which is also a privacy question.

That risk is real, and it is largely a design issue. Scenarios in which the user stands still and looks around themselves cause far fewer complaints than scenarios with artificial movement. We take this into account in the design and test early with real users, including people who are sensitive to it.

We deliver a management environment for devices, users, scenarios and versions. Updates are rolled out to headsets through the management solution that belongs to your hardware. Who grants which group access and who publishes new scenarios is set up according to your own management organisation.

There are good off-the-shelf VR trainings for general topics, and they are a fine starting point. Custom development pays off when it concerns your own procedure, your own machine or your own building, which are precisely the cases where a generic training doesn't quite resemble reality and is therefore not taken seriously.

Ready to build your VR application?

Tell us what needs to be practised or shown, who the users are and what hardware is available. We are happy to help you think through scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom development pays off in your situation.

Edit content