Advanced Streaming: data usage & bandwidth requirements

Overview

Pixaera’s advanced streaming modules are not delivered as continuous video streams. Instead, they are scene-based, asset-driven experiences that progressively load compressed content as the learner moves through the module.

This approach results in:

• Predictable and bounded data usage
• Lower overall data consumption compared to traditional video streaming
• Better performance in bandwidth-constrained environments

Data usage

Total module footprint

Based on measured production assets:

• A typical advanced streaming module has a total content footprint of approximately 150–200 MB
• This represents the upper-bound data usage if a user completes the module end to end

The total footprint includes:

• Scene assets (short video segments, animations)
• Images and overlays
• Audio feedback
• Configuration and UI assets

Subtitles and text-based assets are negligible in size.

Usage during a session

• Assets are loaded progressively, not all at once
• Data usage depends primarily on how much of the module is completed, rather than how long a user remains idle
• Partial completion results in proportionally lower data usage

On desktop browsers, some assets may be loaded earlier in the session to improve playback smoothness. This can result in a short initial increase in network activity when a module is launched. This behavior remains within the total module footprint described above and does not increase overall data usage.

Repeat access and caching

Where supported by the browser:

• Previously loaded assets may be cached locally
• Replaying a module on the same device and browser typically requires less additional data, as not all assets need to be re-downloaded

Bandwidth requirements

Advances streaming modules do not require sustained high-throughput video streaming. Bandwidth primarily affects how quickly assets load between scenes.

Recommended

• ~25 Mbps download on a stable connection
• Low latency for best user experience

Lower bandwidth environments

• Modules can still function on lower bandwidth connections
• Users may experience longer load times between scenes

Mobile and bandwidth optimization

We are actively working on asset-level optimizations, with a particular focus on:

• Reducing payload sizes for mobile devices
• Improving performance in bandwidth-constrained environments

These improvements are expected to further reduce overall data usage over time.

Summary for IT planning

• Typical module size (upper bound): ~150–200 MB
• Data usage is bounded and predictable
• No continuous video streaming
• Progressive loading with browser caching support
• Designed to perform reliably across a range of network conditions