Feature Request: Scene State Preservation with Unique URLs

  • Background

    This request is a follow-up to my previous forum post: I want to give each scene a unique ID or parameters

    Feature Request

    I would like to request the ability to assign unique IDs or parameters to each scene in a VR tour, making URLs unique for each scene state.

    Use Case

    The primary use case is to maintain page state when users navigate between different pages in the same browser window. Currently, when users navigate away from a VR tour page and then return using the browser's back button, the tour resets to the initial scene instead of preserving the scene they were viewing before navigation.

    Current Behavior:

    • User views Scene B in VR tour
    • User navigates to a different page
    • User returns to VR tour page via browser back button
    • VR tour resets to Scene A (initial scene)

    Desired Behavior:

    • User views Scene B in VR tour
    • User navigates to a different page
    • User returns to VR tour page via browser back button
    • VR tour resumes from Scene B (preserved state)

    Proposed Solution

    By assigning unique IDs or parameters to each scene, the URL could reflect the current scene state (e.g., example.com/tour?scene=sceneB or example.com/tour#sceneB), allowing browsers to properly handle navigation history and state preservation.

    Alternative Approaches

    If there are other methods besides URL parameters/IDs to achieve scene state preservation across page navigation, I would greatly appreciate guidance on those approaches as well.

    Technical Benefits

    • Improved user experience with seamless navigation
    • Better browser history integration
    • Ability to bookmark specific scenes
    • Enhanced SEO potential with scene-specific URLs

    Thank you for considering this feature request.

  • hum@no.id
    indexofrefraction

    We would like to express our sincere gratitude to everyone who provided guidance.

    Thanks to everyone, it looks like we will be able to achieve the functionality we are looking for by using "deep links".

    In the future, we will make an effort to always read the official documentation carefully before asking questions in order to have more efficient and informed discussions.

    Thank you for your valuable time.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!