Lay the sheet out as a table
App builders read a sheet as a table: the first row holds column names and each row below is one record. AppSheet’s own help says it works best that way, and warns that extras such as drawings and charts can cause trouble.
- Keep the headings in row 1, with no title above them and no merged cells.
- Give each subject its own tab, such as Customers, Jobs and Invoices.
- Add an ID column so that a row can still be found after its name changes.
- Use Data > Data cleanup > Trim whitespace and Remove duplicates, after working on a copy.
- Add dropdowns with Data > Data validation for columns with a fixed set of choices, so spelling stays consistent.
Start with the smallest thing that works
If you mainly need people to add records, try Google Forms first. Each response lands as a new row, and nobody can overwrite someone else’s work. In a form, choose Responses > Link to Sheets.
When people only need to read part of the sheet, protected ranges and filter views go a long way. They are under Data too, and they cost nothing.
AppSheet: Google’s no-code builder
AppSheet is the natural first try, since it comes from Google and describes itself as a no-code platform. From your sheet, go to Extensions > AppSheet > Create an app. It reads the first tab, makes a table from it, and generates a working app you can preview on the spot.
You then refine it by setting column types, adding other tabs as tables, and defining views and actions. Your data stays in the sheet, so people can still edit it directly, and that remains a risk: renaming a column can break the app.
Glide and similar builders
Glide is another builder that starts from a spreadsheet, with Google Sheets and Excel files named on its home page. People often choose such tools for how the finished app looks. Compare current plans before settling on one, since limits on users and data are usually what decide the cost.
Apps Script: code inside your sheet
Every Google Sheet has Extensions > Apps Script, a place to write small JavaScript programs that act on the sheet. It is well suited to automation, such as sending an e-mail when a status changes or building a weekly summary.
Here is a small example that sends a reminder for every row marked Overdue:
function remindOverdue() {
const rows = SpreadsheetApp.getActive().getSheetByName('Invoices').getDataRange().getValues();
rows.slice(1).forEach((r) => {
if (r[3] === 'Overdue') MailApp.sendEmail(r[1], 'Invoice reminder', 'Invoice ' + r[0] + ' is overdue.');
});
}Set it to run on a schedule under Triggers. The catch is that a script somebody wrote three years ago is hard to maintain once they’ve moved on, so leave notes about what it does.
When the sheet itself becomes the limit
Google allows up to 20 million cells in a spreadsheet, which sounds like plenty, but sheets slow down well before that when they are full of formulas and lookups. Size is rarely the first thing that hurts, though. These usually come first:
- Anyone with edit access can change or delete anything, and you may only notice much later.
- You can’t easily give each person a view of only their own rows.
- Rules live in people’s heads, so nothing stops a bad entry.
- Links between tabs depend on lookups that break when rows move.
If several of those sound familiar, read signs you have outgrown your spreadsheets. The data can move to a database, with an app in front of it.