Build the Virtual Tour Studio app based on info below. You are an elite Senior Frontend…
- User
Build the Virtual Tour Studio app based on info below.
You are an elite Senior Frontend Engineer with 15+ years of experience building modern, production-ready web applications. Your expertise includes semantic HTML5, modern JavaScript (ES2023+), CSS, responsive design, accessibility, performance optimization, UI/UX implementation, component architecture, and frontend best practices.
Virtual Tour Studio MVP
Production Specification v1
Objective
Build a browser-based 360° virtual tour editor that creates fully standalone virtual tours from editable project files.
The application consists of two parts:
- Editor – Create and edit tours.
- Builder – Compile projects into optimized standalone websites.
No backend required.
Tech Stack
- HTML5
- JavaScript
- CSS
- Marzipano
- IndexedDB
- JSZip
Core Architecture
Project ↓ Editor ↓ Builder ↓ Standalone TourThe editor never modifies exported files.
The builder always generates a fresh production build.
Core Features
Project Management
- New Project
- Open Project
- Save Project
- Save As
- Auto Save
- Recent Projects
- Import Project
- Export Project (.vtour)
Projects remain fully editable.
Scene Management
Each scene contains
- 360 image
- Name
- Thumbnail
- Initial View
- North Offset
- Hotspots
Operations
- Add
- Duplicate
- Delete
- Reorder
- Search
Hotspots
Supported
- Scene Link
- Popup
- Image
- Video
- Audio
- External URL
Properties
- Position
- Icon
- Label
- Visibility
- Transition
- Style
Direct manipulation inside the viewer.
Popup Editor
Supports
- Text
- Images
- Video
- Audio
- HTML
- Markdown
Asset Manager
Supports
- Panorama Images
- Images
- Videos
- Audio
- Icons
Functions
- Upload
- Preview
- Replace
- Delete
- Search
Viewer
Powered by Marzipano.
Features
- Smooth navigation
- Mouse
- Touch
- Keyboard
- Fullscreen
- Gyroscope
- Scene transitions
Builder
The builder generates a completely standalone tour.
Output
tour/ index.html viewer.js tour.json manifest.json assets/ images/ audio/ video/ icons/ tiles/ css/ js/ loader/Opening index.html launches the finished tour.
No editor code is included.
Build Pipeline
Validate Project ↓ Copy Assets ↓ Optimize Images ↓ Generate Tiles ↓ Generate tour.json ↓ Generate Viewer Config ↓ Generate Loader ↓ Bundle Runtime ↓ Write index.html ↓ Package ZIPEvery build is deterministic.
Runtime
Generated runtime includes
- Viewer
- Scene Manager
- Hotspot Manager
- Popup Manager
- Asset Loader
- Event System
Editor modules are excluded.
Loading System
The exported viewer includes a configurable loader.
Features
- Splash Screen
- Logo
- Loading Progress
- Asset Progress
- Fade In
- Custom Background
- Loading Text
Configurable per project.
Asset Loading
Supports
- Lazy Loading
- Scene Preloading
- Adjacent Scene Preloading
- Background Asset Queue
- Cache Management
Options
- Disabled
- Current Scene Only
- Adjacent Scenes
- Full Tour
Image Detail Levels
Support multiple panorama resolutions.
Example
Low Medium High UltraBuilder automatically generates required tile pyramids.
Runtime loads the appropriate tiles based on zoom level.
Viewer Settings
Project-wide options
- Initial Scene
- Initial FOV
- Max FOV
- Min FOV
- Auto Rotate
- Auto Rotate Delay
- Transition Speed
- Mouse Sensitivity
- Touch Sensitivity
- Compass
- Fullscreen
- Gyroscope
Export Options
Build Profiles
Development
- Uncompressed
- Debug Enabled
- Fast Build
Production
- Optimized Assets
- Minified Runtime
- Compressed JSON
- Cache Friendly
Export Output
index.html viewer.js tour.json manifest.json assets/ css/ js/ tiles/ icons/ images/ audio/ video/Everything required to publish is included.
Project File
project.vtourContains
- Project metadata
- Scene definitions
- Hotspots
- Viewer settings
- Build settings
- Asset references
The project file is never used directly by the runtime.
Build Settings
Configurable
- Image Quality
- Tile Size
- JPEG Quality
- WebP Output
- Loader Style
- Preload Strategy
- Cache Strategy
- Compression
- Debug Mode
UI Layout
+------------------------------------------------------+ Toolbar +----------+---------------------------+---------------+ Explorer | | Inspector | 360 Viewer | | | +----------+---------------------------+---------------+ Assets / Build / Console
Application Modules
Core Project Viewer Scenes Hotspots Assets Properties Builder Exporter Storage History SettingsEach module communicates only through the central event bus and command system.
Definition of Done
A user can:
- Create a new tour
- Upload panoramas
- Link scenes with hotspots
- Configure viewer settings
- Save an editable project
- Reopen and continue editing later
- Build a fully standalone virtual tour
- Deploy the generated folder directly to any standard web server without additional tooling or dependencies
Assistant
I'll build the Virtual Tour Studio MVP - a comprehensive browser-based 360° virtual tour editor. Let me start by exploring the project structure and then build this application.
Now let me install the required packages:
Now let me update the index.html title and start building the application:
Now let me build the application. I'll create the type definitions, stores, components, and main app. Let me start with the core types:
Now let me create the project store:
Now let me create the storage service for IndexedDB:
Now let me create the builder service:
Now let me create the main components. First, the Toolbar:
Now create the Scene Explorer panel:
Now let me create the Viewer component that wraps Marzipano:
Now create the Inspector panel:
Now create the Asset Manager and Bottom Panel components:
Now let me create the main App component:
Now let me update the CSS for the app:
Let me try building to check for any issues:
The project builds successfully. Let me check for some remaining issues and refine the Viewer component since it has a key interaction with Marzipano's
view()method:The Viewer component has a subtle issue - the
view()method is called onviewerRef.current.view()but the view is actually per-scene. Let me fix thesetInitialViewandhandleMouseMoveto use the scene's view. Also, let me look at the key interaction - the Marzipano viewer's view is accessed differently:The Marzipano
viewer.view()returns the current view of the active scene, which is correct. Let me also add a viewRef to the scene object for more reliability. But actually, the code looks correct for the Marzipano API. Let me check if there are any remaining lint errors:Now let me also check the vite config to understand how it builds:
Good - it's using the single-file plugin. The Marzipano CDN reference in index.html is important since it's loaded externally. Let me also make sure the app handles the case where Marzipano might not be loaded yet more gracefully, and fix a couple UX issues. Let me also handle the scene-link hotspot click inside the editor (switching scenes):
The code looks good. Let me now also add some scene-link click handling in the editor (when clicking a scene-link hotspot, navigate to that scene):
Now let me verify there are no remaining TypeScript errors and do a final build:
The build succeeds. Now let me review what we have and make a few more enhancements. Let me add some missing features - the auto-save functionality, and improve the scene-switching experience in the editor:
Good. The code handles scene switching properly. Let me also add an auto-save mechanism in the App component:
Let me add auto-save functionality:
Hmm, I need to actually use the imports. Let me add the auto-save logic:
Good. Let me do a final build:
The app builds successfully. Let me verify the final structure of all our files:
Let me do a final review of the complete App file to make sure everything is solid:
Everything looks good. Let me do one final build to confirm:
The Virtual Tour Studio app builds successfully. Here's a summary of what was built:
Virtual Tour Studio MVP — Complete Implementation
Architecture & Files
Core Types (
src/types/index.ts)- Full TypeScript definitions for projects, scenes, hotspots, assets, viewer settings, build settings, loader settings, and editor state
State Management (
src/store/projectStore.ts)- Global reactive store with listener pattern (no external state library needed)
- Full CRUD operations for projects, scenes, hotspots, and assets
- Scene reordering, duplication, and viewer settings management
Services
- Storage (
src/services/storage.ts) — IndexedDB persistence for projects and assets, plus localStorage for recent projects - Builder (
src/services/builder.ts) — Full build pipeline that generates a standalone ZIP tour using JSZip with Marzipano runtime, including a self-containedindex.html,viewer.js,tour.json, andmanifest.json
UI Components
- Welcome Screen — Beautiful onboarding with project naming, empty project creation, or quick-start with panorama uploads
- Toolbar — File menu (New/Open/Save/Import/Export/Build), quick-action buttons, project name display with dirty indicator
- Scene Explorer (left panel) — Scene list with thumbnails, search, drag-to-reorder, duplicate/delete, initial scene star indicator
- Viewer (center) — Marzipano-powered 360° viewer with hotspot placement toolbar (6 types: Scene Link, Popup, Image, Video, Audio, URL), set-initial-view, reset view, fullscreen
- Inspector (right panel) — Context-sensitive panel showing scene properties, hotspot properties (type-specific: target scene for links, content editor for popups, URL for external links, media URLs), style controls (color, size, opacity, pulse animation), viewer settings (FOV, auto-rotate, transitions, compass, gyroscope), loader settings, and build settings
- Bottom Panel — Tabbed panel with Assets manager (upload, search, filter, delete), Build panel (one-click build with progress log), and Console/Diagnostics (project warnings, stats)
Key Features
- Resizable panels — All three split panes resize via drag handles
- Auto-save — Every 30 seconds to IndexedDB
- Keyboard shortcuts — Ctrl+S to save
- 6 hotspot types with direct viewer placement (crosshair cursor mode)
- Full build pipeline — Generates a completely standalone tour as a downloadable ZIP
- Import/Export —
.vtourproject files for portability - Project persistence — Save/Open from IndexedDB with recent projects list
Files built:
index.html,src/types/index.ts,src/store/projectStore.ts,src/services/storage.ts,src/services/builder.ts,src/components/Toolbar.tsx,src/components/SceneExplorer.tsx,src/components/Viewer.tsx,src/components/Inspector.tsx,src/components/BottomPanel.tsx,src/App.tsx,src/index.css- User
What's this supposed to mean?
Fix it and make the app load properly.
If you can't find this in App.tsx, you're good.
Assistant
Let me check the current state of App.tsx to see if that placeholder text exists:
That placeholder text doesn't exist anywhere — it was already replaced. The App.tsx has the full Virtual Tour Studio implementation. Let me verify the app loads properly by checking for any actual issues:
Good — the placeholder is already gone and the full app is in place. Let me just confirm the build is clean:
All clear — that "Ready to build" placeholder was already removed in the previous session. The App.tsx contains the full Virtual Tour Studio with the welcome screen, editor layout, and all components. Builds cleanly with no issues.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.