Amen. Twitter[1] and Starbucks[2] have both built gorgeous PWAs in the last couple of years that are perfect replacements for 98% of a native app's functionality. It can be done, people!
1. https://blog.twitter.com/engineering/en_us/topics/open-sourc...
2. https://twitter.com/davidbrunelle/status/905931990444244995
Re:Start with a Website, Not a Mobile App
by charleslmunger on Saturday January 05, 2019 @12:28AM
(#18830088)
Twitter's mobile web site is the most unreliable site I encounter with any frequency. Fully 80% of the links I get to Twitter fail to load, telling me to try again, which only works when I fully refresh the page.
I don't know how it compares to their native app.
Re:Start with a Website, Not a Mobile App
by lowercased on Friday January 04, 2019 @05:21PM
(#18828265)
Done in-house, I'd bet, and that's another disconnect to overcome.
Outsourcing website and/or mobile dev to external company, the focus is often more going to be on whizbangflashy, vs sleek/slim/fast/simple, to justify whatever budget they're getting.
I do find that I end up using the mobile web client for twitter as often as i do the native client. It's not much in either case, but the mobile web client is generally 'good enough' such that if that's where I land, I don't feel a need to jump to the native client.
People have forgotten that you can build a website that isn't a user-hostile SPA train-wreck.