Hacker News Reader

> the way they’ve implemented search in paginated results is the most actively hostile UX decision I’ve ever encountered

Who is the "they" in that sentence? Each AWS product team writes their own console UI, as far as I know, and they're free to do pagination however it makes sense for them.

(Of course my question doesn't really matter because they're all pretty middling.)

View on HN

I don’t know but the behavior seems consistent across services. When there are multiple pages of results for something (running ECS services, whatever) if you filter the results it doesn’t coalesce the results, you have to just keep clicking through multiple empty pages, sometimes dozens of times, before finding a result that matches the filter, or even know if anything matches.

Most of the underlying APIs don’t have any concept of filters and most do pagination and will only return a maximum of 50 results. Given those limitations, it’s the best you can do on the UI.

They're in control of the API, so it's still a ridiculous excuse.

And even if they can't change the API, the front-end could request the next page from the API until they have a full page to display.

Reply on news.ycombinator.com