[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-29 UTC。"],[[["\u003cp\u003eWhen designing your Google Chat app, prioritize user needs by considering factors like app discoverability and user familiarity with Chat app features.\u003c/p\u003e\n"],["\u003cp\u003eAccount for global users by considering time zones and offering multi-language support to enhance user experience.\u003c/p\u003e\n"],["\u003cp\u003eOptimize your Chat app for both web and mobile platforms, ensuring clear and concise messaging while adapting to screen size limitations.\u003c/p\u003e\n"],["\u003cp\u003eMaintain a professional, authentic, and considerate tone in your Chat app's communication, prioritizing user efficiency and providing clear error handling.\u003c/p\u003e\n"],["\u003cp\u003eBe mindful of user permissions and data access, ensuring sensitive information is shared appropriately and avoiding unintended data exposure in shared spaces.\u003c/p\u003e\n"]]],["When designing a Google Chat app, prioritize user needs by considering their discovery, familiarity with Chat apps, geography, and preferred language. Ensure clear, concise communication with a professional, authentic, considerate, efficient, and encouraging voice. Optimize for both web and mobile platforms, and be mindful of varying user permissions and data access. Protect sensitive data and avoid accidental information leaks in shared spaces. Tailor messages based on user preferences and test across different devices.\n"],null,["# Identify your users' needs\n\nThis page describes how to account for your users' needs when designing a\nGoogle Chat app. Whether your Chat app\nsupports a globally distributed team of thousands or just one person, ensure\nyour Chat app helps everyone who messages it by\nincluding the intended user in your design process.\n\nDiscover your Chat app\n----------------------\n\nConsider where your intended users can discover your\nChat app for the first time. When you\n[publish your Chat app](/workspace/marketplace/how-to-publish),\nthink about where users can find it.\n\nFor example, don't assume that users know what your\nChat app does. Make sure your\nChat app's name reflects what it actually does, or the\nservice that it integrates with.\n\nFamiliarity with Chat apps\n--------------------------\n\nYour Chat app might be the first interaction a user has\nhad with Chat apps. Don't assume that users know how a\nChat app works. Features like\n[Chat app commands](/workspace/chat/commands)\nand\n[dialogs](/workspace/chat/dialogs)\nmight confuse some users, so give them instructions.\n\nFor example, when prompting the user to issue a slash command, we recommend the\nfollowing format:\n\nThis prompt is helpful for the following reasons:\n\n- Tells the user exactly what they need to type.\n- Uses special formatting to make the `/createContact` slash command stand out from the surrounding text.\n- States the goal of the slash command.\n\nTo learn more about how to help users with other interactive\nChat app features, see\n[Design user interactions](/workspace/chat/interactivity).\n\nGeography\n---------\n\nIdentify where in the world your users use your\nChat app. Oftentimes, people in a Chat\nspace are located all over the world, which means that they're working in\ndifferent time zones. If your Chat app sends\nnotifications to users or spaces, be mindful of the time of day.\n\nFor example, the following Chat app notifies whomever\nis the on-call reviewer for the week. But, if part of the team is in New York,\nand part of the team is in California, we recommend configuring the\nChat app to send a message at a time that is convenient\nfor all users.\n\nIf your Chat app\n[mentions a user directly](/workspace/chat/format-messages#messages-@mention),\nconsider checking that user's timezone in the\n[Calendar API](/workspace/calendar/api/v3/reference/calendars)\nbefore sending the notification. If it's outside that user's working hours,\nconsider sending the message without a mention, or waiting until their work day\nbegins.\n\nLanguage\n--------\n\nYour Chat app can respond to users in multiple\nlanguages. To support more than one language, your\nChat app must check for a user's preferred language\nand localize its content accordingly.\n\nFor Chat spaces, add a language option to the\nChat app's configuration settings. After users set a\nlanguage in the space, your Chat app can respond to\nmessages using the space's preferred language.\n\nTo check a user's preferred language:\n\n1. Get `User.name` from the [`User`](/workspace/chat/api/reference/rest/v1/User) type in the Google Chat API.\n2. Map `User.name` to [`user.id`](/workspace/admin/directory/reference/rest/v1/users) in the Directory API.\n3. Get `user.languages[]` for the given `user.id` in the Directory API.\n\nPlatform: web versus mobile\n---------------------------\n\nGoogle Chat is available on computers and mobile devices. Computers offer lots\nof screen space where users might be more accepting of information-dense\nmessages with lots of buttons and options. On mobile devices, users appreciate\nsuccinct messages due to the limited screen size.\n\nTry to show three or fewer buttons per card. If you need more, consider\nlaunching a\n[dialog](/workspace/chat/dialogs) instead. Dialogs can present a series of cards\nthat make gathering lots of user input a friendlier experience than trying to\ncollect all of the information in a single card message.\n\nTest your Chat app on multiple devices of varying sizes\nto make sure its presentation of information is digestible.\n\nVoice and tone\n--------------\n\nBecause Chat apps are text-based interfaces, writing clear,\nconcise, and actionable messages ensures user success. When writing messages for\nyour Chat app, consult the\n[Google Material Design writing guidelines](https://material.io/design/communication/writing.html).\n\nEach Chat app is different, but to communicate\neffectively with Chat users, your\nChat app's voice and tone should convey the following\ncharacteristics:\n\n- **Professional**. Your Chat app might be helping\n people at work. Make sure its personality fits into a professional setting,\n or it might feel jarring and inappropriate.\n\n- **Authentic**. Chat apps can speak colloquially, but\n shouldn't pretend to be human. Avoid giving your\n Chat app a gender, or a name that could be confused\n with a person. Including a little character is good, but your\n Chat app should focus on its utility.\n\n- **Considerate**. Be thoughtful and noninvasive. Your\n Chat app shouldn't bother users unnecessarily or\n repeatedly. Strive to anticipate user needs and offer solutions.\n\n- **Efficient**. Recognize that most users aren't looking for a long\n conversation. Help people complete tasks by keeping the\n Chat app experience focused. Avoid saying\n everything in favor of saying the most important things. If you do need to\n convey a large amount of information, break long messages into multiple\n short messages. Try to limit each message to one call to action, and make\n the information presented as relevant as possible.\n\n- **Encouraging**. Be optimistic and friendly with users as they explore your\n Chat app. Users should always know how to move\n ahead towards their goal, especially if they encounter an error, like asking\n your Chat app to do something that it can't.\n Honestly tell users that they've encountered an error or limitation, and\n tell them how to proceed.\n\nUsers with different permissions, roles, and data access\n--------------------------------------------------------\n\nPeople in Chat have different permissions and data access in\nGoogle Workspace and other systems. A single Chat space could\ninclude administrators, managers, sales people, and customers. These are some of\nthe permission-related scenarios to consider while building your\nChat app:\n\n### Limited access to Chat apps\n\nGoogle Workspace administrators can limit who has access to\nChat apps in Google Chat. For more information, see\n[Determine the audience for your app](/workspace/marketplace/how-to-publish#audience)\nin the Google Workspace Marketplace documentation.\n\n### Authentication\n\nPrompting a customer to authenticate to a customer's Google Workspace\ndomain might not work, and might confuse and frustrate the user. Account for\nthis possibility by writing an [actionable error message](/workspace/chat/write-error-messages).\n\n### Share sensitive information in Chat spaces\n\nIf a user authenticates a Chat app to share sensitive\ninformation, like financial or health data, it might be best to limit that\nChat app to 1:1 direct messages so that the\nChat app doesn't accidentally reveal sensitive\ninformation in a Chat space where others might see it. When\nconfiguring this type of Chat app in the\nGoogle Cloud console, on the\n[**Configuration** page](https://console.cloud.google.com/apis/api/chat.googleapis.com/hangouts-chat),\nmake sure that the **Join spaces and group conversations** checkbox is cleared\nand unselected.\n\n### Share information in Chat spaces that include customers\n\nIt's common for employees of a company to share a Chat space with\ncustomers. Your Chat app can be a real boon to\nemployee-customer interactions, but if your Chat app\nshares a space with customers, it's important to consider what data your\nChat app might reveal.\n\nFor example, say your Chat app shares customer case\ndetails. If your Chat app shares a customer case in a\nChat space shared with other customers, it might accidentally\nreveal customer information to people who shouldn't see it.\n\nRelated topics\n--------------\n\n- [Write actionable error messages](/workspace/chat/write-error-messages)\n- [Define all user journeys](/workspace/chat/journeys)"]]
