Unlocking the Full Potential of WPE To Build a Successful Embedded Product
summary
WPE is an embeddable WebKit port optimized for devices; teams report using it on iMX and Raspberry Pi boards, migrating WPE to Skia for 2D rendering and GPU acceleration and replacing Chromium for kiosk-style React HMIs. Practical advice: keep downstream patches tiny, rebase frequently (examples show rebasing every 2–3 weeks versus painful 1–2 year forks), run product-specific CI with performance and regression checks, and contribute fixes upstream to avoid massive maintenance cost and duplicated work.
AI-written summary · about
chapters (10)
- 0:00WPE and embedded products
- 2:27What is a web engine
- 8:47Pitfalls in WPE integration
- 15:27Upstream collaboration benefits
- 19:04Best practices for WPE integration
- 27:03Customer case studies
- 32:59Three pillars for WPE
- 35:10Q&A: Chromium to WPE
- 37:57Q&A: Industrial HMI with React
- 39:22Q&A: WPE vs Chromium
related talks
49mEmbedding WPE WebKit - from Bring-up to Maintenance- 49mEmbedding WPE WebKit - from Bring-up to Maintenance
49mBuilding End-user Applications on Embedded Devices with WPE- 49mBuilding End-user Applications on Embedded Devices with WPE
37mWPE WebKit: HTML5 User Interfaces for Embedded Devices
42mReaching the Multimedia Web from Embedded Platforms with WPEWebKit
33mAutomated Testing for Web-based Systems on Embedded Devices
05mDesign, UX & Advanced PWAs highlights