Custom Chromium and Brave builds
XFII Browser
A branded Brave-based browser with extensions switched off, a custom new-tab page and browser pages built in React.
- Brave
- Chromium
- React
- New-tab page
- Branding
- Built on
- Brave (Chromium)
- Our part
- We built XFII on Brave’s code with its own branding, a custom new-tab page, React-built pages and extensions switched off.
The client and the problem
The client wanted a browser under the XFII brand whose features are fixed by the product: users cannot add extensions, and the first screen they see is XFII’s own.
What we built
We built XFII on Brave’s open-source code, which runs on Chromium. We replaced the new-tab page with XFII’s own, switched extensions off, built parts of the browser’s interface as React pages rendered inside the browser, and carried XFII’s branding throughout.
- XFII branding across the browser
- A custom new-tab page
- Extensions switched off
- Browser pages built in React
Why it was hard
React pages let those screens be built with ordinary web tooling. Pages packaged inside the browser still need a new release to change; pages loaded from a server can change without one. Switching extensions off also means closing every route a user would normally take to install one, not only hiding a menu item.
How it fits together
What XFII changes on top of Brave
XFII Browser
The client’s product: the XFII brand, carried across the interface.
Custom new-tab page
A new-tab page built for XFII in place of the default one.
React pages and locked extensions
- React
- Extensions disabled
Parts of the browser interface are React pages rendered inside the browser, and extensions are switched off.
Brave / Chromium
- Brave
- Chromium
Brave’s open-source browser code and the Chromium engine under it.
Build and release
Packaging and release of the branded build.
- Client's product
- Our engineering
- Upstream: third-party code we build on
- Platforms and release
Related services
Facing a similar engineering problem?
Tell us what you are building. A browser engineer will walk you through how we would approach it, what is hard about it and what it takes to keep it current after launch.
More case studies: Custom Chromium and Brave builds
Egon Browser
A Brave-based browser we built for a private client, with its own branding and privacy defaults set to the client’s requirements.
- Brave
- Privacy
- Branding
Ajna Browser
A Chromium browser we built for a private client, with a redesigned interface and its own privacy features.
- Custom UI
- Views toolkit
- Privacy