When the European Union’s Digital Markets Act (DMA) came into play last year, it sparked a significant shift in how tech giants like Apple operate. The new regulations forced Apple to make several changes to iOS, including allowing developers to create web browsers with their own engines. A year has passed since the changes took effect, yet the major web browsers have yet to release EU-specific versions. In an exclusive interview with 9to5Mac, Jona Bolin, the product manager at Opera, discussed how the changes have impacted competition and highlighted the remaining challenges for third-party browsers.
How the
The Digital Markets Act was designed with the goal of increasing competition within the tech industry by regulating “gatekeepers” — large companies like Apple that control key platforms. For Apple, this meant several significant changes to iOS, the most notable being the ability for third-party browsers to use their own engines instead of Safari’s WebKit. While this is a major step forward, Apple’s limitations have left many developers, including those at Opera, calling for more freedom and flexibility.
Opera’s Perspective on DMA’s Impact
Opera, a prominent browser with a strong European user base, is one of the key players benefiting from the DMA. Bolin, however, believes that while the changes have been helpful, there’s still room for improvement. One of the most significant benefits of the DMA for Opera has been the change that allows users to choose their default browser during the iOS setup process. This, combined with sideloading features, has led to a rise in downloads of third-party browsers in the EU.
However, despite these advancements, Bolin points out that Apple’s rules still create significant hurdles. For instance, although Apple allows third-party browsers to use custom engines within the EU, Opera’s team has reported that no browser is actually doing this due to the restrictions on migrating users from the global version of a browser to its EU-specific version. Bolin emphasized the challenges of managing two separate versions of the same browser, which introduces both risk and additional costs for developers.
The Challenges of
Apple’s implementation of the DMA has left many developers frustrated, particularly regarding the limitations of using WebKit. Bolin argues that the inability of third-party browsers to fully implement features that Apple has not yet supported limits innovation. He also believes that Apple should allow web browsers to use their own engines worldwide, not just within the EU, in order to foster greater competition.
Bolin’s stance reflects the broader sentiment within the developer community: Apple’s control over iOS, while slightly loosened by the DMA, still places significant restrictions on how third-party browsers can operate. The inability to freely offer custom engines across all regions means that developers face logistical and financial barriers to providing a truly competitive product.
Opera’s Strategy Moving Forward
Despite these hurdles, Opera remains optimistic about the future. The company believes that growing global regulatory pressure will eventually force Apple to open up its ecosystem in a meaningful way. Until then, Opera continues to innovate within the bounds of the current regulatory landscape. The company has rolled out updates to its iOS app, adding features like the Aria AI chatbot, a free VPN, content filters, and greater integration with iOS APIs, such as custom icons and widgets.
Opera’s commitment to privacy and user data protection, especially as a Norwegian company operating under Europe’s strict privacy regulations, is another key selling point for the browser. The company continues to focus on delivering enhanced privacy features while making its browser more feature-rich for iOS users.
What Undercode Say:
The ongoing struggle between Apple and third-party developers in the wake of the Digital Markets Act is a reflection of the larger battle over control in the digital ecosystem. While the DMA has made strides toward increasing competition, the implementation of its provisions by Apple has been far from seamless. Apple’s approach, which limits the ability of browsers to migrate users and forces them to work with two separate versions of their software, presents a significant roadblock to real innovation.
Opera’s experience sheds light on the broader issue: Apple is reluctant to allow any real competition on its platform, despite the EU’s efforts to level the playing field. By imposing rigid requirements, such as the continued use of WebKit for global versions of browsers, Apple has essentially locked developers into a model that doesn’t fully benefit users or developers. Even with regulatory pressures mounting, the company’s reluctance to embrace open standards in all markets indicates a fundamental unwillingness to change its control-heavy approach.
This is a pivotal moment in the browser wars, where the pressure on Apple is likely to grow stronger as more regulators across the globe push for greater openness. The Digital Markets Act was only the first step; the real challenge will be ensuring that Apple’s compliance leads to meaningful changes. Until then, third-party browsers will continue to struggle within the confines of Apple’s platform, with limited ability to fully differentiate themselves from Safari.
Fact Checker Results
- The Digital Markets Act does allow third-party browsers to use custom engines in the EU but still imposes limitations on user migration and browser version management.
- Opera’s decision to update its app with features like a free VPN and privacy filters aligns with its focus on user privacy and security, especially in the European market.
- Apple’s refusal to allow third-party browsers to fully utilize custom engines outside the EU remains a critical obstacle to real competition on iOS.
References:
Reported By: 9to5mac.com
Extra Source Hub:
https://www.stackexchange.com
Wikipedia
Undercode AI
Image Source:
Pexels
Undercode AI DI v2
