When everything is up and running, the flow looks remarkably smooth. The firmware gets flashed to a board once, and after that a program is nothing more than a file sent over WiFi that starts immediately. RIBASIC, the interpreter interface, runs a blink script on GPIO 10 with 1000 millisecond pauses between LED states. The script is typed in, a green RUN button gets pressed, and a green arrow marks whichever line is running while a virtual LED flips each second before execution stops back at the ready state.
The way it is put together stands out. The maker wrote a custom virtual machine with a BASIC-like language, and scripts compile to bytecode right on the board. Heavy multimedia work lives in C inside the firmware, covering the decoder, camera and graphics, and shows up in scripts as simple commands. Each script starts with a config block declaring what is wired where, and for popular boards stock presets cover PSRAM, display pins, camera and audio. With just that block edited, one script works across any ESP32 board.
Around the core sits what the maker calls a whole ecosystem: an editor that works from a browser or phone, tools for images, fonts and audio, an AI helper, and a cloud service. The claimed payoff is concrete. A radio that took a week to play without stuttering or crashing, and whose board rebooted after a day from memory leaks, supposedly takes a single evening now. The maker also says a complex project or business idea can launch in an hour with the whole set of tools.
Two things remain open. Whether code executes directly from the screen has not been answered, and the post text actually cuts off mid-sentence right after saying the firmware is debugged once. How the RIBASIC interface relates to the wider ecosystem is also left unexplained.