# Introducing GlideOS

**URL:** <https://community.glideapps.com/t/introducing-glideos/87253>\
**Category:** Announcements\
**Tags:** glideos\
**Created:** [June 4, 2026, 4:00pm UTC](https://community.glideapps.com/t/introducing-glideos/87253 "2026-06-04T16:00:51Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [June 11, 2026, 9:31pm UTC](https://community.glideapps.com/t/introducing-glideos/87253/19 "2026-06-11T21:31:33Z")

</div>

I was able to do similar things and other vibecoding tools, so I assumed Glide West could do it as well. It did take a bit of prompting, but eventually got it working (the biggest hurdle was that the API is not well documented).

When I recommend perhaps is to create a standalone utility app (Glide) these instruments) whose only purpose is to fetch data from the API and sync the data tables.

Since data is shared across all apps in a singular project, you can dedicate this app to syncing data, and the other apps can just be user interface

---

_[View the full topic](https://community.glideapps.com/t/introducing-glideos/87253)._