Trading user interfaces
Consulting on trading user interfaces for web, desktop, and mobile, for people working orders, prices, and positions.
What this work is
We design and build the screens traders, sales, and operators use during the trading day. The interfaces are web, desktop, and mobile. They show orders, prices, and positions, and they let a person act. Send, amend, cancel, pause a strategy, or acknowledge an exception. The interface is part of the trading system. If a button says an order was cancelled before the platform has agreed, that is a defect in the trading system.
The work starts from the task. Who is sitting here, which decision they repeat all day, what they must see without asking, and what the system must refuse to do from this screen. A trader working a live order needs a different density of information from an operator watching sessions. A mobile view used away from the desk is a third job. Those jobs share the same orders and prices, and each one is built for the person using it.
Web and desktop cover most of the day-to-day build. Mobile is in scope when someone has to see or act on a position away from the full screen. A mobile client has to show the state of the order. If it cannot, we leave it out.
Who it is for
Clients are teams that already have a platform and a screen people have stopped trusting, and teams building a platform that does not yet have a usable front. Banks, brokers, fintech startups, and smaller trading firms come with one of those two briefs. We have built interfaces on large in-house platforms and on systems started from nothing.
The request is usually specific. A blotter that cannot keep up, a ticket that hides the fields the venue requires, a strategy control that does not show whether the strategy is working orders. Those can be interface problems and platform problems at the same time. We look at both, and we say when the fix belongs in the order path.
Typical work
The blotter and the order ticket come first. A person has to see working orders, recent fills, and rejects, and has to be able to act without the screen inventing a status the platform does not have. We bind every action to a response. If the venue or the risk check has not answered, the screen says so.
Price display follows. The price on the screen has to be the price the pricing system is distributing, with the age and the source visible when that matters to the decision. A last trade figure that does not match the price the strategy uses will cost the desk time. We show the numbers that match the platform.
Strategy controls are included when the platform runs algorithms. Start, stop, pause, and the parameters a trader is allowed to change. The parameters on the screen are the parameters the algorithm reads. A control that writes to a configuration nobody reloads will not change the algorithm. Status has to include whether child orders are working. That is the same state the benchmark execution path holds when that is the strategy.
Desktop, web, and mobile differ in how they are delivered and operated. A desktop client may be required where the firm already runs one. A web client is often the practical way to put the same orders in front of more than one desk, without a release on every machine. We recommend the client that fits the task, the support load, and the team that will own it. The languages behind the interface, and the ones we use elsewhere on the platform, are listed on the about page.
How an engagement runs
A review of an existing blotter or ticket fits a short package. Designing and building a screen, or a set of screens, fits a larger block. A retainer fits a platform whose screens change with the trading logic. Sizes and prices are on the packages page.
Contact us and say who uses the screen, and which action on it is wrong or missing.