AppSheet No-Code Platform: How Citizen Developers Build Enterprise Apps

The clearest published example of what a no-code platform does to an organisation is Globe Telecom, a telecommunications company in the Philippines. Google reports that Globe’s own employees built more than 200 applications, that the programme delivered $6.7 million in savings in its first year of implementation, and that the net economic impact was expected to increase 38% year on year.

Globe’s frontline app — the one staff use to handle customer requests, track inventory and resolve issues — is the one Google attaches a process figure to: “This has helped them reduce business process turnaround time by 79.8%.”

It is worth being precise about what that number is. It is Google’s own published figure for one app at one customer. Google does not publish the baseline, the measurement window or the method, so it belongs in the “vendor-reported result” column rather than the “independent finding” column. We are citing it because it is the best-sourced figure available, not because it settles anything.

That is the shape of the opportunity: non-technical staff — “citizen developers” — building the mobile and web apps they need themselves, rather than queuing for a development team. This guide covers how AppSheet does that, what it costs, and where the approach runs into limits.

The No-Code Paradigm Shift: Democratizing App Development

Traditional application development requires specialised programming skills, database expertise and software development lifecycle knowledge — capabilities concentrated in IT departments whose queue of requests routinely exceeds their capacity to deliver. The practical effect on a small or medium business is that an internal tool worth building never gets built: the work sits behind whatever is already prioritised, and the business settles for a manual process or an off-the-shelf product that does not quite fit.

You will see confident figures quoted for the average length of that queue. We could not trace any of them to a primary source, so we are not repeating one here. The pattern will be familiar enough to anyone who has asked for a simple data-capture tool and been given a date next quarter.

No-code platforms remove the programming step by replacing it with configuration: a business user connects a data source and adjusts the app the platform generates for them. Google’s published customer examples give a sense of the volume this unlocks. At Lixil, Google reports that employees across teams created about 850 applications within a year. At Globe Telecom it was more than 200. Those are counts of apps built, not measures of their quality or of time saved — but they do establish that the building is being done by people who are not developers.

What none of this means is that no-code is free. Licensing is per user per month and scales with headcount, the apps still need maintaining, and a badly modelled spreadsheet produces a badly behaved app. The honest case for no-code is not that it is cheaper per app in the abstract. It is that it puts the building power in the hands of the person who actually understands the process, and shortens the distance between noticing a problem and having something that addresses it.

How AppSheet Works: From Data to Deployed App in Hours

AppSheet’s core innovation is automatic app generation from data sources: users connect spreadsheets, databases, or cloud storage containing their business data (customer lists, inventory records, project tasks), and AppSheet automatically generates a functional mobile/web app with forms, tables, and workflows based on analyzing the data structure. This “data-first” approach eliminates the blank-canvas problem plaguing traditional development where builders must manually design every screen and interaction.

The platform operates through three core components: data connectors, app editor, and automation engine. Data connectors integrate with sources including Google Sheets, Excel, Cloud SQL and other SQL databases, Salesforce, Airtable and custom REST APIs — meaning businesses can build apps on top of existing data rather than migrating to new systems. AppSheet’s AI analyzes connected data, automatically inferring data types (text, numbers, dates, images, GPS coordinates), relationships between tables, and appropriate UI components (forms for data entry, galleries for browsing, charts for visualizing metrics). For example, connecting a Google Sheet with columns [Employee Name, Department, Leave Start Date, Leave End Date, Status] automatically generates a leave request app with submission forms, approval workflows, and calendar visualization—no manual configuration required for basic functionality.

The app editor provides visual customization: business users modify automatically generated apps through intuitive point-and-click interfaces, adding conditional logic (“If overtime hours exceed 40, require manager approval”), calculated fields (“Total Cost = Quantity x Unit Price”), and workflow actions (“When order status changes to ‘Shipped’, send customer notification email”). AppSheet’s expression language enables sophisticated logic using Excel-like formulas rather than programming syntax — anyone comfortable with Excel’s SUM() and IF() functions can implement business rules without learning JavaScript or Python. This is the single biggest determinant of how far a citizen developer gets: the expression language is where an app stops being a form and starts enforcing how the business actually works.

The automation engine (AppSheet Automation, formerly Bots) enables event-driven workflows: when specific conditions occur (new form submission, data changes, scheduled time), the system automatically executes actions including sending emails/SMS, updating databases, calling external APIs, generating PDF reports, or triggering other apps. Employee onboarding is the use most businesses recognise: when HR submits a new-hire form, the automation can write records into connected systems, email the equipment request, add orientation to a calendar and send the welcome pack — the steps that otherwise get chased by hand and occasionally forgotten. That is an illustration of the mechanism rather than a customer result; we have no measured before-and-after figure for it and are not going to invent one. What it shows is that AppSheet reaches past data collection into workflow orchestration.

Key Capabilities Enabling Enterprise-Grade Citizen Development

While AppSheet’s ease of use makes it accessible to non-developers, the platform provides enterprise-grade capabilities addressing security, scalability, offline functionality, and integration requirements that distinguish it from consumer-oriented no-code tools. Four capabilities particularly enable business-critical application development: offline-first architecture, role-based access control, workflow approvals, and Google Workspace integration.

Offline-first architecture enables mobile apps to function without internet connectivity—critical for field workers in remote locations, warehouses with poor WiFi, or industrial environments. AppSheet apps automatically sync data when devices reconnect, queuing offline changes and resolving conflicts through last-write-wins or custom merge logic. For an Australian business this is usually the capability that decides whether the project is viable at all: a plumber in a basement, a technician on a rural site or a driver in a steel-framed warehouse has no usable signal, and an app that requires connectivity to save a form will simply be abandoned in favour of the paper it replaced.

Two things to check before relying on it. Conflict resolution defaults to last-write-wins, which is wrong for any workflow where two people might edit the same record from the field — you need to decide that behaviour deliberately. And offline image capture is the most common cause of sync problems, because photographs queue locally and need bandwidth the device may not get for hours.

Role-based access control (RBAC) implements data security through granular permissions: different user roles see different data, access different features, and execute different actions within the same app. A sales pipeline app might show sales representatives only their own opportunities while managers view entire team pipelines, and finance sees all opportunities but can only edit commission fields. AppSheet RBAC integrates with Google Workspace, Microsoft 365 and custom identity providers, inheriting existing organisational permissions rather than requiring separate user management.

The limitation worth understanding: AppSheet security filters decide which rows reach the device, and anything that reaches the device is on the device. Filtering for tidiness in the interface is not the same as withholding data, so a filter is not a substitute for a security rule when the data is genuinely sensitive.

Workflow approvals implement multi-stage review processes: requests requiring approval (expense reports, leave requests, purchase orders) route to designated approvers based on business rules (amounts, departments, requestor hierarchy), with configurable escalation, delegation and audit trails. The audit trail is the part that tends to justify the project on its own: an approval chain that lived in email has no reliable record of who approved what and when, which is a problem the first time anyone asks.

Google Workspace integration provides seamless connectivity to Gmail, Google Calendar, Google Drive, Google Sheets, and Google Meet—leveraging tools Australian businesses already use. AppSheet apps can send Gmail notifications, create calendar events, generate Google Docs reports, store files in Drive and launch Meet calls directly from app workflows. A quality-control app shows why this matters: an inspector flags a defect, and the app can generate the incident report with its photographs, notify the responsible manager, put the review in a calendar and file the documentation in Drive — without the business buying a dedicated quality management system. Whether that is sufficient depends on your compliance obligations, which is a question to settle before building rather than after.

Implementation Best Practices and Citizen Developer Success Patterns

Successfully scaling citizen development with AppSheet requires balancing user empowerment with governance, keeping apps maintainable and compliant while avoiding the “shadow IT” problems that plagued earlier grassroots technology adoption. Three things consistently separate the programmes that last from the ones that produce a pile of abandoned apps: structured training, reusable templates, and IT-led governance. These are our own observations from client work, not findings from a published study.

Structured training programs transform interested business users into capable citizen developers through progressive skill development: an introductory workshop on building an app from a spreadsheet, an intermediate session on expressions and workflows, and advanced training on security and integration. Expect roughly a day’s training in total, split across the three.

The part most programmes skip is what happens afterwards. Training produces people who can build a simple app and then hit the expression language, and without somewhere to take that problem they quietly stop. A standing clinic — even a fortnightly half-hour with someone who knows the platform — does more for completion rates than extending the initial course.

Reusable templates and components accelerate development while ensuring consistency: IT creates pre-built app templates for common use cases (inspection checklists, asset tracking, expense requests) that citizen developers customize rather than building from scratch. These templates embed organisational standards for branding, security configuration and data practices, reducing variance and compliance risk. The reason to invest in them is not speed, though starting from a template is faster than starting from nothing. It is that a template is where you put the security rule you want every app to have, so that getting it right once means getting it right everywhere — rather than auditing thirty apps built thirty ways.

IT-led governance frameworks establish guardrails preventing shadow IT problems while preserving citizen developer agility: IT defines data access policies (which databases citizen developers can connect), deployment approval workflows (peer review for apps accessing sensitive data), and monitoring dashboards tracking app usage and performance. Google’s AppSheet administration console enables centralized management: IT can inventory all organisational apps, audit data connections, enforce security policies and retire unused apps — the visibility that prevents the sprawl and security gaps of earlier bring-your-own-technology movements.

The model that works is trust-but-verify, and the line is drawn by data rather than by app: anyone can build and test freely against non-sensitive data, and an app that touches customer records, payment details or anything carrying a regulatory obligation gets a security review before it goes live. Drawing the line at the data keeps the review queue short enough to actually happen, which a blanket approval requirement never does.

The Future of Work: Citizen Development Becoming Baseline Capability

You will find a lot of analyst forecasts quoted on this subject — some version of “by year X, N% of enterprise applications will be built by non-IT staff”. We went looking for the primary source behind the most widely repeated of them and could not establish one: the figure and the target year both change depending on which secondary site is citing it. So we are not quoting a forecast. The direction of travel is clear enough without one.

What is observable is narrower and more useful. Google’s own customer examples show hundreds of applications being built per organisation by people who are not developers. That is not a prediction about 2030; it is a count of apps that exist.

The real competitive effect is about distance, not speed multipliers. The person who notices that the proof-of-delivery process loses a form a week is the person doing it, and in a traditional model their observation has to survive being written up, prioritised, scheduled and interpreted by someone who has never done the job. Citizen development removes most of that distance. That is the whole mechanism, and it does not need a statistic.

For Australian small and medium businesses, this is the first time the apps have been within reach at all. A logistics operator with a few dozen staff can have a route and proof-of-delivery app that works, built by someone who already understands the run, for a licence fee rather than a development budget. The constraint has moved from capital to attention: the question is no longer whether you can afford the app, but whether anyone in the business has time to build and maintain it.

Frequently Asked Questions: AppSheet No-Code Development

What is AppSheet and who can use it?

AppSheet is Google’s no-code platform for building mobile and web apps without programming. You connect a data source you already have — a Google Sheet, an Excel file, a SQL database — and AppSheet generates a working app you then adjust. It is aimed at the operations manager, sales rep or HR specialist who understands the process, not at developers. If you can write an Excel formula, you have the skill it asks for.

How much does AppSheet cost for businesses?

AppSheet publishes tiered per-user pricing: a free tier for prototyping and personal use, Starter at US$5 per user per month, Core at US$10 per user per month and Enterprise Plus at US$20 per user per month. There is also Publisher Pro at US$50 per month per app for apps published to users who do not each need a licence. Most businesses running production apps start on Core. Prices are in US dollars and are the published list rates at the time of writing — check Google’s pricing page before budgeting, and note that the per-user model means cost scales with the number of people using the app, not the number of apps.

Can AppSheet apps work offline without internet?

Yes. AppSheet’s offline-first architecture lets mobile apps work without connectivity, which is the capability field businesses depend on. Changes queue on the device and sync when it reconnects. Two cautions: conflict resolution defaults to last-write-wins, so decide that behaviour deliberately if two people might edit one record from the field; and queued photographs are the usual cause of sync trouble, because they need bandwidth the device may not get for hours.

How long does it take to build an app with AppSheet?

A basic app over an existing spreadsheet is genuinely a same-day job, because AppSheet generates the first version for you and the work is adjustment rather than construction. Apps with multi-stage approvals, integrations and security rules take appreciably longer, and the expression language is where the time goes. We are not going to quote a percentage against traditional development: the comparison depends entirely on what the app does, and the figures circulating for it are not traceable to a published study.

Is AppSheet secure enough for enterprise data?

AppSheet provides role-based access control, encryption, audit trails and integration with existing identity providers through Google Workspace and Microsoft 365, so it can be configured for sensitive data. Whether it is secure enough is a configuration question, not a platform question. The specific trap: AppSheet security filters control which rows reach a device, and whatever reaches the device is on the device — so filtering a view for tidiness is not the same as withholding the data, and should not be mistaken for a security control.

What types of business apps can AppSheet build?

AppSheet suits inspections, asset tracking, expense and leave requests, inventory management, compliance auditing, field service scheduling and quality control. The common thread is a process that is currently a form, a spreadsheet or an email chain, with a defined set of fields and a defined set of people who act on them. What it suits less well is anything needing a bespoke interface, heavy computation, or a public-facing consumer experience — those are still app development.

Do I need Google Workspace to use AppSheet?

No. Google Workspace integration is an advantage — Gmail, Calendar, Drive and Sheets connectivity makes workflows simpler to assemble — but AppSheet also connects to Microsoft 365, SQL databases including Cloud SQL and MySQL, Salesforce, Airtable and custom REST APIs, so existing business data works regardless of which platform you run.

Key Takeaways: AppSheet & No-Code Revolution

AppSheet moves app building from a specialist activity to something the person who owns the process can do themselves. That is a real shift, and it is worth separating from the marketing around it.

What is actually established:

• Volume is real. Google reports more than 200 employee-built applications at Globe Telecom and about 850 within a year at Lixil. Those are counts of apps that exist, built by non-developers.
• One published savings figure. Google reports $6.7 million in savings in Globe Telecom’s first year, with net economic impact expected to grow 38% year on year. This is the vendor’s own reported number.
• One published process figure, narrowly scoped. Google states Globe’s frontline app “helped them reduce business process turnaround time by 79.8%” — one app, one customer, with no published baseline or method.
• Pricing is public and per-user. Starter US$5, Core US$10, Enterprise Plus US$20 per user per month; Publisher Pro US$50 per app per month. Cost scales with users, not apps.
• The capabilities are genuine but need configuring. Offline-first sync, role-based access control, approval workflows and Workspace integration all work — and each has a default (last-write-wins conflicts, row filters that still deliver data to the device) that you need to set deliberately.

What we could not establish:

Widely circulated analyst figures on no-code adoption, cost reduction and development speed could not be traced to a primary source, and the commonly quoted forecasts disagree with each other on both the number and the year. We have left them out rather than repeat them. If a figure matters to your business case, insist on seeing the source.

The honest summary: no-code does not remove the work, it moves it. You trade developer time for configuration time and a per-seat licence, and you gain the thing that is genuinely hard to buy — the person who understands the process being the person who can change the tool.

---

Sources

1. Google Workspace. AppSheet grows: no-code app development for everyone — Globe Telecom (200+ employee-developed apps, $6.7M first-year savings, 38% year-on-year projected impact) and Lixil (~850 apps within a year). https://workspace.google.com/blog/productivity-collaboration/appsheet-grows
2. Google Workspace. Giving more customers access to AppSheet — Globe Telecom frontline app, “reduce business process turnaround time by 79.8%”. https://workspace.google.com/blog/product-announcements/giving-more-customers-access-appsheet
3. Google AppSheet. Pricing — published per-user tiers. https://about.appsheet.com/pricing/
4. Google Cloud. AppSheet documentation — platform capabilities, data sources, security and automation. https://cloud.google.com/appsheet/docs

---

Revised 26 October 2026. This article previously contained operational and financial figures attributed to a number of named companies, along with research findings attributed to several analyst firms and a reference list, none of which we could verify against a primary source. They have been removed. Everything retained above is either traceable to the sources listed or identified in the text as our own observation.

Mobile is one pillar of a complete digital strategy. Ash Ganda writes about aligning technology investments — cloud, web, and mobile — for business growth.

Part of the Ganda Tech Services family, Awesome Apps delivers specialist mobile app development for Australian small and medium businesses.