I find creating either a flow or an advanced flow on the web UI a nicer experience because the text search lets me get to what I want faster than menu navigation on the app.
That said, it is unfortunate that the filtering appears to be done by looking for the exact search string as a substring of available options. A simple alternative is splitting the search query into keywords by whitespace and search for entries that contain all of them.
Example:
- If I input “motion”, the search lists cards such as “motion alarm turned on”.
- If I then append “on” to have “motion on”, the current logic returns nothing because no card contains “motion on”.
- If we had this suggested change, “motion alarm turned on” would match this query (but some entries without “on” would not, making it faster to find what one is looking for).
Demonstration of current behavior:
In my experience this is a handful lines of codes to change, a trivial change that improves UX.
