Implement grid sorting #149

Open
opened 2026-06-09 00:05:35 +02:00 by TheFantasticLoki · 3 comments
Contributor

Description

We need a feature to sort the list of results in browse especially by distance. Generally we already get people close by default but currently a lot of people closer to you will show far down the list buried in results over 100 km away. We can probably have sort by distance, by age, by height with low to high and vice versa. But this would be a pretty big QoL improvement compared to even the official app.

### Description We need a feature to sort the list of results in browse especially by distance. Generally we already get people close by default but currently a lot of people closer to you will show far down the list buried in results over 100 km away. We can probably have sort by distance, by age, by height with low to high and vice versa. But this would be a pretty big QoL improvement compared to even the official app.
Owner

This is a client side feature coming post-mvp. Currently the focus is to implement features available in the official app.

This is a client side feature coming post-mvp. Currently the focus is to implement features available in the official app.
hloth added this to the v0.1.0 (MVP) milestone 2026-06-09 15:07:50 +02:00
hloth modified the milestone from v0.1.0 (MVP) to v1.0.0 2026-06-09 15:07:55 +02:00
hloth added this to the Open Grind project 2026-09-27 01:31:35 +02:00
Owner

I propose a temporary semi-solution: introduce visible pages.

We already load profiles in batches of 600. As discussed, we can't just re-sort the entire grid on each new load, because that will cause jumps and confusion. Instead we could show these pages separated by a horizontal separator, then treat each page as its own sorted immutable list, and not re-sort.

I propose a temporary semi-solution: introduce visible pages. We already load profiles in batches of 600. As discussed, we can't just re-sort the entire grid on each new load, because that will cause jumps and confusion. Instead we could show these pages separated by a horizontal separator, then treat each page as its own sorted immutable list, and not re-sort.

Given that the vast majority of profiles do have a distance, and the biggest ballache is clutter from miles away....

Instead of trying to do any sorting which will always be compromised and clunky, could a first approach just be setting a simple client side distance limit, as each page loads from Grindr drop from the grid any profiles that are displaying distance exceeding the limit. I believe for the lightly loaded profiles you've got to wait until they fully load before getting distance anyway?

Even if 80% of the far away profiles were curtailed it'd bring a massive immediate benefit.

Given that the vast majority of profiles do have a distance, and the biggest ballache is clutter from miles away.... Instead of trying to do any sorting which will always be compromised and clunky, could a first approach just be setting a simple client side distance limit, as each page loads from Grindr drop from the grid any profiles that are displaying distance exceeding the limit. I believe for the lightly loaded profiles you've got to wait until they fully load before getting distance anyway? Even if 80% of the far away profiles were curtailed it'd bring a massive immediate benefit.
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
open-grind/open-grind#149
No description provided.