Replay Kiosk is Too Resource-Intensive for Low-Powered Devices

[kezarjg]

Description

While testing DerbyNet on low-powered hardware, I’ve found that the Replay Kiosk places a significant load on the client device and does not perform reliably on devices with limited resources.

When running the Replay Kiosk on an Onn HD streaming device (Android TV–class hardware), the following behavior is observed:

• The kiosk frequently displays low frame rate warnings
• Performance degrades over time
• The device will eventually hang or crash, requiring a restart

This makes the Replay Kiosk impractical for use on inexpensive or embedded display devices, which are otherwise well-suited for kiosk-style deployments.

Expected Behavior

• The Replay Kiosk remains responsive and stable on low-powered devices
• Frame rate degrades gracefully under constrained resources
• The kiosk does not cause the client device to hang or crash

Actual Behavior

• High client-side resource usage
• Persistent low frame rate warnings
• Eventual freeze or crash on low-powered devices

Environment

• DerbyNet component: Replay Kiosk
• Client device: Onn HD streaming device (Android TV–class hardware)
• Use case: Dedicated kiosk display

Notes / Possible Areas to Investigate

• Rendering or animation complexity in the Replay Kiosk
• Frequency of updates or redraws
• Potential for a reduced-effects or low-resource mode
• Client-side throttling or frame rate caps