Another reason why PWAs don't work for daily consumer social apps: keyboard.

cc @rauchg

I’m convinced the gap in experience between a native mobile app and a mobile web app boils down primarily to user input at this point. 

The performance gap is illusory for most use-cases &amp; devices. Safari iOS handling of how a keyboard displays, the havoc it wreaks on the page,

Guillermo Rauch

Another reason why PWAs don't work for daily consumer social apps: keyboard.

cc @rauchg 

https://x.com/rauchg/status/1909962885910213046

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

EVMavericks #123. Professional $L taker. I’m not for everyone.

Bummer. WebKit doesn’t support VirtualKeyboard yet.

https://developer.mozilla.org/en-US/docs/Web/API/VirtualKeyboard_API

https://bugs.webkit.org/show_bug.cgi?id=230225

🧐

https://www.bram.us/2021/09/13/prevent-items-from-being-hidden-underneath-the-virtual-keyboard-by-means-of-the-virtualkeyboard-api/

https://developer.chrome.com/docs/web-platform/virtual-keyboard

If you find a reliable solution to “my fixed elements get treated like static elements” when the iOS keyboard is present then please let me know.