XP Inc. Home Broker: white-label migration
Front-end work on the Home Broker at XP Inc. during its move to a single white-label platform, including forward-contract trading screens, the navigation menu and the migration to a new version of the SomaDS design system.
XP Inc. now runs the white-label Home Broker for all of its brands.
The problem
The Home Broker is the web trading platform of XP Inc., a Nasdaq-listed company, and one of its largest products. The company needed a single platform that could serve all of its brands instead of the previous model, so the Home Broker was rebuilt as a white-label product. At the same time, the SomaDS design system got a new version, shaped largely by what the Home Broker needed.
What I built
I worked at XP Inc. for four years, about a year and a half of that on the Home Broker, as a front-end engineer in a small squad that owned everything front-end on the product. My work included:
- Forward-contract order ticket (boleta a termo) and the forward-contract positions screen.
- The main menu, including its structure and behaviour.
- Migrating from the old model to the white-label one, including moving the services the front end depended on to new SDKs so they could work in the new format.
- Refactoring components to the new SomaDS version.
- Bug fixes across the product, and onboarding new people joining the team.
Technical decisions
Decisions were made as a team, and I took an active part in them.
- One real-time channel per account. Any movement on the assets linked to an account, such as orders sent, executed or rejected, arrived through socket services. Every screen consumed that stream through shared SDKs instead of opening its own connections, so a new screen got real-time data by plugging into the same layer.
- SDKs as the migration boundary. Moving services to new SDKs was what made the white-label model possible: brand-specific behaviour stayed behind the SDK layer, and the screens above it did not need to know which brand they were running for.
- Design system first. Instead of patching components locally, we moved them to the new SomaDS version, which had been built to cover the Home Broker's needs. That kept the product consistent across brands and left fewer one-off components to maintain.
Outcome
XP Inc. now runs the white-label Home Broker for all of its brands. The forward-contract screens, the menu and a large share of the migrated components are my work.