RETUI does not need an onboarding obstacle course.
The first screen is the launcher. There is no stack of cards to dismiss before you can use your phone. Type an app name, press enter, and you have already learned the most important part.
Start with the obvious thing
RETUI is command-first, but that does not mean every action needs a special incantation. If you want an app, type its name. Suggestions appear under the input so you do not have to remember the exact spelling.
Firefox Signal Camera
You can browse instead when memory is not the right tool. `apps -ls` opens the app drawer, and the same apps remain available from the prompt.
Help should live where the questions happen
`help` prints the workstation quickstart and the current command list. Add a command name when you need its actual syntax. That is more reliable than finding an old screenshot or a command from a build you are not running.
help help apps help alias help wallpaper help module
The full command map is useful when you want to explore, but you do not need to read it before using RETUI.
The guide waits until you ask for it
Type `guide` to see the available paths. The walkthrough prints each step in the terminal and places the current command beside its controls in the normal suggestion row. It does not block the launcher with a separate tutorial screen.
guide -start basicsTry help, the app drawer, modules, and the Settings Hub.
guide -start customizeDerive colours from a wallpaper, inspect presets, read theme controls, and browse configuration.
guide -start modulesList modules, open Notes and Timer, and see where Lua-backed panels fit.
While a guide is active, its command and controls own the suggestion row. That keeps the next step visible. `guide -off` gives the row back to apps, aliases, modules, and commands immediately.
Three ideas unlock most of RETUI
The command surface, configuration, and modules look like separate systems at first. They are really three levels of the same idea: act quickly, shape the launcher, then add the small tools you actually need.
CommandsRun actions directly. Start with an app name, `help`, `settings`, and `files`.
ConfigurationUse the Settings Hub for normal changes, or edit XML and text files when direct control is the better route.
ModulesOpen compact terminal panels for notes, timers, status, media, scripts, and focused workflows.
Presets sit between those levels. They let you save a visual state and return to it later. Wallpaper auto-colour can create a palette from the current wallpaper, but it remains separate from the presets you choose to keep.
A useful first ten minutes
This is not a mandatory setup sequence. It is a small route through the parts that make the launcher feel less like a demo and more like yours.
guide -start basics alias -add ll apps -ls apps -hide <app> wallpaper -auto preset -save mylook module -ls files
`alias` gives your repeated commands names. Hiding an app removes it from normal suggestions and drawer views without uninstalling it. `wallpaper -auto` and `preset -save` turn a generated colour state into something you can return to. `files` crosses into the yellow RETUI Files surface when the job is file management.
If a large visual change has not appeared everywhere yet, run `restart` to reload the launcher cleanly.
You can stop here
Termux, Lua modules, Tasker, Spaces, and direct config editing are there when you have a reason to reach for them. They are not homework for earning the right to use the launcher.
The command line becomes fast because it learns your habits through aliases, groups, presets, and modules. That takes time. RETUI should still be useful before any of that exists.
I want the first minutes with RETUI to feel like using a phone, not configuring a project. Curiosity can take you deeper. The launcher should never force you there.