Guides / Building Search UI / UI & UX patterns

The infinite list is a very common pattern to display a list of results. This pattern has two variants:

  • With a button to click on at the end of the list of results
  • With a listener on the scroll event that is called when the list of results reaches the end

Vue InstantSearch can cover those two different implementations. The former is covered by the built-in ais-infinite-hits widget and the latter is covered by the ais-infinite-hits connector. This guide focuses on the second implementation using the Intersection Observer API. A browser API is used in the example but the concepts can be applied to any kind of infinite scroll library. You can find the complete example on GitHub.

Note that the Intersection Observer API isn’t yet widely supported. You may want to consider using a polyfill. Here the compatibility table to find more information about its support.

Display a list of hits

The first step to creating an infinite scroll component is to render the results with the ais-infinite-hits connector. There’s an external Hit component but it’s not the point of this guide, the intent is to keep the code simple. You can find more information about the connectors API in the dedicated guide about widget customisation.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<template>
  <ol v-if="state">
    <li v-for="hit in state.hits" :key="hit.objectID">
      <slot name="item" :item="hit"> </slot>
    </li>
  </ol>
</template>

<script>
import { createWidgetMixin } from 'vue-instantsearch';
import { connectInfiniteHits } from 'instantsearch.js/es/connectors';
export default {
  mixins: [createWidgetMixin({ connector: connectInfiniteHits })],
};
</script>

Track the scroll position

Once you have your list of results, the next step is to track the scroll position to determine when the rest of the content needs to be loaded. For this purpose, the Intersection Observer API is used. To track when the bottom of the list enters the viewport, a “sentinel” element is observed. This trick is used to avoid observing all the items of the results. You can reuse the same element across the different renders. You can find more information about this pattern on the Web Fundamentals website.

You can use the vue-observe-visibility library to determine when the sentinel is visible.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
<template>
  <ol v-if="state">
    <li v-for="hit in state.hits" :key="hit.objectID">
      <slot name="item" :item="hit"> </slot>
    </li>
    <li class="sentinel" v-observe-visibility="visibilityChanged" />
  </ol>
</template>

<script>
import { createWidgetMixin } from 'vue-instantsearch';
import { connectInfiniteHits } from 'instantsearch.js/es/connectors';
export default {
  mixins: [createWidgetMixin({ connector: connectInfiniteHits })],
  methods: {
    visibilityChanged(isVisible, e) {
      console.log(isVisible, e);
    },
  },
};
</script>

<style scoped>
.sentinel {
  list-style-type: none;
}
</style>

Retrieve more results

Now that you can track when you reach the end of the results, you can use the showMore function inside the callback function onSentinelIntersection. But you should only trigger the function when you still have results to retrieve. For this use case, the connector provides a prop isLastPage that indicates if you still have results to load or not.

1
2
3
4
5
6
7
8
9
10
11
<script>
export default {
  methods: {
    visibilityChanged(isVisible) {
      if (isVisible && !this.state.isLastPage) {
        this.state.showMore();
      }
    },
  },
};
</script>

Go further than 1000 hits

By default Algolia limits the number of hits you can retrieve for a query to 1000; when doing an infinite scroll, you usually don’t want to go over this limit.

1
2
3
$index->setSettings([
  'paginationLimitedTo' => 1000
]);

Disabling the limit doesn’t mean that you can go until the end of the hits, but just that Algolia will go as far as possible in the index to retrieve results in a reasonable time.

Now you should have a complete infinite scroll experience.

The complete source code of the example is on GitHub.

Did you find this page helpful?