# List Filtering - is it done on the server side or the client?

**URL:** <https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320>\
**Category:** Database\
**Created:** [January 20, 2022, 4:44pm UTC](https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320 "2022-01-20T16:44:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdamF](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/adamf/32/15564_2.png) [@AdamF](https://forum.adalo.com/u/AdamF)\
**Post date:** [January 20, 2022, 4:44pm UTC](https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320/1 "2022-01-20T16:44:09Z")

</div>

As I launch my app, I see performance considerations to be important in the design. One area I am having trouble is when filtering a list (reverse-scroll / auto-refresh enabled) that compares a DB timestamp to the current timestamp.

My question: is the filtering shown in the below pic done on the server or are all messages sent to the mobile device and then filtered. I hope its the first case, but can someone confirm?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/adalo/original/2X/5/598663d601fd83ad7ee2120108515c3c3e133748.png)

Bonus question: Any advice for filtering large lists that compare the list content to the current time? When the list gets too large, I seem lose the ability to scroll up on iOS.

---

<div class="post-metadata">

**Author:** ![Yongki](https://avatars.discourse-cdn.com/v4/letter/y/7c8e57/32.png) [@Yongki](https://forum.adalo.com/u/Yongki)\
**Post date:** [January 20, 2022, 8:23pm UTC](https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320/2 "2022-01-20T20:23:42Z")

</div>

Hi @AdamF ,

Take a look at this post.

> [@Reverse scroll + Lazy Loading: how to make it work?](https://forum.adalo.com/t/reverse-scroll-lazy-loading-how-to-make-it-work/15956/12):
>
> Hi @Victor , @afonso , @StevenU Thank you for bringing this up, so it triggers me to implement paging in message list. You can test them, if you like. To change the number of messages in list, it is in Edit Profile By default, when new user sign up, this property is filled with 20. Please let me know if there is something you are not hoping.

I am still optimistic that if configured properly, we can achieve optimal result.

---

<div class="post-metadata">

**Author:** ![AdamF](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/adamf/32/15564_2.png) [@AdamF](https://forum.adalo.com/u/AdamF)\
**Post date:** [January 20, 2022, 10:08pm UTC](https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320/3 "2022-01-20T22:08:14Z")

</div>

Thanks for the link; I have seen it and I have paginated as much as I can.

Might you know if the filtering is client-side or server-side?

---

<div class="post-metadata">

**Author:** ![Yongki](https://avatars.discourse-cdn.com/v4/letter/y/7c8e57/32.png) [@Yongki](https://forum.adalo.com/u/Yongki)\
**Post date:** [January 20, 2022, 10:55pm UTC](https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320/4 "2022-01-20T22:55:10Z")

</div>

My guess would be server side if you use relationship such as current parent\>child, but it will be client side if you use all data then filtered.

---

<div class="post-metadata">

**Author:** ![AdamF](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/adamf/32/15564_2.png) [@AdamF](https://forum.adalo.com/u/AdamF)\
**Post date:** [January 21, 2022, 1:53am UTC](https://forum.adalo.com/t/list-filtering-is-it-done-on-the-server-side-or-the-client/22320/5 "2022-01-21T01:53:25Z")

</div>

Thanks for the interaction. I am reluctant to make DB changes from just guessing. I am hoping that the custom Filters - for speed - would still operate on the Server side, but your guess is the other way. Can anyone confirm with confidence which way it would go?

I just reconfigured my DB to drop relationships as using the external API with relationships was proving problematic.
