Which Glide should you open?
Open Glide Classic if you want the visual builder that turns tables into screens and forms. GlideOS is a separate builder that starts from a prompt or file. It has its own account and plans.
If you already have an app in the current Classic builder, you can keep working there. Glide says there is no seamless move to GlideOS and the two platforms do not share app data. A separate, much older mobile app format also used the name Classic Apps. Its 2025 retirement did not shut down the current Glide Classic builder.
How could you turn a spreadsheet into a gear checkout?
Start with two fictional equipment loans. Each row should say what was borrowed, who can see that loan and whether the item is out or returned. In Glide Classic, the data editor holds those rows and the layout editor decides what people see.
- Start in an empty draftCreate a fresh, unpublished app with its own Glide Table. Type in fictional rows instead of connecting your team’s spreadsheet. Check that the draft is not linked to an existing table and has no actions that message people or update another service. If you cannot verify that, do the exercise on paper.
- Separate the two loan recordsGive each fictional borrower a different email in the owner column, then set that column as a Row Owner. Write down that each person should see only their own loan. Leave the owner field out of anything a borrower can edit.
- Follow one changeChange one fictional loan to Returned in the draft and confirm the other stays Out. If you later use a paid, isolated test app, choose Private and restrict sign-in to the Users table. Before publishing, replace the placeholder owners with two test email addresses you control and that qualify under your plan. Put the same addresses in the Users table. Sign in separately as each tester. Each should see only the loan with their email. The editor’s view does not prove what a tester can see.
What keeps one borrower from seeing another loan?
Use a private app to control who can sign in. Use Row Owners to control which rows a signed-in person can receive. A screen filter only changes what is shown.
An owner column can match the email a person uses to sign in. Glide prevents that account from receiving rows it does not own. Adding a second owner column gives either owner access, which can be useful for staff but widens who can see the whole row. Keep information for a shared equipment list separate from individual loan records.
What changes when you publish a Classic app?
Free lets you build and preview a draft. Publishing requires a paid plan. The published app opens at a web address, so check its privacy settings before giving anyone the link.
Classic turns on automatic publishing for layout edits by default. Turn it off if you need to prepare screen changes before releasing them. Treat the layout and the records separately: turning it off is not a reason to edit a table other apps or people still use.
In the November 2026 Classic plan comparison, Explorer includes one published app, 100 personal users and 250 updates. Maker adds Google Sheets sync and allows unlimited personal users. If coworkers need to sign in with business email addresses, check Business rather than assuming those addresses count as personal users.
An update is a usage unit. Classic typically counts things like syncing a Google Sheet, using an outside service or calling its API. Ordinary edits to a built-in Glide Table usually do not count. A spreadsheet upload is a snapshot; paying for live sync is a separate decision.
What can you take with you from Glide Classic?
You can export selected columns from a Glide Table as a CSV, a file most spreadsheet programs can open. That gives you records to move. The app screens, access rules and actions still need to be recreated if you switch tools.
Open a sample export before relying on it. Glide omits empty columns and calculated columns that link to other tables. Write down how those values are made and keep copies of any original files you need. A spreadsheet export alone does not recreate the way the app behaves.