That's Your Website, Not Your App
Building an app that feels Native, no matter the language
Native apps used to win on speed and features. That gap has closed: faster WebViews, Web Push on iOS, WebAssembly, and phones quicker than old laptops. So why build an app at all? And why do so many apps still feel like websites, with a spinner on every screen and a retry button the moment the connection drops?
This isn't a talk about languages. Swift, Kotlin, Dart, TypeScript, and NativePHP can all ship a great app, and all of them can ship a website in an app costume. The difference is patterns. Web habits like fetching on load, treating the URL as the state, and trusting the server as the only source of truth don't fit a place where users expect something else. Loading, selection, animation, push, and navigation gaps are symptoms of one question: where does the state live?
Open slides fullscreen ↗ 34 slides · arrow keys or swipe