OreoOS: a MicroPython-based OS for an open-hardware ESP32-S3 conference badge

[Circuit-Overtime]

Hi all, sharing OreoOS, a MicroPython-based operating system for the Oreo Badge, an open-hardware ESP32-S3 conference badge (ESP32-S3-WROOM-1-N16R8, 2.0" 320x240 ST7789, MPU-6050, IR receiver, Li-ion over USB-C).

Repo (OS, drivers, apps, KiCad design): https://github.com/elixpo/oreo · Site: https://oreo.elixpo.com

What's in it

• App model: an app is a class with on_enter, update(dt) and draw(display); the launcher discovers apps from folders with a small manifest. About 20 apps ship by default (GitHub profile card and contribution graph, IR scavenger hunt, games, a Markdown reader, weather, gestures), plus an on-device app store.
• OTA updates from GitHub Releases, with SHA-256 checks and an atomic swap on the next boot.
• Native C user modules for the time-critical parts: IR capture, and video playback in the Gallery. The video path (RV565) inflates the next frame on core 1 while core 0 scales and DMA-transfers the current one over SPI; we wrote up the measurements in a paper (arXiv:2610.35935) and published the playback core separately as a library.
• Offline first: network apps draw from flash immediately and only sync when Wi-Fi is already up. We ended up with our own small raw-socket HTTPS GET with a wall-clock deadline, because in our setup a slow server could stall a body read past the requests timeout and wedge the run loop.
• Board definition: the badge builds as its own board (BOARD_DIR, USB strings "Elixpo / Oreo Badge"). We've opened esp32/boards/ELIXPO_OREO_BADGE: Add Oreo Badge board definition. #19846 to add it upstream.

Feedback very welcome, especially on the app model and on anything we're doing that MicroPython already has a better way for.