Connected desk display / Ferced Labs

HUBI

I contributed to a connected desktop display project with a configurable web editor, widget previews and layout synchronization between local software and embedded firmware.

Physical HUBI display showing its clock, Duolingo reminder and coding-agent activity
OriginalOriginal photo supplied by Franco. The physical device is showing its clock, a reminder and agent activity.

At a glance

Period
2026; ongoing development
Role
Web product software contribution
Team
A Ferced Labs project
Users
People who want a small desk display for daily information, shortcuts and connected services
Status
Working device and local hub; product development continues. The public demo uses example data.
  • DeviceESP32-S3 / 480 x 480 touch
  • Local hubBun / TypeScript / WebSocket
  • SetupUSB-C power / local Wi-Fi
  • Public demoExample data / no connected accounts

My part

Contributed to the configurable web editor, device and widget previews, and layout synchronization between the local hub and ESP32-S3 firmware as part of the project.

Tradeoff

Keep a 480 by 480 touchscreen useful while connections, configuration and screen editing live on the computer. A saved setting, a service connection and a device acknowledgement need distinct states.

Evidence

Original device photo and a recorded demonstration supplied by Franco, plus the public product site and screen-editor demo. The public web demo uses example data and identifies integrations still in testing.

01

One small screen, several sources

HUBI puts the clock, reminders, focus, shortcuts and connected-service information beside the computer. The product work is deciding what deserves space on a small display and what belongs in the hub.

OriginalSilent excerpt of the original video supplied by Franco. It shows the physical screen; the full recording is kept separately.
02

Firmware and local software share a contract

The ESP32-S3 runs the touchscreen interface. A local Bun/TypeScript service gathers source state and communicates with the device over WebSocket. Wi-Fi setup, reconnection and OTA updates are part of the same integration surface.

03

Editing screens is part of the product

The hub brings screen editing, the widget library, connections and device state into one interface. A draft, a saved configuration and an acknowledgement by the physical device remain different states.

Public HUBI screen editor with a device preview and editing controls
PrototypeCapture of the public screen-editor demo. Example data; no personal accounts or devices are connected.
04

The website lets people try the idea

The bilingual site combines an interactive device tour, screen-editor demo, material choices and connection details. It explains the computer and network requirements before someone follows the reservation link.

05

What the evidence covers

The photo and recorded excerpt show the physical device in use at the time of capture. The public tour and editor use example data. Connections marked as in testing still need real validation; the recording does not establish compatibility with every account or device.

Project linksgethubi.xyz