Live data from Hacker News

Making Instagram.com faster: Part 3 – cache first

instagram-engineering.com

31–40 of 72 posts

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

#31

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.

I just tried. Why can't I upload shit from the website? I tried changing my user agent and clicking the new upload button that appeared and it didn't work (possibly because it was a video?)

What's the point of making a website if it's crippled compared to the mobile app?

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

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

Similar to Twitter and other social apps. Agreed that it's a very annoying experience.

The worst possible implementation of the “Loading” screen.

It’s like Flash of Unstyled Content, but instead it’s Flash of Useless Content Killed.

Or something with a similarly appropriate acronym.

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

#33

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.

Since you're here, can I ask - is it intentional, when using IG on the web, if I click on a photo on someone's profile page, the comment section is auto-scrolled to the bottom instead of showing the description?

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

#35
post #31

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.

I just tried. Why can't I upload shit from the website? I tried changing my user agent and clicking the new upload button that appeared and it didn't work (possibly because it was a video?) What's the point of making a website if it's crippled compared to the mobile app?

To funnel people towards the native app with more analytics capabilities...

...I presume, at least.

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

#36

Earlier quoted context omitted.

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.

I just loaded Instagram and it did this. It’s probably not something you see because you open the app multiple times a day. You definitely run into it when you only open the app a few times a week.

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

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

I don't use instagram, but I use FB mobile and this same behavior exists on there, and I echo this sentiment.

I have 1000+ connections on FB, built out over the past 15 years (I started using FB in college when it was a college network); which is to say, I'd never be able to fully read everything every one of my connections have posted because there are too many. Sometimes I see an interesting post as I'm scrolling, start reading it, and everything changes (sometimes it waits until I click into the comments of a post, and go back, and then everything changes, which is arguably worse because now I can't refer back to the original post...). If I didn't make a mental note of who created that post, it's lost forever. If I remember who posted it, at least I could search for that person, and scroll down on their feed.

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

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

seems broken on my copy. I see the same as the GP post a lot. Maybe this is not the cause.

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

#39

Earlier quoted context omitted.

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.

I saw it the other day, but I might not have the most up-to-date copy of the app

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

#40

Earlier quoted context omitted.

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.

I see the "new posts" pill if I've scrolled down into the cached content at all, but if I'm just looking at the first post I see the behavior everyone else is describing. It's still pretty annoying.
Post reply on HN