Live data from Hacker News

Making Instagram.com faster: Part 3 – cache first

instagram-engineering.com

21–30 of 72 posts

Re: Making Instagram.com faster: Part 3 – cache first

#21
post #15

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.

I could see that being a problem for facebook.com as people would likely choose one vs the other.

Re: Making Instagram.com faster: Part 3 – cache first

#22
post #5
post #4

Earlier 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.

I'm using iOS and started seeing it pop up like 2-3 weeks ago.

Re: Making Instagram.com faster: Part 3 – cache first

#23
post #7

> 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

#24
post #7

> 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

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

#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…

Yeah, without constant focus on perf, things regress extremely quickly. We're building tight integration with perf budgets into our infra & dev workflows across both Instagram and Facebook, so that any perf regressions will be intentional tradeoffs with product experience rather than unfortunate accidents :)

Re: Making Instagram.com faster: Part 3 – cache first

#27

Earlier 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.

Might have been an earlier version we were testing before we built out the new posts pill, this feature went through several iterations.

Re: Making Instagram.com faster: Part 3 – cache first

#28
post #15

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.

You're probably talking about the desktop web version I assume. If you check out the mobile web version its actually pretty close features wise, theres direct messaging, stories, creation with webgl filters,etc. The desktop version of these is admittedly lagging behind though - but I'm optimistic that desktop will get some more love in future :)

Re: Making Instagram.com faster: Part 3 – cache first

#30

Does 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.

Can't reveal the exact numbers, but yeah - a lot of people use IG on web :) Mobile web was always the big focus for us though - most people assume its just a desktop only web version, but actually the mobile web version is much more fully featured than the desktop version.
Post reply on HN