Our application has a case where you can filter a list of projects with a checkbox to show only your projects. A few members of our development team have requested that state of that filter remain between navigations. That is, if I click a result of the filter and then return to the page that is filtering, my filter settings are retained.

We wanted to find the best practices from a user experience perspective for this sort of behavior.

Could someone point me in a good direction on this?

  • I don't understand I'm afraid. Your users have asked for a specific feature and have described what they want and why is a benefit, so what exactly do you need from us here?
    – JonW
    Commented Apr 17, 2019 at 18:10

2 Answers 2


Retaining the state of the filters is quite a common practice and is handled in the URL of the page using queryString parameters on the code side.

On the UX end, to keep the user experience smooth, the URL could just retain the filters while it is shared, and there is no need to change the UX for this. The filtering experience itself could be improved for one. However, if there is a need to make retaining filters more explicit, here are some examples:


You just described the solution in your question. Implement that solution and test it


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.