I’m making an app for young adults, a guide to all the local bars, with the option to filter bars for your choice. For example, I want my users to be able to somehow filter the list of all the bars on one screen to only show e.g. cheap bars, bars in “this” area, lively bars, top rated bars etc.
How is this done the easiest way? I’m thinking the bars in the database all must have tags and information if theyre cheap/close/lively etc. Then I need some sort of option to update the list of bars in real time, to only show the certain bars the user just chose. Would it be easier to do this option via a dropdown menu or with toggle buttons, or some other way?
I’m a new creator and English isn’t my first language. If you don’t understand something, please ask me down below and I’ll explain it.
I hope someone here has experience with this. Thanks in advance guys!
What I want is to let my users activate multiple filters, which the dropdown menu the article above uses does not support (it seems like).
Furthermore, this way of doing it (according to the link above) doesn’t let my users actively change the filter to what suits them the best (it seems like).
I would prefer a way where the users could select multiple filters to actively change the bars that show up to them from a list. I found a component called “MultiSelect Dropdown”, however, I haven’t quite understood how to use the feature I’m talking about with it…
Do you still know any other ways? Maybe there is some way to do this but it takes a long time and it is not integrated in any component right now? If so, I would be more than happy to hear your way of doing this even if it will take countless of hours. It’s the key feature in my app
Although what you want is technically achievable, (to have users have “preferences”), it will be very time consuming to make the workarounds necessary to achieve that goal. My strong advice for now is to build something more simple, limiting the functionality of these filters and then get feedback from your users on it.
It is easy to assume what your users may want but often, if they can still achieve what they wanted without with the bells and whistles, they tend to not miss them