I’d push back on this - the “native feel” obsession is largely a dev and designer thing. Users care about performance, reliability, and smooth interactions, not whether a button matches platform HIG. Nobody complains that web apps don’t use OS-native form inputs - users adapted years ago. Mobile is no different. Some of the most popular apps ship custom non-native UIs and nobody complains.
This misconception has a real cost: too many devs dismiss the WebView path outright. WebView’s bad reputation mostly comes from early hybrid frameworks that shipped unoptimized web apps in a shell - that was an implementation problem, not a WebView limitation. There’s a ton of optimization headroom there and nothing fundamental preventing it from being nearly indistinguishable from native - WebView engines improve with every OS release, Web APIs keep closing the gap, and platform conventions are converging. We’re planning to take this approach with Hologram after Local-First lands - same repo, same UI components across web and mobile.
