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

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

That ratiogang.com guy. EVMavericks #123.

🧐

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.