🌪 Use Multiple Choice Components to Filter an Inline List

It still applies as of now because it’s viewed as an “edit”. External sources consume “edits”, plus “syncs”.

Thanks. The whole charging per update is ridiculous especially on their own Glide tables. I can sort of see the sync part to external sources but “internal” updates? WTF. No other word for it than a very bizarre business model where you punish your users for using your products most basic feature.

Shame but I really can’t take this as a serious product for deployment - so thanks for the quick response - so I can stop wasting my time. Bizarro.

The whole charging per update is ridiculous especially on their own Glide tables. I can sort of see the sync part to external sources but “internal” updates? WTF. No other word for it than a very bizarre business model where you punish your users for using your products most basic feature.

I have no way to disagree with this. Counting any write to USC as an edit makes no sense to me and makes it hard to create smart and customized solutions.

I hope and think that Glide team is thinking in a workaround for this situation soon.

Shame but I really can’t take this as a serious product for deployment

Don’t go so far, Glide is improving every 3-4 months and some mid-complex deployments can be developed easily in next months.


I know nothing about Glide’s cost structure. If I had to guess though, I would say one of the variable costs of Glide directly related to the product/tech is the amount of computation that happens across the projects of Glide developers. Glide probably runs its own servers, maybe uses AWS or things like that, and the cost of a gazillion bits computed in a project is higher than if only a few bits are computed. This assumption could be wrong, correct or somewhere in between. Gide’s pricing in part based on syncs and edits would then simply reflect this, the cost of computing data. So until Glide is big enough, it does not shock me that Glide passes on some of its technical costs onto the customer.

The below from Glide’s CEO might help to understand:

Glide is built on top of Google Cloud, where we pay for each time we create, edit, or delete your app’s data. Do you think Google is “punishing” us for using their cloud?

We don’t view Google as punishing us–that’s just their business model, and it’s ours too. Maybe you think that editing data in Glide Tables is free for us to do, so it should be free for you? It is not free.

We expect you to pay for Glide if you use it seriously, and the more you use it, the more you should pay–it definitely costs us more when you use Glide more! If this seems like a ridiculous idea to you, then I don’t know what to tell you–it’s how most businesses on the internet that aren’t driven by ad revenue work.


Hi @david,

May I kindly ask that you also address the question or uncertainty around the use of USC and why they are counted towards updates…
This is a real concern not only for @Robert_Petitto but for many and it was highlighted a couple of times in the thread about the new plans…
Are there still talks around it and if so, when can we expect some form of feedback. Before it was not much of an issue because quotas were not enforced but I think now Glide is at a stage of enforcing quotas. I hope we can have a general response or commitment to this rather than User specific solution (Pardon the pun) “Inbox me type of solution”. Thanks


we could still use multiple choice filters inside edit forms with no updates counted … right?

Correct. Add, Edit, and Form screens do not write any data until the form is submitted.


As expected, Glide uses Google Cloud like firebase or indeed firebase. I also see storage and change billing in Firebase or Firestore.

I think the way Glide works is like this.
Glide uses React and Styled-components as frameworks and PubSubJS, HowlerJS and core-js as their JavaScript libraries and largest storage Google Cloud.

Glide doesn’t make apps without code for free but wants to build a large and mutually beneficial community.

I’m honestly very happy with Glide, even custom CSS and HTML are not available on other no-code Appbuilder platforms. :laughing:


Simple genial, genial simple! Congratulations!
Nevertheless I have one caveat: mltiple choice can be done substantially more simple!
Instead splitting entries separated by commas, you can use INCLUDES!
Multiple choice filter “AL,FL” includes both AL and FL records! :slight_smile:

While that is true, you need to be careful. If your choices could include AL, AAL, FL, FFL and a user chose AAL and FFL, then the include would be picking up the wrong rows. Not only the rows with AAL and FFL, but also the rows with AL and FL because AL is included in AAL. You just need to make sure that none of the choices have similar characters.

Of course, I am aware of that. I am using that in my app for recording and presenting children injuries for the column “Injury circumstance”, such as fall, drawning, hit by object, traffic etc. In such case there is no risk of such mistake.

Another topic: is Glide aware of one funny bug in multiple choice? It doesn’t function when entries end with the space!?

1 Like

in addition, thie problem can be mitigated very easy: if you have “AL,AAL,FL,FFL” (there are no spaces after commas!), you can convert this in “,AL,AAL,FL,FFL,” and also to search it not with original entry “AL”, but with “,AL,” instead! Here you have in theory the jeopardy if you have real commas in your data, but I think this is negligeable!

1 Like

Yeah, I’m sure they are aware. I’ve seen glide suggest that people should check for spaces, so Im not sure if they view it as a bug or not.

1 Like

“works as designed”! :slight_smile:
This is defitively the bug!

1 Like

Hi, Robert. Thank you for this tutorial.

I’ve watched the last version and I loved it. It’s a simpler and more elegant solution than showing and hiding a lot of inline lists. It really helped me simplified my app. Thank you very much! :clap: :clap: :clap:

Now, I was having second thoughts about what you say in the video at 2:55 - filtering the screen with “Email is signed in user” -, so I tried not to, and it works fine.

Please help me if I’m wrong here: since the choice is stored in a user-specific column in the Users table, it only affects the signed-in user, not the other signed-in users, nor the not-signed-in users.

Something really important is that if you put the specific user colum for the selected choice in the Users table, only the signed-in users will see the choice component. The anonymous users won’t be affected by the filter, and even more: they won’t see it, the component does not display in the screen.

In my case, that resulted positive, because now the filter is a “feature for members”, but for others maybe it can be an inconvenience.

So, when you want every user to have this filter functionality, you have to store the specific user column for the selected choice in your data table, and not in the Users table. I think in that case your saying in the video is right: then you do have to filter the screen with “Email is signed-in user” or else your choice will affect to every user in the app.

Can you please take a look and tell me if I’m right or wrong? Thank you in advance

1 Like

You’re right. This is assuming that your users are signed in to the app. If you don’t have signed in users, you’d have to create a working table, use user specific columns, and then bring in those values using single value columns rather than a template column.


That was fast! :grin:

Yes, I was making it that way with my old filter for everyone. Thank you again!

All this is amazing, but can this apply to the Website format? (not app).
I cannot even make it work for a single filter…