Create the app package
Prepare app.info, main.lua, and required assets.
HoloCubic App SDK
The app package defines its name, entry point, and assets. Lua handles lifecycle, networking, and device logic; LVGL builds the interface. Use the public C ABI only when native performance is required.
View the workflow ↓hello/
├── app.info
├── main.lua
├── main.png
├── assets/
└── modules/ # optional
$ app.rescan()
✓ Hello is readyBasic workflow
Prepare app.info, main.lua, and required assets.
Use LVGL widgets or Canvas for the 320 × 240 screen.
Upload to /sd/apps/{app-id}, then rescan apps.
SDK STACK
Every layer has a clear boundary, from app package to native extension. Start with Lua and LVGL; use the C ABI only for a measured performance need.
Directory, metadata, entry point, lifecycle, deployment, and cleanup. An app starts independently and stops tasks and releases resources on exit.
[app]
name = "Hello"
entry = "main.lua"
icon = "main.png"NodeMCU-style timers, networking, and files plus HoloCubic capabilities for BLE services, IPC, and device state.
local timer = tmr.create()
timer:alarm(1000, tmr.ALARM_AUTO, function()
print("tick", tmr.time())
end)Widgets, styles, events, animation, images, fonts, and Canvas, designed around 320 × 240 and short callbacks.
local label = lv_label_create(lv_scr_act())
lv_label_set_text(label, "Hello, Holo.")
lv_obj_center(label)A versioned Host API for performance-sensitive audio, protocol, and sustained computation. It neither exposes nor permits reliance on host-firmware internals.
const holo_host_api_v1 *host;
int holo_module_init(const holo_host_api_v1 *api) {
host = api;
return HOLO_OK;
}PUBLIC BOUNDARY