Experiences

In Vū Studio, almost anything in your Library can become an Experience — a launchable piece of content that you add to a custom Session. An Experience can be an image, a video, a web link to a 3D experience or a website, the name of an executable you plan to run on the Vū Media Server, or an animated background.

Experiences are organized into Sessions — curated launcher screens that bundle a selected set of Experiences behind custom branding. Sessions are ideal for kiosks, touchpads, briefing centers, and trade-show stations.

Creating an Experience

Anything you add to your Vū Studio Library can be turned into an Experience, and the workflow is the same for every asset type:

1. Add the asset to your Library. Upload an image or a video, add a web link (to a website or a 3D/Unreal experience), enter the name of an executable you plan to run on the Vū Media Server, or create an animated background.
2. Save the item.
3. Right-click the asset and select Create Experience from the menu.

Vū Studio generates the Experience settings for that asset and adds it to the customizable Experience module, where it becomes available to add to any custom Session you design for your needs.

Experience Settings

Creating an Experience opens its settings so you can customize how it looks and behaves:

• Name and description — how the Experience is labeled in the module and in Sessions
• Icon and color — the appearance of the Experience tile
• Background — the image shown behind the Experience
• Start and stop behavior — what happens when the Experience is launched and when it ends (for example, looping or closing when a video finishes)

Sessions

A Session is a curated launcher screen that groups the Experiences you choose behind custom branding — your own logo, page title, and background. Build one Session per audience, vertical, or event, and load the appropriate Session on each kiosk or touchpad. You can add or remove Experiences from a Session at any time to tailor it to your needs.

Sessions live on the Experiences page at one.vu.studio/experiences. To get there inside Vū Studio, click the Vū Studio icon to go Home, then click Experiences.

The page is the Session — there is no separate list to work through before you reach the content. It opens straight onto the launcher your audience sees: the Session's logo and title in the title bar, the Session's background filling the screen, and the Experiences it contains laid out as a grid of tiles that launch on a single tap. A Session with no title of its own is headed Experience Selector.

Switching Sessions

The title button in the top bar names the Session you are currently in — or reads Session when no Session is loaded. Click it to open the Session list:

Option	What it does
A Session name	Loads that Session — its branding and its set of Experiences
Default	Returns to the unbranded selector, showing your Experiences with no Session branding
Add New	Opens Create New Session so you can build a new one

Switching Sessions takes effect immediately; there is nothing to save.

Creating a Session

1. Open the Session list in the top bar and click Add New.
2. In the Create New Session dialog, type a Page Title. This is the name shown in the title bar and in the Session list.
3. Optionally pick a Background and a Logo from your Library. Each is chosen from an asset picker, and the restore icon beside it clears your choice.
4. Click Create Session.

The new Session loads straight away, ready for you to add Experiences to it.

Editing a Session

Click the pencil icon (Edit Experiences) in the top bar to enter edit mode. A row of buttons appears along the bottom of the screen:

Button	What it does
Add Content	Opens the Experience picker so you can add existing Experiences to this Session
Session Settings	Opens the Session's title, background, logo, and team sharing options
Save	Saves your changes to the Session
Cancel	Leaves edit mode and discards your changes
Delete Preset	Deletes the Session. Shown only for a Session you own, and asks Delete Session? before it goes ahead

While you are in edit mode, each tile carries a small close button in its corner that takes that Experience out of the Session. Removing an Experience from a Session does not delete the Experience or the underlying Library asset — it only takes it out of this Session.

The pencil is available only to the owner of the Session, so a Session shared with your team cannot be re-edited by the people you shared it with.

Session Settings

Session Settings holds everything that makes a Session look like your brand:

Setting	What it does
Page Title	The title shown in the title bar and used in the Session list. Left empty, the page is headed Experience Selector
Background	The image or video shown behind the Experience tiles
Logo	An image shown to the left of the title in the title bar
Share Session With Team	Shares the Session with your team. Sharing a Session also gives the team access to any Experiences within it. Available on a team profile, for a Session you own

Click Save in the dialog to apply your changes.

Other Controls on the Page

Control	What it does
Magnifier (Search Experiences)	Opens a Search experiences... box that filters the tiles as you type
Plus (Create)	Offers New Canvas Design, which asks for a canvas size and then opens the Canvas Designer
Sliders (Toggle Admin Panel)	Opens a side panel with Sound, Image, and Lighting controls
Logo button (top-right)	Opens a menu with Enter Passive Mode, Exit to Library, and Log Out

While you are in Passive Mode the editing controls are hidden and the logo button asks for the PIN instead — see Passive Mode below.

Installing an Experience

Experiences can be installed on a specific display, making them available for on-site staff to launch directly without opening Vū Studio. Use the install option on an Experience to choose which Vū Media Server(s) it installs to. The Experience is then available as a one-tap launch from that display.

Running an Application on a Display

An App asset launches a program on the player computer instead of playing a media file — a kiosk program, a third-party viewer, a show-control tool. You cast it from the Library like any other asset, or start and stop it as a step inside an Experience.

Where applications run

Player	What you can launch	Path
Vū Studio Player desktop app on Windows	A Windows program (.exe)	Must be a full path, for example C:\Tools\Kiosk\Kiosk.exe
Vū Studio Player desktop app on macOS	A macOS app bundle (.app)	Must be a full path, for example /Applications/Kiosk.app
Vū Media Server	A Windows program (.exe)	A full path, or a path relative to the Documents/VuOne/ExperienceInstall folder
Web Player (browser tab)	Nothing — a browser cannot launch programs	—

The program, and any files it needs, must already be installed on the player computer. Vū Studio does not copy it there.

Adding an application

1. Open the Library at one.vu.studio/library — click the Vū Studio icon to go Home → click Asset Library.
2. Click Add Media, then choose the App tab.
3. Enter the program's path in Enter an application path... — a Windows .exe path or a macOS .app bundle path.
4. Click Add Application Source. The button stays disabled until the path ends in .exe or .app.
5. Cast the new asset to a player that can run it (see the table above).

The dialog accepts either kind of path, because an asset does not know in advance which player it will be cast to. The player checks the path when it launches: the desktop app on Windows runs only .exe files, and the desktop app on macOS runs only .app bundles. A relative path is rejected by the desktop app.

While an application is running

• One at a time. Launching an application closes the one that was already running.
• Casting something else closes it. Casting another asset or a scene, or stopping playback, closes the running application.
• Closing it on the computer is noticed. If someone quits the program on the player computer, Vū Studio stops showing it as playing.

Starting an application from an Experience

An Experience can launch a program as one of its steps. In the Experience's commands, choose Start Application and fill in Application Path and, if the program needs them, Arguments (Optional). Use Stop Application to close it again. The Experience itself stays the item that is playing while the program runs.

Limitations on macOS

• Most of Apple's own built-in apps (for example Calculator, TextEdit and Preview) refuse to open this way. Use the app you actually want to show rather than testing with one of these.
• A launched app may open in the computer's ordinary desktop space rather than on top of the player's full-screen window.

Passive Mode

Passive Mode lets visitors launch Experiences themselves using a PIN or touch interaction, without giving them full access to Vū Studio. It is useful for self-guided briefing centers, kiosks, or demo spaces.

To enable:

1. Open the Session or Experience settings
2. Enable Passive Mode
3. Set a PIN (optional)

Volume and Brightness

Each Experience can have its own volume and brightness settings that override the global player settings while it is running. Configure these in the Experience's settings.

Canvas Designs

Experiences can include Canvas Designs — multi-page interactive graphics built in the Canvas Designer. A canvas design can contain text, images, video, shapes, lines, and interactive elements that respond to clicks.

To launch a canvas design directly from the Experiences page, click the Launch Canvas Design button on an experience card. This opens the design in Present Mode — a full-screen interactive playback environment — without needing to open the Canvas Designer first.

To build or edit a canvas design, go to Create in the left sidebar to open the Canvas Designer.

Using a Canvas Design as a Session

A Session does not have to be a grid of Experience cards. A Session can instead be one canvas design that IS the page — the design fills the whole screen and the Experience card grid is not shown at all. This is the mode to use for a lobby screen, a briefing-room backdrop, or any surface where an audience is looking at the display and the app chrome should be out of the way.

Where this lives: https://one.vu.studio/experiences — click the Vū Studio icon to go Home → click Experiences → open the Sessions dropdown at the top of the page and choose the Session you want.

What is different on a canvas Session

• The design fills the screen and the navbar hides itself. The header is moved out of sight so nothing overlays the design.
• One way back: a small, deliberately faint arrow at the top centre of the screen. Click it and the navbar slides in; a matching close control appears just below the navbar, so the same spot toggles the header in and out. The arrow is a real button, so you can also reach it with Tab and press Enter. While the navbar is hidden it is skipped by keyboard focus entirely — you cannot tab into controls you cannot see.
• Search and the + create menu are dropped. What stays is the same set kept whenever content takes the whole viewport: your identity, the connection indicator, the room controls, and the exit.
• The Sessions dropdown is the exit and stays reachable whenever the page is not in Passive Mode.
• Add Content and card reordering are dropped, because there are no cards to add or reorder.

Editing the design

Edit design is in the header and jumps straight to the Canvas Designer editor. It is hidden in Passive Mode but is otherwise available to anyone who can edit the design — a teammate can edit every pixel of a team-shared design, not just the person who owns the Session. Permission is enforced when the editor opens, not by hiding the button.

Session Settings and Delete remain available to the Session's owner only, exactly as they are for a grid Session.

The design's own actions still reach the room

A canvas design's interactive actions — sending content to another display, lighting changes — fire normally from inside a Session. Passive Mode restricts administration, not operation, the same way the Experience cards already behave.

When the design cannot be shown

Situation	What you see
The design was deleted	The Session stays a canvas Session, explains what happened, and offers to point at another design
You do not have permission to read the design	The card grid, plus a notice
The design has no pages	The card grid, plus a notice
The design has pages but every page is hidden	The design renders anyway, starting on the first page

That last row is deliberate: a design with all pages hidden renders in Present Mode and on its Library tile too, so refusing it only here would make the same design look broken on one surface and fine everywhere else.

Using a design for a Session does not hide it anywhere else. The design still appears as a card under Default, on the Canvas page, and in the Library. Being used by a Session is not a visibility setting.