I got halfway there and then got sidetracked, but this turned into something pretty interesting.
Re:T-UI now supports custom modules powered by Termux.
The idea is simple:
- Termux acts as the execution layer
- Re:T-UI acts as the UI surface
You write a script in Termux, it outputs structured text, and Re:T-UI renders it as a module.
How it works
Termux gathers data → script prints module metadata → Re:T-UI renders it
The script just needs to output specific tags like:
::title
::body
::suggest
Example: Battery Module
For a first test, I built a simple battery module.
It uses termux-battery-status (from Termux:API), parses the JSON, and outputs formatted lines.
Output format:
::title Battery
::body Level: 75%
::body Status: CHARGING
::body Health: GOOD
::body Temp: 32C
::suggest refresh | command | module -refresh battery
Re:T-UI turns that into a UI module with a refresh action.
Script
#!/data/data/com.termux/files/usr/bin/sh
INFO="$(termux-battery-status 2>/dev/null)"
LEVEL="$(printf '%s\n' "$INFO" | grep '"percentage"' | cut -d: -f2 | tr -d ' ,')"
STATUS="$(printf '%s\n' "$INFO" | grep '"status"' | cut -d: -f2- | tr -d ' ",')"
HEALTH="$(printf '%s\n' "$INFO" | grep '"health"' | cut -d: -f2- | tr -d ' ",')"
TEMP="$(printf '%s\n' "$INFO" | grep '"temperature"' | cut -d: -f2 | tr -d ' ,')"
[ -z "$LEVEL" ] && LEVEL="unknown"
[ -z "$STATUS" ] && STATUS="unknown"
[ -z "$HEALTH" ] && HEALTH="unknown"
[ -z "$TEMP" ] && TEMP="unknown"
echo "::title Battery"
echo "::body Level: ${LEVEL}%"
echo "::body Status: ${STATUS}"
echo "::body Health: ${HEALTH}"
echo "::body Temp: ${TEMP}C"
echo "::suggest refresh | command | module -refresh battery"
Setup in Termux
mkdir -p ~/retui
nano ~/retui/battery.sh
chmod +x ~/retui/battery.sh
~/retui/battery.sh
Register in Re:T-UI
module -add battery termux:/data/data/com.termux/files/home/retui/battery.sh
module -refresh battery
module -show battery
Why this approach works
What I like about this:
- Re:T-UI doesn’t need a heavy plugin runtime
- No need to load arbitrary Android code
- No need to support full Android widgets
Instead:
- Termux = scripting + power
- Re:T-UI = clean UI surface
What you can build
Anything you can script:
- battery status
- server health
- weather
- network info
- habit tracker
- task list
- focus mode status
- build/deploy status
- Tasker-fed automation state
Notes
There were some typical Android/Termux quirks:
dumpsys batterywasn’t reliable on my devicetermux-battery-status(Termux:API) worked much better
But importantly, the module contract stayed simple:
- print
::title - print
::body - optionally print
::suggest
Status
Still rough around the edges, but the foundation is there.
Custom programmable modules in Re:T-UI are now possible.