Every screen in the app is being rebuilt this weekend
Contents
Starting Saturday morning we are rebuilding the app's screens. This is not a new colour scheme.
The layout changes, the order things appear in changes, and in several places so does the number
of clicks between you and an order.
Here is what is changing, what is not, and how it arrives.
1. Why now
The screens grew by addition. Everything that shipped since the beta went wherever there was
room, and the result reads like a changelog rather than a workspace.
Over the past two weeks we put our screens next to the tools people already pay for, one screen
at a time, and wrote down where we lose. We lose on the scanner and on the trade journal. We are
even or ahead on the parts those tools mostly ignore: knowing whether the engine is actually
running, stopping it without panic, and seeing a backtest next to what the same strategy did
live. This rebuild is aimed at both halves of that list.2. What each screen becomes
Dashboard. One screen that answers is it running, what did it do today, and is anything
wrong, without scrolling. Equity curve with drawdown underneath, a calendar of daily results,
today's warnings, recent fills, performance split by strategy, and backtest against live for the
same strategy. A fresh install gets a five-step checklist instead of an empty screen.
Top and bottom bars. The top bar groups what you watch while running: state, today's result,
positions and working orders, your loss limit, and feed health. Start and stop become one
control, and stop asks which one you mean, stop the engine, stop new entries, or flatten
everything. The bottom bar carries connection and feed, engine, machine load and version, with
diagnostics behind an expander.
Settings. Rebuilt around operating profiles. A profile is one named bundle of strategy,
symbol selection, money and risk, trading hours and order method, so changing how you trade is
one choice instead of six screens. The left menu groups the sections and a fixed summary at the
bottom tells you what is still unsaved.
Backtest. Six screens. A strategy editor with a full-width code area, a factor reference,
completion and inline errors. Results with diagnostics and a robustness view. A trade list that
says why each entry fired and how it filled. Optimisation drawn as a two-variable map with the
stable region marked rather than a table of best rows. One-second replay with ten levels and the
tape. A run history that puts two runs side by side along with the code change between them.
Live trading. Status bar, loss limit, three emergency buttons, click-to-order from the depth
ladder, and sell-all from a position row. Emergency flatten confirms once, then re-reads the
account and reports what it actually holds, instead of assuming the orders worked.
Scanner. Moves into a workspace you can lay out and save.3. What is not changing
Your settings keep their values. Not one setting key was renamed, so what you saved is what
you get, under new labels.
Your strategies, recordings and trade history are untouched. Nothing is migrated, converted
or rewritten on the way through.
Two things are being removed: the AI model section in settings, and the AI check feed strip. If
you have a backtest whose results depended on the ML entry gate, re-run it after you update.4. How it arrives
As ordinary updates across Saturday and Sunday, in several builds rather than one drop. The
backtest screens land in stages, so for part of the weekend you may see the new editor next to
the older result tabs. Nothing stops you trading while this happens, but if you are running live
on Saturday, take the update between sessions rather than during one.5. What we want back
Tell us where the new layout costs you a click you did not pay before. That is the failure this
kind of rebuild introduces most often and the one we are least able to see from the inside.
Feature Requests or Bug Reports, either board is fine.