Youĭeclare BIIs in your app using Android capability elements. Launching your app at the requested screen or displaying an Android widget. When a user invokes an App Action,Īssistant matches the query to a BII declared in your shortcuts.xml resource, Suggest tasks for users to discover or replay, in the right context.Īpp Actions extend your in-app functionality to Assistant, enabling users toĪccess your app's features by voice. Suggest voice shortcuts from Assistant.Queries that match predefined semantic patterns (BII). Provide Android widgetsįor Assistant to display, offering inline answers, simple confirmations andīrief interactions to users without changing context. Display app information on Google surfaces.
Here are a few common reasons to use App Actions to extend your apps to Trigger on a number of factors, including quality and relevancy to the user's request.īased on those factors, Google may exercise discretion in surfacing your Action in response to Note: App Actions, like all Actions that support built-in intents, Users can onlyĪccess App Actions on Android phones, and Assistant on Android Go does not Widget to display within Assistant to fulfill the user query.Īpp Actions are supported on Android 5 (API level 21) and higher. For some use cases, you can specify an Android Semantically accessed using BII, and enables voice support for your features.Īssistant fulfills user intents by launching your app to Capabilities tell Google how your in-app functionality can be You enable support for App Actions by declaring tags in Shortcuts in your app, with the App Actions in-app promo SDK. Users to easily discover and replay your App Actions. Shortcuts to users, based on the user’s context. With App Actions, Assistant can proactively suggest your voice capabilities as
0 kommentar(er)
