Today marks
three years since we released Vivaldi for iOS. Hurray! We released Vivaldi on Android seven years ago. So what explains the iOS delay? Quite simply, Apple caused the delay.
Globally, the only way to distribute apps for iOS and iPad iOS is through Apple’s App Store.
Since the dawn of time, one of Apple’s rules requires that every app that browses the web uses Apple WebKit, the same browser engine that Apple uses to power Safari. You can’t choose which version of WebKit you use; it has to be the one that Apple ships, and it’s different from the one on the Mac.
Since Vivaldi began, we’ve built the browser for every other platform on top of Chromium, the open source project that uses Blink (and V8) as its engine. This is the basis of all our desktop browsers, and Android. We use it because we can build on top of it, adapt it to ensure that features like our Tracker Blocker are powerful and fast, and because we can remove any code that we don’t want to ship.
Building on top of WebKit gives us none of this flexibility. The only people who can fix bugs or add features to the engine are Apple, and only if it fits their business objectives. And because we can’t amend the code, we’re limited to what Apple allows us to change, in the manner they determine.
So we delayed developing for iOS, hoping that the new
EU Digital Markets Act (DMA) would require Apple to end its restrictions on competitors choosing their own tech stacks. The DMA was designed “to comprehensively regulate the gatekeeper power of the largest digital companies”, and it’s obviously anti-competitive for a Big Tech gatekeeper to limit the capabilities of its competitors.
But demand from our customers grew, and because we have no shareholders or investors pulling the strings, we listen to our community. So we built a team especially for iOS, and released the first version 28 September 2023.
Apple finally allowed non-Webkit browsers on iOS 17.4 in March 2024, and in September 2025 in Japan, under the Mobile Software Competition Act.
But we have not released a version using our preferred engine yet. Nor has any other browser vendor. Again, the reason for this is purely because of Apple. We were required to agree to a “Web Browser Engine Entitlement” purely to compile and test Chromium on iOS, and only on devices tied to Vivaldi’s developer account.
But
the conditions Apple attaches to the entitlement make it impossible for a small independent browser company to distribute our preferred product. We would have to develop and maintain two iOS browsers, one for EU and Japan, and the other for the rest of the world. We would need to ask all our EU and Japanese customers to move to a new Vivaldi rather than simply push an update through the App Store, while agreeing that “Apple may, in its sole discretion, reject, or cease distributing Your Alternative Web Browser Engine App (EU)
for any reason”.
vivaldi.com
