2 ms·
Something tells me we're seeing more of this partly because of graphql and its first class spec to infinite scrolling. So no - I don't think the decision came f
by jehlakj 4y ago
Something tells me we're seeing more of this partly because of graphql and its first class spec to infinite scrolling. So no - I don't think the decision came from none other than the programmer who do this. And to be quite honest, UX designers I've worked with don't really dictate this kind of stuff. Heck, some don't even know how the scrolling works in their own designs when asked about it!
- kgeist 4y agoHeh, in a feature we're about to release, infinite scrolling was indeed dictated by the programmers, as it makes the API cleaner and somewhat more scalable ("incremental loading of data with an opaque next page token" as opposed to "go to page 80 and I don't care if it takes forever/complex archirecturally to make it fast/consistent"). We could have added a "load more" button but it looks somewhat terrible on mobile.