Panel debate: Day 2

on YouTube ↗36m

" summary

Progressive web apps win concrete scrutiny: background geolocation is not a thing yet so a web app plus a thin native layer is recommended for tracking; Ionic’s move to compiled web components yields dramatic size and speed gains—Ionic compiled components are six to eight times faster—and more teams adopt component compilers (Stencil, Svelte). Payments move forward with the web payments API enables seamless checkout. Feature flags and testing in production enable rapid rollouts; a native editor experiment fails, prompting a pivot.

AI-written summary · about

" chapters (14)

1. 0:00Panel debate intro
2. 1:47Progressive vs native apps
3. 3:10Choosing PWA over native
4. 6:18Progressive enhancement
5. 7:00Done > perfect
6. 9:06Docs and design systems
7. 11:54Tools closer to users
8. 14:23Accessible specs
9. 17:54Admitting defeat
10. 20:23Rapid prod testing
11. 23:40Web components future
12. 29:21Web billing payments
13. 32:09Better sketching tips
14. 35:22Closing remarks

" related talks

• 40mProgressive Web Applications: when “progressive” sounds ironicDenis Kondratev · HolyJS 2025 Autumn
• 53mFuture of Frontend PanelMinko Gechev, Daniel Roe, Alexander Lichter, Anthony Fu, Ryan K Carniato · DevWorld 2024
• 39mDesigning great progressive web appsNicole Saidy · NDC Oslo 2017
• 51mGoing Web NativeA.Mahdy Abdelaziz · DevConf.CZ 2019
• 38mProgressive Web Applications: The What, the Why and the HowRadu Enuca · Voxxed Days Frontend Bucharest 2019
• 41mProgressive WebAda Rose Edwards · ffconf 2016
• 06mThe future of the webIstván Szmozsánszky "Flaki" · RuhrJS 2016
• 33mBuilding apps that are on FIREMariko Kosaka · View Source 2017