|
|
|
|
|
by heleninboodler
2251 days ago
|
|
For extremely generous definitions of "works." I am constantly amazed at how long (and how many attempts) it often takes to load a single tweet page. The SPA-initializing state is usually measured in minutes on my iphone regardless of what kind of connection I'm on, and the result is often that message that the page failed to load because my browser made too many attempts. I don't know how you can possibly do this badly at delivering what should be the smallest web pages ever. My standard practice on mobile now is, no joke, take the URL of the tweet page I'd like to read and paste it into a new FB post because it's faster and more reliable to get FB to fetch preview the content than it is to load it with my own browser. (edit: and note this is while using FB in my mobile browser. Think about how much more complicated a FB page should be than a single tweet, and it's still 100x faster to load.) I've come to the conclusion that this is very intentional because they'd really like me to install the app and therefore have no incentive to improve the mobile experience, but I absolutely will not install an app for content that could very easily be delivered as a simple web page. I hope the trend of companies pushing their apps hard eventually reverses. |
|