Show HN: FrameOS – operating system for single function smart frames

Original Article ↗ Hacker News Discussion ↗

A new project called FrameOS aims to turn Raspberry Pi-based devices and various e‑ink or HDMI displays into single-purpose “smart frames” for dashboards, art, signage, and home automation. Commenters praise its polished visual editor, Nim-based runtime, and GPT‑4–assisted app building, while probing how it handles image processing, hardware drivers, and potential ports to low-power platforms like ESP32 or RP2040. Much of the debate centers on trade-offs between flexibility and resource constraints, whether it qualifies as a true operating system versus a kiosk-style application on Linux, and how it might compete with or complement existing solutions like MagicMirror or commercial digital frames.

Hardware & Platform Support

  • FrameOS currently targets Raspberry Pi (Pi Zero and up), using Raspberry Pi OS Lite as the base.
  • Supports HDMI displays and specific Waveshare/Pimoroni e‑ink panels via SPI/GPIO; more Waveshare drivers are planned.
  • Does not yet run on RP2040 or ESP32, though the author thinks Nim + static binary makes a future port possible, with tradeoffs (no threads/GC, tight memory).
  • Some users want it on cheap ESP32 e‑paper boards (e.g., InkPlate, LilyGo T5), but others note ESP32’s limits for HTTPS, image processing, or 60 fps output.

“OS” vs Application Debate

  • Several commenters argue it’s not a true OS but a fullscreen app on Linux.
  • Others counter that “OS” is loosely defined, and FrameOS behaves like a single-purpose environment: boots into one binary, owns apps/drivers, could in principle run bare‑metal or on microcontrollers.

E‑Ink, Image Processing, and Burn‑In

  • Users like automatic handling of cropping, dithering, and color indexing; manual workflows were painful in past DIY frames.
  • There is discussion of dither quality, color matching, and potential use of better algorithms.
  • For burn‑in on LCDs, common mitigations mentioned: periodically shifting the image slightly, random crops, or rotating multiple images.
  • E‑ink itself is said not to suffer traditional burn‑in.

Developer Experience & LLM Integration

  • The web editor uses a flow‑diagram interface (React + React Flow) to compose Nim apps into “scenes.”
  • Testing currently requires deploying to a Pi; faster browser-based simulation via Nim’s JS backend is a desired future step.
  • GPT‑4 integration exists in the editor: code is sent to the API to generate or improve FrameOS apps. Some see this as validation that LLMs will be standard in new tools; others are skeptical of LLM‑everywhere trends.

Use Cases & Comparisons

  • Suggested uses: home dashboards (often with Home Assistant), photo frames, digital signage, shop windows, hospital artwork/wayfinding, and transit signage.
  • Compared to alternatives like MagicMirror, old tablets, Kindle/Fire hardware, and commercial frames; many complain existing signage/art systems have clumsy or “rubbish” software.
  • Power usage and sleep/battery modes for Pi‑based frames are raised; deep sleep support is acknowledged as not yet explored.