I wonder if they're ever going to bring the web version anywhere close to feature parity with the apps, or update the UWP app that's been abandoned for years.
Making Instagram.com faster: Part 3 – cache first
21–30 of 72 posts
Re: Making Instagram.com faster: Part 3 – cache first
#22Earlier quoted context omitted.
That was a common complaint but the newest version doesn't do that anymore. Instead of immediately loading the new content, you instead get a little hover button at the top of the feed that says New Posts - that you now click to load the new content. Because the old system was indeed super annoying, seeing something cool and then having it disappear in a long feed was annoying beyond belief. It's a small change with…
I was looking to make williamscales's very complaint as soon as I read this. Instagram's latest beta for Android 10 does not include this hover button. Maybe iOS only for now.
Re: Making Instagram.com faster: Part 3 – cache first
#23> we immediately present users with a cached copy of their previous feed and stories tray, and then replace it with fresh data once it’s available I vehemently HATE this pattern. I'm on a slow connection, and I open the app. Yay, I see some (cached) content. I start reading. After a random amount of time EVERYTHING CHANGES, and I can't get back to it. It's gone, for all intents and purposes, forever. I'd love to have…
Re: Making Instagram.com faster: Part 3 – cache first
#24> we immediately present users with a cached copy of their previous feed and stories tray, and then replace it with fresh data once it’s available I vehemently HATE this pattern. I'm on a slow connection, and I open the app. Yay, I see some (cached) content. I start reading. After a random amount of time EVERYTHING CHANGES, and I can't get back to it. It's gone, for all intents and purposes, forever. I'd love to have…
(Author here) To clarify, we don't actually replace it automatically - we show a pill notification that new stories are available. You can either choose to tap it and see the new feed, or ignore it and continue with what you were doing
Re: Making Instagram.com faster: Part 3 – cache first
#25> However, as the product grew, a side effect was that our web performance began to slow. Over the last year we made a conscious effort to improve this. We’ve [1] been advocating strongly for using performance budgets [2] as a means of protecting hard-earned performance improvements. There’s some depressing stat around performance regressions... something like 25-50% of big sites regress in performance 6 months after…
Re: Making Instagram.com faster: Part 3 – cache first
#26Re: Making Instagram.com faster: Part 3 – cache first
#27Earlier quoted context omitted.
(Author here) To clarify, we don't actually replace it automatically - we show a pill notification that new stories are available. You can either choose to tap it and see the new feed, or ignore it and continue with what you were doing
I have definitely had the "the thing I was looking at right after the app opened disappeared after a few seconds and I can't find it again" experience /u/mfontani describes.
Re: Making Instagram.com faster: Part 3 – cache first
#28I wonder if they're ever going to bring the web version anywhere close to feature parity with the apps, or update the UWP app that's been abandoned for years.
Re: Making Instagram.com faster: Part 3 – cache first
#29Because the comments side panel on pictures is probably the buggiest implementation of _anything_ i've ever seen.
Re: Making Instagram.com faster: Part 3 – cache first
#30Does anybody from instagram actually use instagram.com? Because the comments side panel on pictures is probably the buggiest implementation of _anything_ i've ever seen.