Author: Wojciech Sowa

 The first part of my Google AppSheet tutorial offered a basic understanding of how to create a new app based on a data table using the Google AppSheet platform. You should know how data sources work, and be aware of the rules you need to follow to make the whole development process smooth. But it's easy to see that when it comes to functionality and visuals, the application created in step one still has a long way to go. In this article, I'll show you how to make it even more functional. 

I’ll start with some basic theories. I’ll introduce you to the Data tab, and explain what you can do with the various sections you’ll find inside. Later on, I’ll show you how to put that knowledge to good use – I’ll present three examples of specific changes that can be made to your sample app to improve it in several areas. In short, you’ll learn how to use AppSheet to better effect.

AppSheet is a no-code framework offered by Google, which is to say it’s a technology that allows people who aren’t software developers — but rather specialists in other fields — to seamlessly build professional web applications. The important thing here is that the app creators don’t have to write code (hence the term “no-code”). This idea is called Citizen Development, and it has gained popularity in recent years. 

Google AppSheet replaced the old Google App Maker. It’s worth noting that it’s a part of Google Workspace — which means that the applications you create can leverage other areas of the Google ecosystem (such as the popular Google Cloud Platform). The assumption here is very simple: if the organization has implemented the Google Workspace package, then its employees should be able to build a fully functional application for an internal or external user — based on AppSheet — which directly draws from the data processed in the company. Is this assumption true? Let’s find out how functional and complex AppSheet web apps can really be.