I have an app (iOS) that outputs a grid with all the applicable products.
Is there a prevalent design pattern that indicates the end of infinite scroll?
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
When the user scrolls to the end of a list, you want to:
Communicate that the end has been reached. You don't want the user to wonder whether more items are loaded, or whether the page is still loading.
Suggest the next step!!! This is an important opportunity! The user has just interacted with the list so you know you have her attention. Moreover, you know it's likely that the user has finished looking at the list and is figuring out what to do next. This combination of (a) a captive attention and (b) user decision point can create a great opportunity to provide a call to action, more information, or a suggestion for one or more next steps!
In the top left example, the end-of-scroll just presents some passive information. The other 5 examples show how a UX designer might capitalize on the user's attention to create more interaction/stickiness:
The exact next step you suggest depends on your overall UX objectives, what behavior(s) you are trying to create for users, and what empirically is successful when you test (e.g. A/B testing a few different buttons may yield very surprising insight).
You could either simply display a line showing end of content. like below
There is a very popular ecommerce app called Myntra in India which does a very interesting thing. They show a quote by a famous fashion designer at the end of content Screenshot is Android, but they do the same thing on iOS.
Hope this helps!
[ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [ scroll ] [A] [B] [C]
Let user come to a distinct end and select among several infinite scolls.
To really make it infinite one button should be called