# Next page of topic list loading too late on mobile?

**URL:** https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476
**Category:** UX
**Created:** [22 ביוני,‏ 2018,‏ 12:07pm UTC](https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476 "2018-06-22T12:07:14Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [22 ביוני,‏ 2018,‏ 12:07pm UTC](https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476/1 "2018-06-22T12:07:14Z")

</div>

This has been bugging me for a while: At least on my mobile device (S7), I feel that when I’m scrolling down a topic list (e.g. /latest here on meta) the next page is starting to load slightly too late so that there is always a slight delay until I can continue scrolling. Not a smooth UX, in other words.

Since I have fast Internet and the device is not _that_ old, I’m thinking perhaps discourse could start loading the next bunch of topics just a bit earlier? Is anyone else having similar a experience?

P.S. I just realized that this also applies when scrolling through topic replies but I didn’t notice it that much since scrolling speed in topics tends to be a lot slower anyway, due to reading.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [22 ביוני,‏ 2018,‏ 12:49pm UTC](https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476/2 "2018-06-22T12:49:10Z")

</div>

> [@tophee](#):
>
> I just realized that this also applies when scrolling through topic replies

For posts we load half the normal amount in Android becausr most devices are slow.

---

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [22 ביוני,‏ 2018,‏ 12:52pm UTC](https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476/3 "2018-06-22T12:52:43Z")

</div>

> [@Falco](#):
>
> For posts we load half the normal amount in Android becausr most devices are slow.

That makes sense, but the question is: when is the loading process triggered?

Let’s say it’s triggered when there are 3 items remaining (have not entered the viewport), in that case, I’d suggest maybe to start loading already when there are still 5 items waiting for their turn.

---

<div class="post-metadata">

### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)
#### Post date: [21 באוגוסט,‏ 2018,‏ 5:49am UTC](https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476/4 "2018-08-21T05:49:45Z")

</div>

Isn’t anybody else experiencing this issue of scroll-lag?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [21 באוגוסט,‏ 2018,‏ 10:57pm UTC](https://meta.discourse.org/t/next-page-of-topic-list-loading-too-late-on-mobile/90476/5 "2018-08-21T22:57:46Z")

</div>

Yes its a bug in chrome **desktop** per:

> **[requestAnimationFrame based rendering](https://discuss.emberjs.com/t/requestanimationframe-based-rendering/14284/5?u=sam)**
>
> I made a small tweak to the snippet above to also add perf measures, so we can see whats happening in a trace: Ember.run.backburner.\_platform.setTimeout = function(method, wait) { var start = window.performance.now(); var i = Math.random(); ...

I can imagine this would be even more noticeable on Android and that it shares this bug.

Which reminds me… @xrav3nz when you start out can you help me get this reported to Chrome, there is a surprising amount of work in creating a good report here with a repro.
