Requirements & Architectural Considerations for Local (Offline) URLs in EloView 3
Audience: Public / Elo Customers, Content Developers & Integrators
Article Type: Architecture & Content Deployment Best Practices
In EloView® 3, a Local URL package allows web applications, interactive kiosks, and digital signage content to run locally from onboard device storage without requiring continuous internet or network connectivity.
Core Requirements & Deployment Considerations
-
Self-Contained Local Asset Bundling:
For reliable offline execution, all dependencies must be packaged within the deployed ZIP archive. This includes HTML files, JavaScript libraries, CSS stylesheets, web fonts, vector graphics, image assets, and video/audio media files. -
Client-Side Execution Only (No Server-Side Runtimes):
Technologies that rely on active web server backends (such as PHP, Ruby, ASP.NET, Java Servlets, or Node.js server runtimes) cannot execute within the local browser runtime. All logic, routing, and rendering must rely exclusively on client-side browser technologies (HTML5, CSS3, JavaScript/WebAssembly). -
Bandwidth & Network Reliability Optimization:
Local URLs are ideal for environments with intermittent, bandwidth-constrained, or non-existent network connections (e.g., trade shows, secure retail zones, remote field kiosks). Hosting media files locally prevents network latency, buffering delays, and high cellular data consumption. -
Modern Caching & Offline Web API Support:
Progressive Web Applications (PWAs) running in EloView can leverage browser-level storage and synchronization mechanisms, including the Cache API, IndexedDB, and Service Workers. For technical implementation guidance, refer to MDN - Using Service Workers. -
Client-Side Frameworks & Background Sync:
Modern Single-Page Applications (SPAs) built with React, Vue, Angular, or vanilla JavaScript function completely offline when bundled properly. Applications designed for periodic synchronization can queue user transactions or telemetry locally and push updates whenever the device reconnects to a network.
⚠️ External Dependency Advisory: Offline reliability depends directly on how the application was architected. External CDNs, cloud APIs, third-party authentication redirects (OAuth), and remote database endpoints will fail to load or respond while the device is in an offline state. Ensure robust fallbacks and error handling are implemented for all network-dependent components.
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article