3DVista development, for tours that have to do more than spin

What 3DVista development actually means

3DVista is a tour authoring tool, and most people use about a tenth of it. They stitch panoramas, drop hotspots, add a floor plan, and publish. That is a brochure that moves, and it is why so many virtual tours get looked at once and never again.

3DVista development is the other nine tenths. Underneath the panoramas there is a scoring system, conditional branching, url parameters, and a layer that will host your own HTML. There is also, deliberately, no published scripting API. Those five facts are the whole job.

I have been building tours since 2022 and writing software since 2020, and this sits exactly in between. That is the whole reason it is rare. A photographer does not want to write logic and a developer does not want to carry a tripod through a factory.

Conditional actions, which is where most tours stop

A conditional action asks a question before it does anything. Has this visitor already seen the safety panorama? Did they answer the third question correctly? Did they arrive through a partner link rather than off the home page?

Once a tour can ask, it can behave. A staff induction can refuse to hand out the certificate until every station has actually been visited. A showroom can show trade pricing to someone who came in through a partner link and retail pricing to everyone else. A museum can let a child and an adult walk the same rooms and read different labels.

This is ordinary in software and almost unheard of in virtual tours, because it needs somebody who thinks in state rather than in scenes. Most of the 3DVista development work I am asked for starts here.

Custom skins, not a template with your logo on it

The skin is everything the visitor touches: the buttons, the menu, the overlays, the panels, the transitions. 3DVista ships templates, and a template is instantly readable as a template.

A custom skin is drawn for the space it belongs to and for the job the tour has to do. A hotel tour and a factory induction should not have the same interface, because a guest is browsing and a contractor is being checked. Twenty five years of industrial design is not decoration here. It is knowing what a control should look like when somebody has to use it correctly the first time.

Tools that run inside the tour

3DVista will host your own HTML inside the tour, and this is the least used and most valuable thing in it. A working tool, in the panorama, sharing state with the tour around it.

A price calculator that adds up what the visitor selected as they walked. A keypad that unlocks a room. An audio player that keeps its position when you move. A menu that builds itself from what the visitor has already unlocked.

I already sell finished tools of exactly this kind, which is the honest proof that the approach works rather than a claim that it might: a dynamic menu builder, a full keyboard generator, a pin code generator and a smart audio player, all standalone and all written to drop into a tour without colliding with each other. Custom work for a specific tour is the same craft, aimed at one problem.

Gamification and quizzes, when they earn it

Gamification is usually decoration bolted onto something nobody wanted to look at. It works when the score means something: a training pass mark, a treasure hunt a museum runs for schools, a qualification step before a sales team calls you back.

Here I will tell you something most people selling this will not. 3DVista already has a quiz system, and it is a good one: question cards, several scores running at once, branching on the answer, and a report at the end. If a plain scored quiz is all you need, you do not need me, and anybody telling you otherwise has not opened the software.

You want 3DVista development at the point you need something it does not do. A result screen that is yours instead of the built in one. The score leaving the tour and arriving somewhere you can act on. A scoring rule a question card cannot express. Something that is not a quiz at all.

A tour somebody else already shot

This is the most common way people arrive. There is a tour, it cost money, and it does nothing. The panoramas are usually fine. What is missing is everything that was supposed to happen after them.

In most cases that can be rebuilt from the existing project without going back to the location, which makes it far cheaper than starting again. Send me the project file or the published link and I will tell you honestly whether it is worth rebuilding or whether the capture itself is the problem.

Working with a 3DVista developer remotely

The capture has to happen where the space is. The 3DVista development does not. Logic, skins, tools and rebuilds are all done from the project file, so this part of the work is the same whether you are in Thessaloniki or anywhere else.

If you are a tour producer who has won a job you cannot deliver the interactive half of, that is a normal arrangement and I am happy to sit behind you rather than in front of your client. Hiring a 3DVista developer for one job is cheaper than turning the job down, and considerably cheaper than promising it and learning the software on the client's deadline.

If you would rather read than hire, three pages go into the detail: what the e-learning module does on its own and where it stops, running your own HTML inside a tour, and what to do about there being no JavaScript API.

You get the project file at the end. A tour you cannot open without me is a tour I would not want to have sold you.

What you get

• A scope written before anything starts, so 3DVista development is a fixed piece of work rather than an open meter
• A custom 3DVista skin built for your tour, not a template with your logo dropped in
• Conditional actions: the tour changes what it shows depending on what has happened
• Dynamic inputs, variables and state that survive moving between panoramas
• Custom HTML tools running inside the tour: calculators, keypads, players, menus
• Gamification and scored quizzes, with a result the visitor and you can both see
• An existing tour rebuilt into something that works, without going back to the location
• The project file handed over, so you are not locked to me