Install CLI Step
A developer install step with per platform commands behind tabs, numbered login and test commands, and a live row waiting for the first event.
A developer install step with per platform commands behind tabs, numbered login and test commands, and a live row waiting for the first event.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Install CLI Step is the developer setup screen of an onboarding flow, laid out as three numbered commands inside a single card. Step one is a platform install line behind macOS, Linux, and Windows Tabs, each with a copy Button; step two authenticates with acme login; step three sends one sample event with acme events test. Below them a bordered row spins a loader while it waits for the first event to land, the signal that setup actually worked.
Install commands and follow-up steps are two small typed arrays, and the active tab swaps the shown command. The waiting row matters most: it turns a list of instructions into a confirmation that closes on its own the moment an event arrives, so the user never wonders if it worked.
Reach for this block on the instrumentation step of a developer onboarding wizard, wired to your event ingest so the waiting row flips to done in real time. The copy is careful to say nothing here touches production traffic, and an escape hatch lets users skip and instrument later without leaving the flow blocked.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the third step of technical setup. Other install step variants:
Tip: a live waiting row that resolves itself removes the did it work step, the most common place developers stall during setup.