Engaging Android App With Assistant

There are millions of apps in the Android ecosystem, so there may be some investment needed to help you search. Your app needs to offer something that separates users from other similar apps to stand up.

Creating a collaborative work is a quick and easy way to increase the potential reach of your Android app by creating a new entrypoint from the devices covered by Google subsidiaries. With this, you can bring users services without installing anything through voice, and when people can offer more value, people can bring them to your app.

Your collaborative work fulfills your Android app experience by offering some of your services through Google Helper, which is available on more than 500 million devices, including speakers, phones, cars, headphones, and more. Creating an Action provides a frivolous way for users to start connecting with your services when Google Assistant is available.

Creating an action for the assistant will increase your brand presence, which will bring your services into new devices and references, because users interact with Google assistants.

Feature what your app does better

It is probably a mistake to try to rewrite all your Android apps as a conversation process, because the voice is a different way with different barriers and usage patterns. Instead, you should start by selecting the most important or popular features in your app that translate well into the sound context and can be easily completed there. Then, you can create your conversation experience to offer these features on Google Supporting Tools. Check out the Conversation Design site, which has many articles and guides about how to create a great voice UI.

Come see a fictional example. Imagine that you have a mobile commerce app. Some features include searching of products, navigating in different categories, adding payment information, and checking. You can make an action with the same functionality for the assistant, but we encourage you to see what is the best understanding in the conversation experience.

In this case, your action can focus on what you want to know after purchasing products through your Android app or web page. You can provide a quick way of getting updates on the status of the purchase (if you provide different state for payment / purchase process) and shipment information, or to order a user to re-order To provide the interface. Then, your users will be able to ask something, “Hey Google, ask about my last purchase from the Voice Store.”

Or, to reach users who have never shopped before, you can create an action to offer exciting deals for common products. For example, you can create an action that “O Google, asks the Voice Store what deals are on TV today”.

As you can see, starting with the “Hero” use case for your action is an exciting way to present complementary conversation features of your Android app, and you feel that it will take less time.

In Google I / O 2018, we presented a discussion, “Integrating your Android app with Google Helper” that includes more details and examples for developers.

Delivering user’s purchases across surfaces

In-app purchases, subscriptions, and one-time products have proved successful for Android developers while talking about monetization, allowing developers to provide additional types of payment to different types of digital goods and users. These types of monetization are proven to drive the user conversion and make the app more profitable.

Google Play Billing provides a series of tools, APIs and documentation to help developers manage life-cycle, build server-side authentication and more. If you are new to in-app billing, check out the Google Play billing overview page.

Now, Android developers can expand where users can access these items or upgraded experiences by presenting them through actions. This extension is accomplished by honoring users’ rights on Google Play in different surfaces and devices when they can not (or do not want to) use the app when cooking or driving.

For non-Android platforms, you will need to ask your users to link their accounts. You can then use your user’s account history to identify that they have purchased purchases on other surfaces.

See Accessing Digital Purchase Pages for step-by-step guides on how to enable user access to purchases and request request data and analyze.

What will happen next?
If you are not yet familiar with the actions on Google, start by looking at our Overview page, which describes the platform in detail and tells you what you need to know to create your own actions for Google Assistant is.

Stay tuned for more posts about how to improve your Android app experience with actions on Google.

Thanks for reading!

Source : android-developers.googleblog.com

Leave a Reply

Your email address will not be published. Required fields are marked *