# YCode for Airtable

**URL:** <https://air.tableforums.com/t/ycode-for-airtable/556>\
**Category:** Airtable Questions\
**Created:** [April 27, 2023, 4:10pm UTC](https://air.tableforums.com/t/ycode-for-airtable/556 "2023-04-27T16:10:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bfrench](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/bfrench/32/46_2.png) [@bfrench](https://air.tableforums.com/u/bfrench)\
**Post date:** [April 27, 2023, 4:10pm UTC](https://air.tableforums.com/t/ycode-for-airtable/556/1 "2023-04-27T16:10:48Z")

</div>

I think I may have [mentioned this](https://preview.mailerlite.io/emails/webview/171/86618968556569908) a while ago - maybe on an Opensiders call. Back then, they had no Airtable support but the ability to create fast and clean UIs seemed like a good one to watch.

- Ycode’s integration with Airtable allows you to access your data **without the need for any third-party tools**.
- The integration is **real-time** , meaning your data is always up-to-date.
- With Ycode’s **custom design** capabilities, you can create stunning designs for your Airtable data without any limitations.
- Best of all, this integration is available in **all Ycode plans, including the Free plan**.

If you’re still groping for the perfect front end, this one might be a winner.

In the context of front-ends for Airtable, is it me, or is there more talk about Airtable in the background and other stuff in the foreground? Is this an early indication of a broader movement?

---

<div class="post-metadata">

**Author:** ![Kuovonne](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/kuovonne/32/17_2.png) [@Kuovonne](https://air.tableforums.com/u/Kuovonne)\
**Post date:** [April 27, 2023, 4:35pm UTC](https://air.tableforums.com/t/ycode-for-airtable/556/2 "2023-04-27T16:35:44Z")

</div>

> [@bfrench](#):
>
> - Ycode’s integration with Airtable allows you to access your data **without the need for any third-party tools**.

Of course, Ycode itself is a third party tool. Or Airtable is a third party tool, depending on how you look at it.

> [@bfrench](#):
>
> The integration

Looks like they use personal access tokens and not oAuth. If I understand Airtable’s comments correctly, they prefer that 3rd party tools use oAuth, but they cannot stop you from using personal access tokens.

> [@bfrench](#):
>
> your data is always up-to-date

I suppose they are doing a fresh read with every page load. I suppose that is how they (and every other portal) deals with expiring attachment urls.

> [@bfrench](#):
>
> If you’re still groping for the perfect front end

The price looks nice. Haven’t seen what it is like to limit members to viewing their own data and only allowing conditional edits.

> [@bfrench](#):
>
> In the context of front-ends for Airtable, is it me, or is there more talk about Airtable in the background and other stuff in the foreground? Is this an early indication of a broader movement?

I think there are a lot of third party front-ends for Airtable because

- The more people who use Airtable, the more people want to share access to their Airtable data.
- Airtable’s native interfaces are not a solution for external users. Interfaces is too expensive and the styling is too limited.
- Airtable’s API is so darn easy to use

---

<div class="post-metadata">

**Author:** ![bfrench](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/bfrench/32/46_2.png) [@bfrench](https://air.tableforums.com/u/bfrench)\
**Post date:** [April 27, 2023, 6:45pm UTC](https://air.tableforums.com/t/ycode-for-airtable/556/3 "2023-04-27T18:45:32Z")

</div>

> [@Kuovonne](#):
>
> Ycode itself is a third party tool. Or Airtable is a third party tool, depending on how you look at it.

Or, it’s a first-party tool that uses a number of back-end third-party databases. 😉

---

<div class="post-metadata">

**Author:** ![Kamille-Parks](https://avatars.discourse-cdn.com/v4/letter/k/90ced4/32.png) [@Kamille-Parks](https://air.tableforums.com/u/Kamille-Parks)\
**Post date:** [May 9, 2023, 2:34pm UTC](https://air.tableforums.com/t/ycode-for-airtable/556/4 "2023-05-09T14:34:11Z")

</div>

I tried YCode several months ago and found it to be frustratingly buggy, but it was still in beta at the time. I’ll give it another look!

---

<div class="post-metadata">

**Author:** ![bfrench](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/bfrench/32/46_2.png) [@bfrench](https://air.tableforums.com/u/bfrench)\
**Post date:** [May 9, 2023, 3:31pm UTC](https://air.tableforums.com/t/ycode-for-airtable/556/5 "2023-05-09T15:31:57Z")

</div>

Don’t get your hopes too lifted. It still has bugs, but it’s better. I have a brother-in-law who was an idiot. I helped him reshape his worldview, but he’s still an idiot. In contrast, YCode will get better and likely stay better.

I see YCode as a bell weather, not an ideal choice per se.

But the future of database front and back-ends will probably be a story of fragmentation. YCode may serve only to help us understand what’s next. Glide has certainly demonstrated this to a degree. So, with that, here is why things like YCode and Rowy (as an example) will dovetail nicely with AGI.

**Opinion** : The idea of monolithic no-code platforms that include both front and back ends may have run its course. If you anchor the best database UI to the most limiting back-end, you end up with Airtable. Finding corollaries is also effortless.

Fact: Many aftermarket platform buyers (Stacker, Softr, etc) typically have one attraction; a front-end that meets business requirements that Airtable doesn’t. The backend is fine; security, web access, etc., not so much.

**Fact** : Many delighted Airtable customers seek out pathways to meet high(er) data ceilings. They want (generally need) a different back-end. This is where Rowy rises to overcome Airtable’s low operating ceilings.

**Fact** : AGI shows signs that it can build information tools through careful descriptions. As primitive and clunky as these early experiments are, there is a pattern that can be extrapolated into near-term disruption. GPTPlugins are already demonstrating near-instant manifestations of rudimentary CRUD apps using SQL.

**Probable Fact** : Rowy is architecturally able to be “programmed” by AI to build a great back-end dynamically. Airtable is not.

**Fact** : YCode is architecturally able to be “programmed” by AI to build a front-end dynamically. Airtable is not.

**Fact** : Google App Sheet is a microcosm of this trend; a no-code front-end designer coupled with a back-end of your choosing from SQL to NoSQL, BigQuery, spreadsheet, and Firebase.

**Opinion** : No-code front-ends and back-ends will flourish in the coming years. It will become a race of specialists. No-code solutions will transition into best-of-breed components beginning with the fundamental decision point - Which front-end and back-end do I choose for this project?
