Transcript

Hailee Zapata:

Hello, everyone. Thank you for joining us today. We are really excited to have representation today from both Promevo and our newest partner, QREW Technologies.

Over the next 45 minutes, we're going to introduce AppSheet for Google Workspace. You're going to receive a live demo from QREW Technologies, and we're going to explain how to start using AppSheet within your organization. And of course we always have our Q and A session with our presenters at the very end.

So, I'd like to start off by introducing myself. I am your webinar host, Hailee Zapata. I'm the Alliance Marketing Manager here at Promevo. Promevo is a Google Premier Partner that sells, services, and builds Google products. We are 100 percent Google focused and we specialize in ChromeOS, Google Workspace, Google Cloud, and of course our own proprietary Workspace management tool, gPanel.

If you are only working with us on Google Workspace, you are just tipping your toe in all the solutions we can provide and help you with.

So let's meet our stars of the show today. Our presenters are Jeremy Brooks, who is our Senior Client Success Manager here at Promevo and the QREW subject matter expert, Austin Skidmore, who is the Director of Operations at QREW Technologies, and then Cameron Lupton, our Google Developer Expert.

And just a quick fact on QREW, they actually have six of the 14 total Global AppSheet Google Developer Experts and six of seven in the total North America. So Cameron is one of seven people in North America who is a GDE, which is completely awesome. We're super excited to have them here today.

All right, guys, go ahead and take it away.

Austin Skidmore:

Sweet. Thanks, Hailee. All right. Welcome, everyone. Glad y'all are able to make it today. Like Hailee said, I'm Austin from QREW Technologies, and I have Cam here, our Google Developer Expert.

So we're super excited to meet with you guys today. We've got lots of videos on our YouTube channel, if y'all want to check that out. And are interested in learning more about the ins and outs of AppSheet and what it is used for on a daily basis. But y'all can check that out at your own time and then yeah, I want to toss it over to Cam for a quick intro and then he'll get into our content for today.

Camron Lupton:

Awesome. Yeah. So I've been using AppSheet for around six and a half years, and that was long before the Google acquisition. And so we used to have our, what we would say a QREW, our wagon hooked up to a horse and then all of a sudden that horse became a Ferrari. The second they got hooked up to Google's rocket.

And so we'd just been, we'd been dragged behind since day one. We offer services of consulting of development, and then we also do training for people who desire to build apps themselves and AppSheets.

And what is AppSheet? AppSheet is a no-code, rapid app development platform. It's owned by Google and it synergizes really well with the rest of the like Google Workspace ecosystem and has a lot of native integrations to those.

And so it allows you like them having that position in the Google Workspace allows them to really easily make all those integrations to the third party. Google workspace apps because it's part of the same ecosystem. And so you're actually able to integrate with those with very low code or no-code options compared to a lot of the other no-code players in this game, a lot of them really have to have code solutions to connect to these sort of platforms.

Austin Skidmore:

From a developer standpoint, what kind of stands out with AppSheet as compared to other platforms that you've used? Like, why choose AppSheet over something else?

Camron Lupton:

Yeah. I just feel like you get to use AppSheet on a single solution. And then as soon as you're done with that solution, you realize that you've already paid for those licenses.

And that you can build another app for free for all those same users, whereas like other no-code solutions, you have to pay for every single app. And so it incentivizes you building one giant app that does everything and runs slow. Whereas AppSheet incentivizes building multiple apps.

Maybe your project managers have one app, your employees have one app, your, like, developers have one app. It's like different user roles have different apps. That runs super snappy quick because you're not loading in all this data from other roles and other workflows that person doesn't do.

Austin Skidmore:

Gotcha. Okay. So the microservices is what it's best used for.

How about someone brand new to app development in general. Where do I get started with AppSheet? Why is it a good, we already answered why is it a good product, but like, how do I start getting integrated with the tool and technology?

Camron Lupton:

Jeremy was highlighting something just the other day and how when you go to AppSheet. com and you say create new app, it asks you if you want to chat with Gemini to create your first app. And it's pretty cool.

You can be like, Hey, I want a project management app that has a table of clients, a table of projects, a table of users. And I want a user to be assigned to each project, and I want each project to have a client that, that belongs to, and it will understand that text prompt that you give it like chat GPT or Gemini, and it will convert that sentence that you wrote into a full app with a data back end immediately.

And that's just like that might not be the final app that you want. Probably won't be the final app that you want. But it will be an app that you can start like logging information about your projects immediately on. And it's super cool.

However, the primary workflow for creating an AppSheet app is usually somebody comes to us or somebody falls up, like goes to our YouTube channel and sees our tutorials.

And they're like, Oh, whoa. This Google sheet that I hate putting in data into every single day, I can just convert that into an app. 

And so on AppSheet. com, whenever you hit print a new app, you can start with existing data and that will generate an app based off of the tables that you're at, that you're doing sheet already has in it.

So it's super sweet and super beginner friendly.

Austin Skidmore:

Yeah, awesome. Sweet.

Camron Lupton:

Let's dive into some of this onboarding. And how does it relate.

 Yeah, so if you want to go ahead to the next slide.

Austin Skidmore:

Okay, let me find my cursor again. There we go.

Camron Lupton:

Yeah, so no, this one's good. So a lot of times what we see is that businesses have their primary workflow already Okay.

So they might already have a specific CRM in place, or they might already have a specific platform, software system, paper system, whatever that is already working decently well for them. And they would have to uproot their whole business to switch platforms.

And even though AppSheet can do that, and we've done that for hundreds, thousands of clients, that's not always the most like the easiest win that you can take first.

And so a lot of a lot of the language we use is filling in the gaps from businesses.

There's all these gaps that we've seen in every single industry that people have a tech startup or even a large company.

We see a lot of times where they, you find that certain employees are spending hours and hours a week on this task that, if it was done properly, it would save them all those hours a week where they can actually do the type of work they went to school for.

And so we see stuff like project managers spending hours a week scheduling and communicating that schedule, if we're like in the construction industry. PMs are constantly communicating schedules. And it's that's not what they went to school for. That's not why you're paying them money: to be somebody who does scheduling.

And so, we've seen solutions built for that. We've seen solutions built for, like, IT ticketing or building management ticketing.

And so you'll see situations where your IT department or your building managers are constantly receiving tickets through email and they're getting lost and the people sending them feel like they're not being accommodated. They're getting lost in the system. They have no expectations of those ever being completed.

We've seen that's an easy solution with an AppSheet. And then another solution that would be a gap would be like marketers.

Austin right here, he works at a company that is a leader in AppSheet development. He's not technically an AppSheet developer. By job title, he's a marketer in sales.

And if you look at his computer, he has built like 30 different apps by himself to accommodate all those small gaps.

Marketers outside of QREW have those same gaps, they just settle on like Google sheets or something like that to accommodate those gaps.

But Austin has all these awesome apps that have multiple calendar views, scheduling out every all the content that's like relational data that has notes on each of the campaigns.

It connects the different content that has to do with each campaign. And it's like incredible that a non developer is doing this to fill in his own gaps.

It's awesome. That's like the idea of AppSheet right there.

And so these gaps one by one might seem trivial, but over the course of having hundreds of them, you're losing out on so much value of your company.

By them not being properly addressed. And so whenever these like small gaps are properly addressed, that employees are saving time, your business is saving money and you're helping them all together, do a better job.

And we can go ahead and go to the next slide and we can talk about, oh, actually one more.

So real quickly, what do you think are some downsides a business would have by having a poor onboarding or training process?

Austin Skidmore:

There's some points up here. But it always goes back to the end customer, I feel like.

 If employees aren't properly onboarded, it could lead to downstream effects for the customers. Whether it's like they don't know what they're selling, speaking of the retail industry or. They're confused about the proper process for the buyer journey.

Jeremy Brooks:

Yeah, or like perhaps their training list isn't, up to date or, included into the wrong groups or just result in, in, in general miscommunication.

Austin Skidmore:

Proper storage of inventory items, stuff like that.

Camron Lupton:

Yeah. I'm 28 right now. I worked at QREW for. Six years and I've worked some small jobs before QREW, believe it or not. And I worked at places that were corporate companies that have multiple branches and they just give you somebody to latch onto that has never trained somebody, a lot of times.

And they're just like, "I do this on a daily basis. And I think I do this thing."

And it's just no matter who's training you or what branch you're at, you get trained completely differently. And it kind of mucks up that like brand identity that a company can have.

Like, if you go to Chick fil A, let's say, every single time you say, thank you, or make an order, they say "my pleasure."

And it's part of their brand identity of they're trained all that same way. And you go to Chick fil A expecting to feel like honored and appreciated. And it just makes you like feel slightly more appreciative of them because they were trained well.

And so the instance that we're talking about right here is an onboarding and training app that was created for a retail company, and they were experiencing that same issue: where different employees trained by different people were receiving completely different content on how they should do their job. And what this was doing is it was like having a lot of downstream negative effects.

And so after they built an AppSheet app, this is like the good things that they saw from this implementation of that small gap.

And so for their employees, they were able to streamline onboarding processes, assuring everyone in that role was trained with the same content.

They were able to improve their employees satisfaction of their training experience, and they were able to reduce the rate of employees leaving.

For their customers, they enjoy interacting and being serviced by employees. That know how to do their job well, and they had for the customers increased satisfaction and brand loyalty.

Finally, what most of you guys are here for, what did it do for the business?

For the business, they were able to achieve a greater level of operational excellence.

They were able to improve revenue, improve brand image. And so you can see how just like one small gap that isn't part of their sales dashboard or part of like their product that they're selling. It seems like a small gap, but it actually is able to create a long term positive effect on their business.

And we have this slide right here just to mention why AppSheet was a good solution for this issue. AppSheet is considered a rapid app development platform. So this gets your product out so much faster than native development apps. We have a potential demo that we can show you guys afterwards where I build an app beginning from complete scratch, not any information about that app all the way to a MVP that could be used within a business within 10 minutes.

So I can show you guys how to build an app 0 to 100 in 10 minutes.

Were you about to say something, Austin?

Austin Skidmore:

Yeah, I had a quick question. So thinking in this line of the rapid app development life cycle what's the goal of creating an AppSheet app?

 Is it to release it to the general public? Is it to optimize a business process? Where are we going with these applications?

Camron Lupton:

So, AppSheets licensing is on a per you pay per user. So, if I have 10 apps and those 10 apps have 80 people using it, I'll be paying for 80 licenses, unless you have a Google Workspace license, then you automatically get Workspace core for free.

And what that means based off the pricing system is that it really does a good job accommodating businesses, internal workflows.

This is not the app platform that you're going to build the next Twitter on. You're not going to build the next Facebook on this because you don't want to pay 15 per user for that type of stuff.

But if you're already paying for Google Workspace, then these users are free and you can build unlimited apps for these users instead of bringing on a different no-code platform that you'll have to pay a different thing that you'll have to track the cost for it.

Austin Skidmore:

Nice.

Camron Lupton:

Yeah. So, another thing is that AppSheet has integration with your Workspace directory. And it also has whitelisting by domain. And so you can make it where all your employees automatically have access to specific apps and that they automatically get added to those apps by their Workspace directory.

Any AppSheet app that you build is automatically available on apps as in the app store as a tablet app or a mobile app. And then you can also access it from any browser, which is super powerful.

Another thing is that's easily customizable without compromising speed of development. And that's another potential demo that we could see.

What that looks like is we could add a an email document that gets sent out whenever somebody completes a course inside this app.

And so that, that will be another option that we have a poll for of what you guys could see.

And then finally, it works seamlessly with all the Google Workspace technologies. And it's just that edge that AppSheet has that other no-code platforms don't have.

A really cool thing about AppSheet is that there's things called security filters that allow you to filter what data specific users get to see. And so by using that, we can also limit what views that user sees and what functionality that user can have.

And so in this app, we'll go into more detail in a moment, but in this app, we see that there's admins, there's store managers, and there's staff.

So on the right side, you can watch what type of workflows are happening within this app. And this is specifically on the mobile view as of right now, but an admin has ability to manage courses and what that means is they can add edit or delete courses. They can make Google Meets automatically from the app .

So if one of the training courses that a user has to go through is talking with their manager, they can, in this app, create a scheduled event in their calendar for this user to be onboarded using Google Meets with their manager. You can also do the same thing with Google Classroom.

For more Google Classroom type experience, and all this is triggered and created within AppSheet itself.

Also, if you get a new user that, let's say, they're working the register at the retail business, you can make it where a course automatically gets assigned to that user whenever they get added or onboarded.

So, if that clerk gets added to the database, instantly they're assigned all the clerk related courses.

And on this slide, we see the store manager. And so these people are maybe what you're thinking of, like the individual branches or the people that are the managers over a specific department of the store. And so these people are the ones who are actually adding the individual staff members and assigning the courses that are like ad hoc assignments. And they're able to review the progress of where their staff is.

As we can see on that right side, we see Felix has zero of three complete, and one of them is overdue. Sally has zero of three complete, and none of them are quite due yet, so they're not like behind on anything.

Another feature that a store manager can do is we could say, oh, hey, Felix is overdue. Let's click into him and hit the chat button. And what that automatically does is it creates a Google space with you and Felix to say, "Hey, we see that your loss prevention course is overdue. Please make sure you finish it tonight."

We can go ahead and go to the final one, which is the staff member. And, just what you would think, the staff member is capable of reviewing their content and completing those courses.

Also, they can choose to enroll in optional professional development courses. So you see right there, library, the third option on the menu that actually allows them to enroll into a course that they're not actually assigned to. That way they can maybe pursue a promotion or so on.

Also, if they run into any issues, they can always chat with their manager by creating a Google space with them the same way.

And so this is where we see the superpower of AppSheet. With no-code, you're able to access each and every single one of these right here.

If you were trying to use any other no-code platform, you're either going to be using really complex webhooks, or you're going to be using code to connect these things.

And so it being part of the Workspace ecosystem makes it so powerful. We see things like directory API, the directory being connected, easily with whitelisting. We see Google Chat, we see Gmail, Calendar, and Meets working together seamlessly.

You can actually add calendar as a data source within your app, almost like a table where it sees each individual event as a table, as a record in the calendar table of your app. Super sweet.

You can automatically report, do generated reports off of Google Docs. Do like weekly reports of everybody's work completed, everybody who's overdue that you need to reach out to and so on.

Whenever somebody gets assigned a task, you can go to their Google task and you can add a task to their Google tasks. And so that way they can just always look at that Google task and know what they need to complete.

So we'll go ahead and run a poll. So I believe Hailee has a poll ready to go. And right before I demo this app, I want to give you guys an option on what we want to see afterwards.

And so the options we have is to add a feature to this onboarding app. And what that looks is we want to add a certificate that gets generated with the course name and the user's name who completed it and the date time, or let's say, just the date that it was completed.

Next, the other option is building an app from scratch. This is what I was talking about having nothing and then instantly seeing an app build within 10 minutes. And so that's an awesome option.

And then finally we can do an extended QA. We're already going to have a short QA, but if you guys have lots of questions, then go ahead and select the extended QA and we can have it a little bit longer.

So if everybody wants to go ahead and vote that'd be great. Austin, Jeremy, do you have any questions?

Austin Skidmore:

Yeah. Looked like we had a few questions come in the chat. One particular, this one might be for you, Jeremy, about the licensing.

If you have 500 users in your organization? Do they all get to create apps under their workspace licenses? At least for core.

Jeremy Brooks:

AppSheet Core is included with Business Starter, Business Standard up through Enterprise SKUs, and yes, you can enable them to be able to create apps without any additional costs.

What you lose out on in comparison to the Enterprise tiers are the ability to govern those and provide additional security controls around that.

But, that was actually big news last August. Yeah. Yeah. That's exciting. It was pretty huge news.

It was a big disappointment for companies that had already paid for it .

Austin Skidmore:

Yeah.

Camron Lupton:

I'll go ahead and answer this next question. How well does AppSheet scale? And does it slow down if there's too many rows of data?

AppSheet is capable of running offline. And what that does is it stores the data. offline, and if you're not running it offline and you're running it online, Then it syncs a fresh data set of all the changes that have been done since then.

And so yes, the speed of the app is directly related to the amount of rows of data you have.

There's definitely other factors that you can rely upon, but I haven't seen it be an issue for the thousands of apps I built, as long as you're showing the data that you should be showing. I have apps that run great with 100,000 rows.

Austin Skidmore:

I was just going to add, what are some of the technical aspects of like scaling and AppSheet app?

Do you have to use different data sources? How does that work?

Camron Lupton:

Yeah. So obviously things like my SQL will be faster than Google Sheets, or if you're having hundreds of thousands rows and so on.

But also what I see is that a manager might need to see more data than a staff member. And so you can limit the the amount of records that a staff member sees.

Where if the staff member, let's say only needs to see 2 percent of what an admin needs to see their app is going to load really snappy, fast.

Austin Skidmore:

Gotcha.

Camron Lupton:

Also, if you see a manager, maybe you only need to see the stuff from this year. And so you security filter out that from that year, and then you have an attribute on the user table that says, "Hey I want to see all archived data."

And so also what that does is it resyncs her app. And you have access to all the data of all time can take a little bit longer to load, but you're only going to be using that feature when you want to see data past this 1 year.

And so you can always limit how much data is coming into your app using security filters. And so you can make it run faster or slower for different users based off of how powerful you want the data to work with.

But we see that as long as you're keeping, as long as you're not trying to build your whole entire business into a single app, and then those records are being created on the loop and automatically being created thousands at a time.

That you're really not going to run into issues as long as you're intelligently developing the data structure. 

Austin Skidmore:

Yeah, nice.

Camron Lupton:

Great. We'll go ahead and demo the app that we have real quickly, and then we'll see if we can get started on the poll choice.

Austin Skidmore:

Yeah, we did get the poll, and Hailee said that we want to see it from scratch.

Camron Lupton:

All right I'll do a quick demo of our other app before I jump into that..

All right. You guys should be able to see my screen. And right here we have the actual app for the onboarding that I'm on the admin perspective, and we can see that I can see the progress of all the employees currently.

And we see that Timothy, test at test. com, and Hannah Molly are all completed, but let's say some of these ones are not completed.

We can go to my trainings. As an admin, I'm not really assigned anything right now. We can go to staff, review the staff, see information, give them a call, create a chat with them and so on. We can go to library and we can add new content.

Let's go ahead and go into manage roles and let's say if we wanted to, so we were looking at this list and we're like, Hey, as a retail company, maybe we wanna onboard some social media influencers and we don't want to reach out to IT to add a whole new user role.

And so I can say, let's say brand advocate and say social media. influencers.

It's a cheesy example, but let's go ahead and hit save.

Then I can do a course and I can add a course that anytime we add a brand advocate, it automatically assigns to them.

So if we were onboarding a big social media name and we wanted them to actually follow our brand guidelines and everything on how we get that content out, then they can have a course that walks them through how to do it.

And you can assign this so you can say five days after they get added, we want them to have this completed and so on.

There's the other perspective of the user, the staff right here. And we can go ahead and let's go to one of the staff members. Let's do test two. On AppSheet, we can preview as another user as an editor.

And so as test two, we see a slightly different UI. We see my training. So the ones that are completed for her, the ones that she has left to do and the ones that are completed almost Kanban style, like a Trello board. We have my teams, we have library where they can choose to do additional professional development.

So, I wanted to go ahead and learn about conflict management. I can enroll into that quite easily and it shows up over here. Also, you can change your profile and see the active courses you have.

So , I'm going to be deep into the thinking, I'll be talking out loud what I'm thinking, what's going through my mind as I'm doing it, but I would love for Austin and Jeremy to entertain the peeps a little bit. Yeah. So ask me questions and so on. Yeah.

Austin Skidmore:

Cool. Cool. Add some commentary. And it looks like we have just a little under 15 to 10 minutes, I would say 10 to 15 minutes.

Camron Lupton:

Cool. All right, let's see what I can do.

Austin Skidmore:

Let's see. Let's see if Cam can knock it out of the park with zero to 60 AppSheet app.

So Jeremy, what's your experience with, appSheet development or no-code in general?

Jeremy Brooks:

Yeah. I, the first time I heard the term citizen developer, I didn't really know what that was.

In fact, I think the first time I heard it was within the context of AppSheet. And, I think it's a shift in thinking from the management of a company to say, we have this subset of people who are maybe technically inclined and and being influenced by, CEOs, CTOs, and. We have decided what's, what's going to work for the company after much research and development and testing, we know what's going to work to.

That approach can work just fine, but also enabling the people who will benefit the most from the application to build something very quickly on their own and then have it have the organization kind of improve it, and grow it, and scale it up.

Just the concept of a citizen developer was what really drove home the value of AppSheet, for me.

And then just getting my hands dirty a little bit. One day going, "Oh, look, this is something I can do." And my first app took about 10 minutes.

And then we do have Gemini, formerly known as Duet AI here. And so I took on the challenge of adding Gemini into chat and then using Gemini with just a few prompts to create an app.

And I was able to create an AppSheet app directly from my chat space interface. And with, I had to ask the IT administrator for approval, but in 10 minutes, I had my app that I'd created.

That's right here appearing on my phone. So I can ask for time off. That was my, that's my...

Austin Skidmore:

That's a good, that's a good app to make.

Jeremy Brooks:

But that's just super cool. Cause I can share that with the company if it were to scale up. So, someone on the, someone at the grassroots level can have an idea and it can have a chance to grow and be proven out and then potentially scale up in the company.

Austin Skidmore:

Yeah. And then you're like the hero because you've I've made this app and then someone's " Hey, I don't really like this feature. I need this feature added." And then two to three minutes later, you're like, Hey, check it now. And you're like...

Jeremy Brooks:

But how often does it happen that, maybe you have a teammate and you and that teammate have found a system that works.

You've got some sort of tool. Maybe you developed a fancy spreadsheet and just the two of you are using it. What if that tool was something that could help the rest of the company, but was available across, an application across several different platforms, and then at a company and management executive level, something that could be governed and scaled.

And so it's an idea. It's just the way of getting the knowledge. And and that yeah, that scaling it.

Austin Skidmore:

Yeah, for sure. I think that's really the idea of AppSheet. And that's one of the reasons why they limit the UI.

So one of the questions we often get is, like, why is the UI so limited? Because where AppSheet is trying to limit time-to-value and when you want to focus on UI elements or different landscaping elements of like the app needs to have this kind of design aesthetic or whatever, it's not really the focus of AppSheet.

It's really functionality over a pretty interface, or whatever you might be looking for there, which is good because it keeps your line of business user, focused on, okay, this form needs to have this workflow that triggers this email automation or whatever.

And then like Cam's doing here, getting into some of the expression writing. So definitely adds a layer of logic that maybe you're used to, creating Google forms or something like that. And this adds just like fuel to your Google forms.

So yeah just add a little bit of commentary for the audience of what Cam's working on here.

He's moved back and forth between the spreadsheet and the AppSheet editor. So what you're looking at right now is AppSheet editor.

We have a couple of tabs on the left hand side, and that's going to be like your data, your views, action buttons, the robot is the automations tab. And then you actually have a new tab for chat and you can just integrate chat seamlessly. And then there's a few other options for like global settings below the line there.

And then moving just slightly over, this is where you'll navigate between your views or if you're on the, the data tab, it like shows you all your data tables that you have connected.

I think we had a question come in talking about data tables and how those interact with the different IDs and stuff.

So you can add like unlimited number of sheets. I don't recommend adding, like too many sheets that will slow down the processing speed of your app, but can let Cam speak to that one too.

There's definitely some things that you'll have to think through as you're going through your development process.

But for the most part, it's pretty intuitive as long as you just get in there and start, um, working with a tabular data set, which is getting a little bit technical aspects. But it's just have your rows, your header row at the top, and then all your data is going down. So let's see what we got here, Cam.

Camron Lupton:

Easy troubleshooting. It should be done right here and it should be on to the next step.

So far what I have is I have two tables. I have a tickets table that tracks information and attributes about a ticket, the status and all that.

It has a user of who assigned it. It has, the users have a role. The roles can be either HR or staff.

Staff and HR are both able to submit a reimbursement request. Whereas HR, the only people who are allowed to approve them.

And so within the tickets table, I have my tickets, which is only showing the tickets that I've created or whoever's logged in. And I have open tickets, where only HR will see that. And that is HR's list of all the tickets they need to complete.

So far I have a way where a user is able to go in here and say ate lunch with client. Let's say Jeremy, Promevo. And I can go ahead and type in the information of why I went. What was the strategy behind it, so on. Take an image of the receipt and hit save.

Now if I go to the Google Sheets over here, we can see that a brand new ticket got added with a unique ID, the email who submitted it, the time, the date that it was submitted, the title, the info, it can save the image within Google Drive, save the file within Google Drive, and we see that it had an automatic status of opened.

Now we wanted to build up a workflow for a, let's say, a user to see the ones that they've submitted. And so let's go back into here and go into views and create a new view.

We'll call this one, my tickets. Instead of using all tickets, we only want to see my tickets. We're going to use that slice, which is a portion of the tickets.

We want this to be a table view. And we want the columns for it to show is we want to start off, which is the title, the dates submitted, and then we want to group them by their status.

And so we see this is all my open ones. If I had another one that was, if I got one that was declined or approved, they would also be separated by this grouping right here.

Let's go ahead and move this where it's on the left side.

 So my tickets are down on the left side. Let's choose the icon. I'm going to do a folder, and I'll just do a list of folders like that. And then we want to go ahead and create another view similar to this.

So we'll go ahead and duplicate this view and call this: "Open Tickets."

On an open tickets. We're not using my tickets. We're using only the open tickets, and this is all only the tickets where they're all opened. And so we're going to go ahead and group these by, let's say, the user who submitted them. I don't feel like it's the best option. Let's go ahead and say they're also grouped by the date so that we can have it like that.

And we want it, the date ascending. So as this goes down, the dates are going to be come bigger. That way, the oldest ones are on the top. That way we finished in FIFO, "first in, first out."

Let's go ahead and change this -icon for this one into a different folder.

Go ahead and say open. We'll use an open folder for the open tickets. And right here, we'll see this. And so we want to go ahead and create a detail view for the open tickets. So let's go ahead and create a new reference view.

And so how are we right now? We're a little bit over.

Austin Skidmore:

Yeah, I just wanted to tie a bow on this one. And and then we'll pass it back over to Jeremy for closing us out here.

But yeah, this is great. We got zero to 60 real quick. Obviously we can do a lot more with this for the audience. But this is just scratching the surface for what's possible with AppSheet.

Cam, what's one of your highlights like big takeaways for what people need to know about the 0 to 60 with AppSheet?

Camron Lupton:

Yeah, AppSheet is fun. AppSheet is enjoyable. People that aren't AppSheet developers can jump in and see if it works for them. If, especially for you guys who have Workspace licenses, it's a no brainer, just try out.

It's something that there's a lot of training resources online. There's a lot of developers. You're in an area, in an environment where you have a lot of support.

If you want to, if you jump into AppSheet, you enjoy it and you want to go big with it.

Austin Skidmore:

All right. Toss it over to you, Jeremy. Thanks Cam.

Jeremy Brooks:

Thank you. Thank you, Cam. That was awesome. I think you just touched on something that I want to segue off of, which was like, it's fun to use AppSheet.

And you think about people entering the workspace who have been in, been professionals for, let's say under 20 years. These are digital natives. They're used to an application, something as simple as an app on your phone. How many apps, do our workplaces have that we could all do from our phone?

And we're used to this. Yeah. This kind of siloed approach of working where, I'm going to go to my desk. I'm going to open sheets, but how many times, perhaps I'd love to hear examples in the chat of have you heard, have you thought of examples of how something like this could help you.

But I can definitely remember a few being an IT admin myself and trying to track inventory of laptops, and being on-site somewhere looking, I can definitely remember wishing I had something like this.

But, what is Promevo's role in this? Our role is really just, we know our customers the best. We have the relationship with them to grow them with Workspace, and we're your next step for learning more about the product, learning how it can help you.

And in two high level ways, we help with licensing guidance and licensing management. We can help you strategize, what is the best fitting, the best plan for you?

Like we are right now with some people in the chat wondering, "Hey is what I have access to right now a suitable for what I want to do? Is it suitable just for testing? Do we need to take the next step?" That's something you could talk through with my role.

The second point is account management is I'm a Senior CSM here. So I'd like to think that I know my customers really well.

And I, I take, any of you who know me, I see several of you here, at least four of you are my customers. I like to, I genuinely like to know what you do, as a former, as a technologist and former admin it's very interesting. And I take more of a guide and advisory role and approach.

But specifically my role can help with cost monitoring, staying within a budget. Thank you. If you are using a Google Cloud database connected to AppSheet, then of course, that's something that we can help monitor the cost of as well.

Generally, it's very low cost, but but yeah, and then me, my role is also just to connect with resources, right? So whether it's resources at Google or resources at QREW.

There's a very good reason that we've chosen QREW to, to work with. Google relies on QREW group and oftentimes pushes customers their way. So we are strategically aligned with them because they are the best in the business.

I'll blaze through this because I know I'm really low on time, but, I broke down how we engage our customers and to just, for I words, we inform you of what is capable of demonstrated features, provide resources, sharing use cases.

I have several examples with use cases. And I, if I had time, I'd like to go into some of those. But, I had a customer who wanted workstation reservation tool. And we were looking at all these third party things and it turned out that AppSheet had a template for workstation reservation or resource reservation.

So inform what it can do identify pain points. Then iterate and conceptualize together, ideate on how it could potentially be valuable to your company.

And then lastly, just to integrate, to help bring the product into your environment, the, selecting the licenses, adding them to your environment, helping you deploy those things.

But then. At the next level, a company like, QREW can help enable you by holding workshops, learning sessions. Or they can help you develop the product with real hands on approach.

There are four AppSheet tiers. We've got Starter, Core, Enterprise Standard, and Enterprise Plus.

So, Core is what we've been talking about, it is included in Workspace. I think everyone on this call is a Google Workspace customer. So you all have access to this tier.

And for smaller projects and for getting going with citizen development. This is going to check the box for a lot of you.

But Enterprise Standard and Enterprise Plus are where we can build a very robust tool that could connect to multiple data sources and adds governance and security to those tools.

If I had a little bit more time, we could do a deeper dive into all the differences of tiers, but that's what I'm here for, to talk to you about, your ideas and see which solution might fit best.

Lastly, all tiers benefit from Google's latest generative AI tools now called Gemini, as of last week, formerly known as Duet AI.

It's my job to share what's exciting about products. I love connecting customers with the right tool for their job.

And, Gemini, we mentioned this a little bit earlier, so I'm not going to belabor it, but Gemini can be used from within Chat to create an app, without ever having left Google Chat.

And then in AppSheet, you'll have the ability to use a natural language to improve and make changes on that application. Like I want it to do this and I want to change it to do this.

And then you can also create an app. So you've got the platform of your desktop platform of your mobile. You can also have a platform for using AppSheet within your Google Chat where if you're familiar with Slack, you know, and you want to add an application, maybe you want to add Asana or some other thing. Now, you can create one of those for yourself and add an app straight to your Chat.

 I think that's really all it for me. Sorry. I had to blaze through that section.

Hailee Zapata:

No, Jeremy, that was great. Thanks for going through that. Just so they know how Promevo can really help them get involved with QREW.

That was wonderful guys. It's really interesting I think we needed a second webinar, like a deep dive on use cases and how you can really get involved with AppSheet.

So we're going to plan that for the future, guys. So stay tuned. We will have that coming.

We hope you guys will check out our website for more information and reach out to us directly to get your own personal AppSheet demo. These guys love doing it. They can show you all the ways to do it.

We will also be sending out the follow up email with this recording and links to the upcoming webinars that are on the right hand side. We have an AppSheet blog, a one pager, all the resources for you.

So let's not waste any time. Let's go ahead and get to some questions. Let me pull up. I know we have a few left.

Let's see here.

Camron Lupton:

While we answer a question or two. Would you like to see the final app?

Hailee Zapata:

Yeah. Go ahead and share your screen.

Camron Lupton:

I could submit a ticket in about five seconds.

Hailee Zapata:

Yes. Perfect.

Jeremy Brooks:

I see it.

Hailee Zapata:

Is there an advantage from a workflow standpoint, having Google Workspace rather than just AppSheet as a standalone?

Camron Lupton:

It's really, if you don't already have workspace, if you're in the Microsoft ecosystem, then AppSheet is still super powerful for you.

You can access Excel, you can still do integrations using APIs and webhooks to other Microsoft platforms and products. And so it's still powerful, but it's a no brainer if you're already in the Google ecosystem.

Jeremy Brooks:

Yeah, AppSheet really is a platform agnostic database, agnostic as it works across a wide range of different platforms. But like Cameron said, it's in the context of Workspace, it's a no brainer to at least see if it benefits your company.

Camron Lupton:

Let me go ahead and submit a ticket in about two seconds right here. So I'm on Austin at QREW tech. So it's a user who is a staff member. I can go ahead and say, ate lunch, need reimbursement. So I'm just putting in some like filler text. Let's say hop dotty, big favorite of mine.

 I'll go ahead and add the receipt, a picture of the receipt. I'll just do a picture of my Google calendar for now. Hit save.

This other user type who is an HR person, over here. He reloads his app. All of a sudden he sees this ticket on his side.

As you can see, there's this open folder right here for HR. The staff member does not have the open folder. And so he goes into here, clicks into here, says, Oh, that's pretty valid. I'm going to approve it.

Over here on Austin side, we could send an email saying it's been approved. But he goes to my ticket and he sees that it's been approved and so on.

So we're good to go back to the QA.

Hailee Zapata:

No, that's really cool. I think we can do that in 10 minutes, maybe less.

Jeremy Brooks:

And there's notifications about actions taken are customizable too. So it could come to an email or I think even SMS, right Austin?

Austin Skidmore:

Yeah.

Jeremy Brooks:

Notifications can be made several, they're completely customizable.

What other questions were there?

Hailee Zapata:

Yeah. So how secure are the apps that are created and can you share them like externally?

Camron Lupton:

Yeah. AppSheet has a secure SQL connection. It also has a secure Google sheets connection. And so they're fully secure. They're secure up to the level that your actual data source is secure.

So, if you are not sharing your Google Sheet publicly, it's secure. If you're not protecting your SQL database, it's not secure.

 But you actually can whitelist the individual IPs of the AppSheet SQL connector. And you can make it where only you and your IP, and then only AppSheet has access to that SQL database, making it fully secure.

And the way that you log into an AppSheet app is using the OAuth. And so you have to physically log into their Google Workspace or Microsoft Teams, 365, or whatever, to get into the app. And so it makes it super secure. Just right off the bat, fully native.

Hailee Zapata:

Okay. We I know we're at time, guys, so we're going to go a little over just to answer a couple of questions, but if you need to hop off, feel free.

You will get the recording with the answer to these questions later on.

We do have a little technical question. Can we make an AppSheet screen pull data from a Google Sheet based on the Google Sheet ID passed as a parameter? For example, use one AppSheet screen to pull data to that screen dynamically from different Google sheets based on the Google Sheet ID.

That was a lot. I hope you understood that,

Camron Lupton:

I don't know quite what you mean by that. You could have a user attribute of which feeds data you want to bring in. And so you could say, Hey, I could turn off the connection entirely for this user accessing any data from this sheet. Therefore, this app isn't showing this different table in the app at all.

And so I assume that would accommodate what you're asking for.

Jeremy Brooks:

Yeah. And you can also initiate an AppSheet app from that sheet. It'll automatically be dynamic because it was, that's the primary source, where it was began from.

Hailee Zapata:

So does everyone need an AppSheet license within an organization or just some people, like how does that work when your company wants to get licenses?

Camron Lupton:

Yeah. So everybody who. You want to be using an app when you need an AppSheet license.

And so sometimes that looks like accommodating for all your employees at once. Sometimes you have a strategy on how you want to deploy AppSheet. And that looks like maybe I want to first build apps for our admins and our managers to have a specific workflow completed. And that might only be 10 users the first rollout.

And then you guys are like, now that we've seen that actually has proven itself, we want to see what it would look like for each of our individual smaller employees to [00:52:00] receive AppSheet and what we can accommodate their processes with.

And then you can increase your license count.

Hailee Zapata:

Okay, great. We are over time. I want to thank everyone for joining us today.

I don't know about anyone else, but I'm in marketing, like building an app is intimidating and this was so interesting and it is fun and exciting and I think it's something that I would love to do.

It makes it easier for the person who's not exactly the most techie, IT related person get involved with app building.

So I think this is great.

If anyone wants a demo, please reach out to us. We would be happy to get with you guys, show you all the features.

Thank you for joining us today. We look forward to seeing you guys in our next webinar.

And thank you Cameron, Jeremy, and Austin for a great presentation.

Jeremy Brooks:

Of course.

Hailee Zapata:

We really appreciate it.

Jeremy Brooks:

Of course. Look forward to hearing from you.

Hailee Zapata:

Thanks everyone.