Mario Sanchez-Prada
Software Engineer and WebKit Team coordinator at Igalia
Lalín, Spain
Actions
Software engineer and partner at Igalia with 18+ years of experience working on the development of Linux-based Operating Systems, the GNOME platform, Web engines (i.e. WebKit, Blink) and Web browsers (Epiphany, Chromium).
Past experience includes work on the Maemo project, Litl OS, GNOME, WebKit, Samsung’s SmartTV platform, Endless OS, and the Chromium project, among several other projects.
Mario currently works as part of Igalia's WebKit team coordinating its efforts around WebKit and WPE.
Area of Expertise
Topics
Unlocking the Full Potential of WPE to Build a Successful Embedded Product
The Web engine is the most important component of a Web browser, enabling developers to leverage the Web Platform for their applications. And thanks to Open Source Web engines like WPE, it is now possible to build all kinds of products for embedded devices using Web-based technologies, from set-top boxes and smart home appliances to GPS devices and in-flight infotainment systems, to name a few.
Unfortunately, companies usually fall into the trap of applying one-off fixes to meet their immediate needs, accumulating technical debt and struggling to adapt to the evolving nature of the Open Source projects they heavily rely on. On top of that, it makes it difficult to ensure that the stable releases of such projects properly fit the needs of the products they intend to build, leading to spending too much time being reactive to integration-related problems instead of focusing on building a great product.
In this session, we will focus on explaining the best practices to unlock the full power of WPE without falling into such traps, so that you can focus on building a stronger foundation for your future embedded products with WPE, while keeping maintenance costs under control.
Engineering Quality in a Fast-Moving Open Source Project: WPE WebKit
Building an embedded product on top of a large Open Source codebase like WPE WebKit is only the first step. The real challenge is keeping its quality stable as thousands of lines evolve and hundreds of changes land every week across multiple platforms.
In such an environment, errors and regressions are inevitable. What matters is detecting them quickly, understanding their impact, and reacting before they propagate further. This talk focuses on the engineering work that makes this possible, an effort that is essential yet often invisible.
Using WPE WebKit as a case study, we will explore how quality becomes a continuous engineering effort rather than a final validation phase and how CI and QA infrastructure, testing strategies, and processes (e.g. stabilization windows) sustain upstream development while supporting downstream deployments. We will show how these feedback loops reinforce each other and why aligning upstream and downstream processes is critical to keep quality stable over time.
This talk targets engineers, maintainers, and technical leaders working on large Open Source projects, as well as teams building products on top of them who need to sustain quality at scale.
Building end-user applications on embedded devices with WPE
The Web engine is the most important component of a Web Browser, enabling developers to harness the power of the Web Platform to build their applications. However, Web Browsers are not the only type of applications that can be built with Web Engines, which can also be used to develop other types of applications using the same Web-based technologies, but for a different type of use cases other than "browsing the Web".
These use cases can cover a wide range of situations outside of the traditional desktop or mobile environments, such as the ones embedded systems are usually used for (e.g. set-top-boxes, smart home appliances, GPS navigation devices, or in-car/in-flight infotainment systems, to name a few). And in those situations it is very common to be running on boards with SoCs and a particular set of HW capabilities that make it crucial for the Web Engine to be able to tightly integrate with them.
In this session we will focus on how WPE, a fully Open Source port of the WebKit Web engine for Linux-based embedded devices, can be used to adapt to the different challenges that embedded devices pose to develop end-user applications, using the power of the Web Platform underneath.
WPE Hands-On: Writing a Launcher for Embedded Devices with the New WPEPlatform API
WPE WebKit is the WebKit port for Linux-based embedded devices, powering Web-based user interfaces on platforms such as set-top boxes, smart appliances, and industrial systems. With the 2.54 release, a stable version of the new WPEPlatform API is now available, radically simplifying how the Web engine is embedded: thanks to built-in support for Wayland, DRM/KMS, and headless rendering, libwpe and external backends are no longer needed unless you target a different platform. Zero-copy buffer sharing via DMA-BUF is also available for efficient video and graphics pipelines on modern Linux kernels and supported platforms.
After a quick introduction to WPE WebKit, the session will demonstrate the new API in practice, showing how simple it has become to write a custom launcher to run Web-based applications on embedded devices. It will also offer practical guidance for migrating existing integrations to WPEPlatform, whether they are based on Cog or built directly on the legacy API.
Whether you are evaluating WPE for the first time or maintain devices already shipping it and wonder what it means for you, this talk will help you get started with the next generation of the WPE public API.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top