App Actions and Android Slices | WillowTree
Summary
While developing and testing App Actions and Slices isn’t new this past October, the ability to do so easily, without jumping through additional hoops, is. This actually replaces the old intent, Google says they recommend implementing GET_THING instead of Once those steps are complete, you can begin the App Actions review process. The cop-out answer is to follow Google’s codelab here: https://codelabs.developers.google.com/codelabs/appactions It’s been very recently updated and does a great job of describing how to get started on all of this, including the requirements needed for testing your App Action locally. Couple things to note in the codelab: • It mentions that you can’t actually upload an apk with an file to Google Play, that’s no longer true as long as you go to “Advanced Settings” and agree to the “Actions on Google” terms of service • The “Creating Preview” dialog sometimes ends up behind the App Actions Test Tool for Android Studio, if you press “Update Preview” and don’t see any progress, that might be why • Invocation through adb/test tool works immediately, but implicit invocation through the assistant seems to need some time between creating the preview and it actually working on device App Actions and Android Slices are another way to increase user engagement with your app, as well as simplify tasks users are already completing. The scale of adoption on these APIs is still unclear as they’re so new, but one thing’s for certain: if a user asks the Assistant to do something, you don’t want your app to be the one that isn’t showing up as eligible to fulfill that request.