Overview
Single-page applications (SPAs) are web apps that load a single HTML page, then dynamically update it as users interact with the app. Instead of loading new pages from the server for each action, SPAs rely on JavaScript to modify the existing page, creating a fast, seamless experience similar to a desktop app.
Key Features of SPAs
Lazy Loading: SPAs load the main HTML, CSS, and JavaScript once, and then dynamically update parts of the page as users interact with it. This eliminates the need for full-page reloads.
Enhanced User Experience: Because they avoid page reloads, SPAs provide a smooth, app-like experience. Users can interact with the app without waiting for new pages to load each time.
Routing: SPAs use front-end routing to handle different "views" or "pages" within the single HTML file. This allows for URL changes without triggering a full page load.
Popular Frameworks: Many SPAs are built using JavaScript frameworks like React, Angular, and Vue.js, which provide tools and libraries to handle the complex state management and routing.
Single Page Application Support in ObservePoint
ObservePoint supports Auditing and Journey execution in Single Page Applications just like normal websites with one exception.
The only exception is a specific setting called "Prevent Navigation" which is optionally configured in Audit and Journey Actions. This isn't supported because in order to prevent navigation, ObservePoint intercepts the network requests that would cause a new page to render, but in the case of Single Page Applications, unless you are linking to an external domain that isn't a single page application, no network will fire during navigation.