Reverse sort

[John F]

Originally Posted by davidfor

...

So, how do you know which direction it is sorted? ...

Some UIs use an up or down arrow, a caret, or actually have A - Z or Z - A.

And if I change to a different sort, which does it use?

I would say that each sort option has it's own sort order. After all, sorting A - Z doesn't make sense when sorting by most recent. This allows you to do things like sort by Author in one direction and titles within the author in another direction.

And if I am in the middle of the list and change the direction, which page gets displayed?

Basically, the same page.

And as you said, this is only an opinion.

[davidfor]

Originally Posted by John F

Some UIs use an up or down arrow, a caret, or actually have A - Z or Z - A.

It is amazing how many people do not understand what that little arrow is in the column header in Explorer. Or complain about why the order keeps changing.

"A-Z" and "Z-A" works for the names sorting, at least in English, but what about for the "Date added" or "Recent".

I would say that each sort option has it's own sort order. After all, sorting A - Z doesn't make sense when sorting by most recent. This allows you to do things like sort by Author in one direction and titles within the author in another direction.

That is not what I meant. If I tap "Size" twice to get to small-to-large and then change to "Author". When I change back to "Size", which order should the list be in?

Basically, the same page.

So, if I am on page 25 of 100 when I tap the reverse sort, I should still be on page 25 of 100. Or should I be on page 75 showing roughly the same books as I was viewing?

I don't know the answers to any of the above. But those are the sort of things that go through my mind when considering changes.

[John F]

Originally Posted by davidfor

...

I don't know the answers to any of the above. But those are the sort of things that go through my mind when considering changes.

Sure, and to me, they can be quickly resolved or the question not even mentioned.

Again, IMO.

[Semwize]

Originally Posted by davidfor

for someone to suggest that.

This is the standard implementation of list sorting. When you wrote about the complexity of the interface, clearly implying the addition of extra items, I was very surprised...

[JSWolf]

Originally Posted by davidfor

I was wondering how long it would take for someone to suggest that.

So, how do you know which direction it is sorted? And if I change to a different sort, which does it use? And if I am in the middle of the list and change the direction, which page gets displayed?

These are complicating the interface. The complication might not always be visible, but, there are complications in how to use it.

My opinion, and that is all it is, my opinion, is that it isn't needed. Because the lists all wrap, it is easy to get to the other end and see what it there. And what you suggest needs two taps and what I suggest is either a swipe or one tap.

There is a solution to this (IMHO). Only allow the sort order to be changed if the list is at the first screen.

[compurandom]

Originally Posted by John F

Sure, and to me, they can be quickly resolved or the question not even mentioned.

I think davidfor's point (and I agree) is that neither of us know the "correct" answer to these questions, and probably nobody will agree on what correct is.

And you can't "not mention" these questions, because they are fundamental to how the UI would have to work if sorting was added, and the UI can't be written without every one of these questions being decided in some way.

If that isn't clear to you, let me restate it. If you were writing the sort UI, and you decided not to answer any of these questions, you've already picked a default answer. And someone, no matter which answer you pick, is going to hate you for it.

[John F]

Originally Posted by compurandom

I think davidfor's point (and I agree) is that neither of us know the "correct" answer to these questions, and probably nobody will agree on what correct is.

And you can't "not mention" these questions, because they are fundamental to how the UI would have to work if sorting was added, and the UI can't be written without every one of these questions being decided in some way.

If that isn't clear to you, let me restate it. If you were writing the sort UI, and you decided not to answer any of these questions, you've already picked a default answer. And someone, no matter which answer you pick, is going to hate you for it.

I could live with the hate. And IMO, a company should be able to implement sorting.

[davidfor]

Originally Posted by Semwize

This is the standard implementation of list sorting. When you wrote about the complexity of the interface, clearly implying the addition of extra items, I was very surprised...

In that case, can you tell me what it is? And where the standard is published.

And, any time you add an option or a different way of doing something, you are complicating the interface. You should only do that with a good reason. Personally, as Kobo treats the list as continuous, I don't see the need to add more options.

[davidfor]

Originally Posted by John F

I could live with the hate.

What hate? I have only expressed an opinion. And asked questions to see what people are actually thinking about. That is part of my day job. When people suggest changes to the systems I maintain, I have to ask questions to know what they want. And to make sure that they actually know what it is that they want.

And IMO, a company should be able to implement sorting.

Sorry, but that statement is just silly. Kobo have implemented sorting. It works. There are no bugs in it (that I can think of). It is just that you think it should be done differently. Whereas I think the current options work well.

[John F]

Originally Posted by davidfor

What hate?

From the post before mine:

... And someone, no matter which answer you pick, is going to hate you for it.

... I have only expressed an opinion. And asked questions to see what people are actually thinking about. That is part of my day job. When people suggest changes to the systems I maintain, I have to ask questions to know what they want. And to make sure that they actually know what it is that they want. ...

I had a similar day job, but didn't find it necessary to go back to users for every little detail.

... Sorry, but that statement is just silly. Kobo have implemented sorting. It works. There are no bugs in it (that I can think of). It is just that you think it should be done differently. Whereas I think the current options work well.

You got me. I meant Kobo should be able to expand their current sorting.