# A new way to show data 🆕
Hello **Fellow Gliders** 🛝
I’m excited to share a versatile **Swipe Cards Collection** I created using an **AI Component** and **JSON**. Though it might remind you of Tinder, its applications are extensive. This post will show you what it does and guide you through the implementation.
# First, here is the baby
# Fine-tuning
You can change anything you want in it by asking the AI to make so changes. **Remember** that the AI in the Glide AI Component doesn’t remember previous message. It only know the current message context and the code already in place. So make sure to do good prompts.
# JSON Configuration
Create the needed columns in your desired table. By using my default AI Component, here is the columns configuration and the JSON Object.
Then, you need to create a **joined list** and a **template** to make a **JSON Array** of all the rows. You can use **query column** before joined list if you need to **filter the data**.
# Likes Counter
You can now create, if needed, the likes counter.
Create a likes-dislikes table.
Then, create the relation.
# Context
Add a _user-specific_ **text column** that will store current Card JSON object in it to be able to execute action in the right row context from the AI Component.
# AI Component
You first need to create the variables and actions:
- For the user id, you can use row id of the users table. For the example, I forgot to create the row id, so I used email instead.
Then paste:
```html
Do exactly this :
```
# Happy Gliding! ⚡🔥
Hope you like it! Feel free to comment or ask any questions. 🙂
---
> [@MaximeBaker](#):
>
> Then, you need to create a **joined list** and a **template** to make a **JSON Array** of all the rows.
hehe, you’re still doing this 🙂
Have you actually tried using a Lookup like I suggested last time?
Save yourself a column, and the bonus is that the Lookup is “JSON aware”, where a Joined list is not.
---
It’s a nice collection style. We could try to think of good use cases for it in a business setting.
I love it how Glide removed the custom code component and this is the answer 😆
---
I usually
1/ ask to add the data fields to the DOM (header)
2/ create component with this exact same code
{{write the code in the body minus the first 2 div}}
I always find this process to avoid waisting time if you remove step 2/ the data fields are kept safe
---
Now that we’ve got this feature can you give us a share link?
> [@Beta: Share & reuse AI Custom components](https://community.glideapps.com/t/beta-share-reuse-ai-custom-components/81038):
>
> We’re testing a new capability to let you share, reuse, and import AI Custom components between Glide apps. Here’s a quick demo from Christian, our lead designer on the project: The feature is in Public Beta. Our team is watching this thread, so please give it a try, and reply with whatever feedback you have. Learn more in our [Glide docs for the AI Custom component](https://www.glideapps.com/docs/essentials/components/ai-custom#sharing-and-importing-ai-custom-components): Thank you! folded_hands
---
> [@fk1214](#):
>
> Now that we’ve got this feature can you give us a share link?
>
> [Beta: Share & reuse AI Custom components](https://community.glideapps.com/t/beta-share-reuse-ai-custom-components/81038)
There you go:
> **[Untitled - Glide custom component](https://components.glide.info/share/commit::15e8a422-5cfa-40eb-5644-ffee5f065e8c)**
>
> Custom component created in Glide
---
Thank you! It takes forever if I just paste “Do exactly this:” and a lot of code in the component, luckily we have this now so we could share components much easier 😅 With a little tweaking I made a more TikTok-ish style feed for an app [Snapverse](https://community.glideapps.com/t/snapverse-share-your-moments/80928) 🎉
---
Well, yes.
I couldn’t say for sure, because generally I don’t use the AI component.
But the fact is a JSON Array created via a lookup does return valid JSON, and it works perfectly fine if you subsequently use it in a JSON Template, Call API, Trigger Webhook, or whatever. So if the API component can’t handle it, to me that points to the API component.
---