Part of that to do list could be shared with this community…it will be appreciated…and great suggestions will rise
Hmm, it doesn’t seem I do. Is this something going forward I should have setup to try these new add-ons quicker? Thank you!
Google chat will be available for google workspace accounts only , from what I’ve read
Hi @Rachelgmoore ,
Just to give it a little more insight: I’ve been following thoroughly the described steps here:
Quick start: Create your first Chat app with AppSheet - AppSheet Help
I was able to follow each step. However, despite my account being a paid one and on Google Workspace, I’m facing this:
I didn’t read any limitation about the app being deployed. Is it an error, or is it normal?
Thanks for considering !
EDIT: once deployed, that works fine. But…I build my apps mainly on prototype stage 
1 Like
Im just curious what the possible, useful and effective use cases of this new coming features? I considered, but I came up with none.
AppSheet is no doubt, an APP.
Google Chat is another APP. Then why do we need to juggle the two different apps at the same time? We can send the notification with exsiting webhook to the Google Chat Spaces. Then user quickly open up the AppSheet app from there. Then what is the user intention to stay with Google Chat rather than directly interact with AppSheet?
Still it is my own question, what the new benefit the new Google Chat functionality will be bringing to the users.
3 Likes
For me, “Use cases” should be driving factors for the appsheet creator to touch upon and eagerly learn and test new fetures. I tested before for this (only once). But I could not came up with any user case for that, which make the app users productivities to be improved.
So I completely forget about it.
There should be tons of the areas to improve the platform. Not fancy ones, but just improve the existing functionalities to the next level…
For example, the better Calendar view… The currenlty the optional changes App Creator can make is almost NIL. So I personnely never used such type of views. If the calendar view is enhaunced, I belive 100% existing App Creators will welcome it better than welccoming something new feature like Chat app, where I don t know what the use case is.
- Better, wise and precise App Formula assistance functionalities.
- Grouping the Gallery view. select the image type to apply to the gallery view.
- New chart type (project is seemingly abandanded)
- Observed odd behaviors on the app editors (several people recently claiming on this community)
For instance, I just listed up few items, Those items are not significant from Google point of view, but they will bring the tons of better experience and push the AppSheet to the next level but sadly Google wont touch those… (x.x) This is factual, as nil of the feature requests thrown to the feature request category never happen. Only the new features (including Chat app) is suddenly comes up. This is the evidence, Google pursue to their own (technical) challenges, rather than providing better and enhanced feature by hearing the voice from the users… (x.x)
7 Likes
Thanks for the feedback, as always. For what it’s worth, we have received a lot of interest from customers around Chat Apps support, which is the reason its under development. The common use cases are for wider distribution of apps that are infrequently used or require limited interaction from the user. Obviously, if you’re using an AppSheet app every day, totally agree that its not saving you a lot of time to use the app directly via chat.
However, if you’re using an app infrequently, the discoverability and usability is much better for a Chat app - there’s no need to log in again, the app will already be in your chat history, or in a space/room where you are already communicating with colleagues. If, for example, you just need to approve a request, it can be faster to just approve from the message itself rather than jump out to appsheet, log in, have the app load, and then approve the request.
One customer we met with has a ~30 page guide for building chat apps internally for developers - if I remember correctly they have over 50 chat apps in their environment. They’re exploring using AppSheet to dramatically streamline the development of new chat apps, along with making the audience of developers significantly larger.
There’s also some tradeoffs to be made here - we absolutely review feature requests on an ongoing basis, and part of our product development process is that as we look at a particular feature, we go back through the open feature requests and do our best to incorporate the feedback. I just did a quick skim through the top feature requests now and several of those items are under development - we have a people API integration that is coming, an enhanced expression editor, and iframe support. The new desktop UI is heavily influenced by feature requests as well as community feedback.
I think part of the challenge is that the users we are hearing from are a much broader set of users than the users who post here in the community. We hear from customers directly, from feedback provided in-product, from surveys we run, even from the sales organization. All of these constituencies get a voice, and we have to trade off among all of these different groups, with different goals and incentives. I would say a lot of the people here are power users who want deeper, richer functionality, similar to what you describe. What we hear from customers directly, however, is a lot more around security and control. We hear from new users that the product is too difficult to use. What we end up building is a balance between these competing priorities, through a lens of how can we help the most users/have the most impact. We obviously don’t always get it right, but we are thoughtful about what we prioritize.
I will also say that i have certainly seen teams at Google who build things for the sake of technical challenges, but I have always done my best to prevent my teams from that behavior, and I know Tomas on the engineering side feels similarly. At the same time, as a startup, AppSheet cut a lot of corners in the interest of speed and we spend a good chunk of our time paying down that technical debt in a sensible way.
8 Likes
Hi Aurelien,
Yep, you do need to deploy Chat apps before they can be used. We’ll make sure to call this out more clearly in help docs!
1 Like
Hello I am new to appsheet an chatbots. I just tried to create a chatbot from an appsheet project and have it running in less than five minutes which of course is great! We are looking to create a chatbot that can give answers to technical support questions based on our support knowledge base. For example if someone asks what to do if they can’t print, the chatbot can give the article from the knowledge base which presents a couple of solutions. If the user is not helped, then they can contact live support from the chat. Is this a possible use case for an appsheet chatbot? Or is it not designed to use it in this way. Thank you!
1 Like
Among the generative AI features planned for Google Workspace was a Chat feature.
Is this related to AppSheet’s Chat integration feature?
Thanks.
1 Like
Hi @takuya_miyai ! It’s not, no. There is a variety of features coming to Workspace and Chat separate from what we’re offering as part of this Chat Apps project, so stay tuned to the Workspace blog for more info on those.
1 Like
Hello! So glad to hear you were able to get things up and running quickly.
Yes, the use case you mentioned is definitely something you could approach with a Chat App-based solution as long as you take a few steps to allow the underlying AppSheet app to read your knowledge base data in tabular form. Said a different way: You’d need to get your knowledge base articles into whichever database you’d like to use to power your App, then your chat-based interface would act as a way to search through those rows to find a specific “value” (e.g., article or issue).
You could also add a “contact support” button to a view or add a new “contact form” view to the App and use that to address the use case of what if people are unable to find an answer.
Hope that helps!
Thanks @Rachelgmoore
I see.
It seems that Google Chat continues to evolve beyond my expectations.
I expect it to become an even more synergistic feature with AppSheet’s Chat integration! 
Ok that’s clear! Thank you for pointing out how we can approach this!
We worked hard and tried to find a way to remove the chat app from the available list from search result in Google Chat. We un-deployed the app, but the Chat App is still available to anyone. We enabled Chat App while the app is deployed, but the Chat App is listeded up when we search the name from Google Chat. Even it makes story worse, we completed deleted AppSheet app and removed the associated Google Cloud Project completely. However, the “Ghost” of the Chat App never die.
This will cause potential disruption toward the features. Once the user started to “TEST” the Chat App feature, the more of the Chat App will be listed up as a search result. However, we all do not know which Chat App is active and alive, and which Chat App is died out. We asked Support Desk but the answer is there is no way to remove the Chat App once the option is enabled. Once we did this operation, there is no option to remove such Chat App from Google Workspace…
Trust me, this behavior will cause massive disruption to the users in the near future.
We definitely need to “Kill” Chat App once it is not needed due to any reasons.
3 Likes
Thank you for the feedback! For this Chat app, were you using the manual configuration mode or the automatic configuration? If you are using manual configuration, since AppSheet does not own the project or have access to it, we cannot clean up the chat app.
Do you mind filing a support ticket? I can take a look and follow-up.
Will do and mention to ask to tag you sir.
Thanks @Sarmad_Hashmi
This problem occurred in my environment and I will contact support.
Please wait a moment.
In Chat integration, could you consider improving the UX on Google Chat in general?
I understand that some ViewTypes are not yet available, but even for those already supported, there are some points that are difficult for the average GWS user to operate.
For example, I intuitively felt the following two things.
- The dialog of information display is small.
- Even if the image display setting of Detail View is set to Fit, it is displayed wide and visibility is poor.
There are others, should I mention them in this thread if I notice them?
In addition, I have long wanted a site to manage different Known issues as the UI of this community is inappropriate for conversations about feedback on new AppSheet features and responses to them.
In addition to the points raised by @takuya_miyai , this is not a big deal but logically wrong I feel.
My understanding is the app creator can create ONE Chat App PER one single app. But the main menu says “Chat Apps”, which is plural. Locally, Chat App (singular) should be the right name for the menu option.
1 Like