# Using Search in a Choice Component

**URL:** <https://community.glideapps.com/t/using-search-in-a-choice-component/71593>\
**Category:** General\
**Created:** [March 11, 2024, 5:22pm UTC](https://community.glideapps.com/t/using-search-in-a-choice-component/71593 "2024-03-11T17:22:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [March 11, 2024, 5:22pm UTC](https://community.glideapps.com/t/using-search-in-a-choice-component/71593/1 "2024-03-11T17:22:23Z")

</div>

In the following case, the phrase “search to find more” in the choice component may seem odd to users who rely more on visual colors rather than using the search bar. I agree that it would be better as an expand button. Search only speeds up the selection process, but it is not the essence of the choices component, which is to display options.

 ![IMG_2087](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/a/6ab17cc48ef5cc0f065b527cf7da2a619624316a.jpeg)

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [March 11, 2024, 5:51pm UTC](https://community.glideapps.com/t/using-search-in-a-choice-component/71593/2 "2024-03-11T17:51:36Z")

</div>

Couple thoughts:

- You could change your choice component to display the color name, but write the hex value. That would make it a bit easier to search by having actual color names.
- A bit of a workaround would be to instead show a slide in screen with a collection of colors instead of a choice component, then change the action on that collection to write the chosen color to a column in the user profile. Then you could grab the chosen color from the user profile.

---

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [March 11, 2024, 6:04pm UTC](https://community.glideapps.com/t/using-search-in-a-choice-component/71593/3 "2024-03-11T18:04:40Z")

</div>

1. Yes, that partially solves the issue. However, I prefer reducing the color options until the phrase mentioned earlier no longer appears. I’m sure you understand my point from the user’s perspective.

2. I’ve done that before, but it feels like taking up too much space just for one choice.

It’s okay, Jeff. I brought this up for feedback rather than looking for a workaround.

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [March 22, 2024, 3:23pm UTC](https://community.glideapps.com/t/using-search-in-a-choice-component/71593/4 "2024-03-22T15:23:08Z")

</div>

> [@Himaladin](#):
>
> Search only speeds up the selection process, but it is not the essence of the choices component, which is to display options.

I hear you re: search, but I’d also argue that infinite scrolling in a dropdown menu isn’t a good experience, either. 🙂

I’d go with Jeff’s suggestion of a slide-in screen for displaying a “gallery” of choices when you’re prioritizing visuals.

Appreciate the feedback, as always!

---

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [March 22, 2024, 3:59pm UTC](https://community.glideapps.com/t/using-search-in-a-choice-component/71593/5 "2024-03-22T15:59:54Z")

</div>

What are your thoughts on the in-app-filter feature in the collection component? I still prefer it to be more of a “choice” that offers options rather than hiding them. Making it concise is a challenge. Additionally, you should be aware that when opening a slide-in within a form, Glide actually closes the form view. This is poor UX because users are likely to be confused.

Another issue I’ve encountered is that when you provide an option to expand, it should always be accompanied by a collapse option. This is still found in chat components placed within a slide-in page or in notes from the classic app. Why create a “show more” button without providing a “show less” button?  
This is just my feedback that you may consider.
