Free testing
US$0
Prototype and test with up to 10 users before deployment
No-code business app builder connecting spreadsheets, data capture and workflow automation.
Choose it if
Operations teams building inventory, inspections, job tracking or approval apps around structured data, particularly in Google Workspace organisations
Skip it if
You need an unrestricted public consumer app with confidential accounts, highly custom interfaces, or a field workflow that assumes every media type works offline
Starting price
Starter US$5/user/month; Core US$10/user/month; eligible Google Workspace users may already have Core
Build and test with up to 10 users at no cost; free testing is not a general production licence
Decision checklist
Google AppSheet fits work that already has a recognisable data structure: inventory items, inspection records, jobs, customers or approval requests. Instead of asking staff to navigate a large spreadsheet, an app can give them a focused form, an assigned-work list and the information needed for the next action. The first design task is deciding what each record represents and how records relate to one another.
For a field-inspection workflow, start with a table of sites and a separate table of inspections. A technician records the site, result and photograph; a supervisor reviews exceptions. Build that complete handoff before adding more views. AppSheet uses spreadsheet-like expressions for business logic, so no-code does not remove the need to understand your data and conditions.
The lowest AppSheet pricing tier is not always the right baseline. Core adds security filters and scheduled events that matter when staff must see only their own jobs or when a reminder must run at a set time. Enterprise Plus becomes relevant when the required data connection or organisation-wide governance is outside the standard connector set.
Before purchasing, check whether the users already have Core through their Google Workspace edition. AppSheet counts unique users across deployed apps, and the creator’s licence tier affects the entitlement users need. A covered employee and an external contractor are not automatically the same licensing case. Map the intended audience before rolling out an app beyond the original test group.
An AppSheet offline app must first open while online so its definition and data can be downloaded. Decide whether changes should queue until a deliberate sync or synchronise automatically when connectivity returns. A field team needs a simple routine for preparing devices before departure and confirming that captured records have reached the backend afterward.
Offline support has specific boundaries. A device can capture GPS coordinates, but the Google map view is not available offline. Images and documents need appropriate caching, and browser-based capture has different persistence limitations from the mobile workflow. Test the actual device, file type and network interruption expected on a job; do not treat an offline switch as a guarantee for every feature.
A view that displays only assigned jobs is not a complete access-control design. Core security filters evaluate which rows are included in the app, and requiring sign-in lets you define access around the current user. The underlying data source also needs appropriate protection. Consider what happens when an employee changes role or a contractor’s assignment ends.
Data capacity is another early decision. Starter and Core AppSheet databases currently allow 2,500 rows per database, while Enterprise Plus raises that allowance to 200,000. Those are AppSheet database limits, not a universal limit on every connected source. If the app will collect a new record for every inspection or movement, estimate growth and choose the data source before the initial store fills up.
Gemini for App Creation can suggest tables, columns, views and actions from a description of a business process. It is available on paid AppSheet accounts, including eligible Workspace Core users. Check its proposed schema against the real process: which fields are mandatory, what identifies a record and which role may approve a change? These decisions determine whether the resulting app is useful in daily work.
Include Glide when comparing another approach to data-centred apps, and Bubble when a more custom application experience is the main goal. If the problem is primarily connecting services rather than providing a user-facing app, compare n8n as a different kind of automation solution. AppSheet is most compelling when structured data, controlled access and repeatable staff actions belong in the same workflow.
Starting price: Starter US$5/user/month; Core US$10/user/month; eligible Google Workspace users may already have Core. Model: Per-user Starter, Core and Enterprise Plus; separate per-app Publisher Pro for suitable public apps.
Worked exampleA team of 12 unique users needing Core security filters pays US$120/month (12 x US$10), or US$1,440 across 12 months, if none already has an eligible entitlement. If all 12 are covered by a qualifying Workspace edition, the incremental Core licence purchase is US$0, excluding the existing Workspace bill and other services. Multiple Core apps used by the same 12 people do not automatically double the user count.
US$0
Prototype and test with up to 10 users before deployment
US$5/user/month
Basic apps and automation; standard data connectors; no security filters
US$10/user/month or included for eligible Workspace users
Advanced app features, scheduled events and security filters; standard data connectors
US$20/user/month
Broader enterprise data connectors, governance and priority support
US$50/app/month
Unlimited public users for apps without sensitive data, sign-in or security filters
Count unique app users across deployed apps, not only the people who build them. The app creator's licence tier determines the required user entitlement. Core is included in qualifying Workspace editions for domain-verified users; do not purchase duplicate coverage. External access and User Pass require a separate entitlement review. Publisher Pro uses per-app pricing and is unsuitable for confidential user-specific data. Data-source, messaging or other connected services may add charges.
Closest alternative: Glide. Here is how the shortlist compares on price and fit.
| Compare | Google AppSheet |
Glide | Adalo |
Bubble |
|---|---|---|---|---|
| Best for | Operations teams building inventory, inspections, job tracking or approval apps around structured data, particularly in Google Workspace organisations | Operations teams building lightweight internal tools, directories and workflow apps from structured data | Founders and small teams building booking, membership, directory or marketplace-style apps with a visual interface and managed database | Founders and agencies building custom portals, marketplaces or workflow apps that need a visual database and business logic |
| Starting price | Starter US$5/user/month; Core US$10/user/month; eligible Google Workspace users may already have Core | Free; Explorer US$19/month billed annually | Free to build and test; Starter US$36/month equivalent, billed annually at US$432 | Free development plan; Web Starter US$32/month or US$29/month equivalent billed annually |
| Free plan / trial | Build and test with up to 10 users at no cost; free testing is not a general production licence | Free plan for learning and small personal apps | Free plan: unlimited test apps and screens, 500 records per app, 1 editor; no production publishing allowance | Free development version; eligible new apps can access a 14-day Starter trial subject to activation rules |
| Biggest limitation | Per-user entitlement and sync design constrain deployment: sharing with external users can require additional licences, while offline use depends on cached data and supported content types. | Usage, user and update limits make the cost less predictable as an app grows | No editable source-code export: moving the application logic to another platform requires a rebuild rather than a simple code handoff. | Workload measures backend resources, not a predictable number of users; inefficient queries and repeated workflows can raise consumption without increasing customer value. |
Prices are taken from each vendor's own pricing page on the dates shown. Taxes and add-ons may apply; confirm before you buy.
The public offer is for building and testing with up to 10 users. When deploying a business app, confirm the required subscription or Workspace entitlement; the testing allowance is not a blanket free production licence.
Not if the same 12 unique users use both apps within the applicable tier. Count distinct users across deployed apps. Creator tier, external users and organisational policies still affect eligibility.
The official subscription guidance includes Business Starter, Standard and Plus for domain-verified users. Confirm the user's entitlement and admin settings before purchasing separate Core licences or sharing externally.
It can capture GPS coordinates when supported by the device, but Google map data is not cached for offline map display. Open the app online first and test its configured sync and content behaviour.
A filtered interface is not a substitute for row-level security. AppSheet security filters require Core or above; require sign-in and protect the underlying data source as well.
No. It is the current limit per AppSheet database on Core. Connected sources have their own limits and performance behaviour; do not apply that number to every source or assume large spreadsheets will sync quickly.
We read pricing and plan limits from Google AppSheet's own pages (listed above) on the dates above. Where a vendor does not publish a price we can verify, we say so rather than estimate. Spotted something out of date? Tell us.
Profile updated · facts checked 7 Oct 2026
