Google IO 2017 Recap
Download as PPTX, PDF1 like516 views
The document discusses various features and best practices of Instant Apps introduced at Google I/O 2017, emphasizing user engagement and seamless content discovery without requiring app installation. It outlines implementation requirements, dos and don'ts, and highlights limitations such as the 4MB download cap for Instant Apps and device compatibility. Additionally, it covers new notifications in Android O, Google Play App Signing, and updates on Firebase tools for performance monitoring and analytics.
Google IO 2017 Recap
- 1. Google IO 2017 Vishal Nayak
- 2. Contents
- 3. Instant Apps • Introduction • One Codebase • Structure of a Instant App • Implementation requirements • Do’s and Don’ts • Caveats
- 4. Introduction • To get the user engaged with your content and complete a task, not to get user to install your app • To increase the discovery of your content through URLs and search results
- 5. One Codebase
- 6. Structure of an Instant App
- 7. Implementation requirements • Remove unnecessary code and resources from your app. • Support Android app links • Refactor app into feature modules • Implement runtime permissions • Implement Smart Lock for passwords • For payments, use Google payments API • Define entry points for your app
- 8. Do’s and Don’ts • Put sign in when users understand the value of signing in, not at the beginning of instant app launch • Allow users to complete a task – don’t prompt for installation just before task completion • Installation prompting inside the instant app - Explicit and Implicit • Mobile holdback on play console : define percentage of users that should go to the mobile web and percentage that gets the instant app • Use Google analytics for Firebase for tracking • Don’t create additional splash screens • Don’t branch your UI - user should be faced with as little re-learning post installation as possible • Provide a "share" action within your app that allows users to share your instant app's URL.
- 9. Caveats • Instant Apps are currently available on devices running Android 6.0 (API level 23) and higher. • 4MB download limit for Instant apps (validation occurs when you upload your instant app to the production track of the Google Play Console) • Users can opt out of Instant apps via: Settings > Google > Instant apps.
- 10. Android Omg – What’s new • Notifications in Android O • Google Play app signing • Other new stuff…
- 11. Notifications in Android O
- 12. Need for change • People often want only some notifications from an app, but not all of them • Many people don’t adjust their settings, even if they know they can • When a notification is addressed right away it is easy to forget later • Only 2 types of notifications are valued People to People notifications Reminders
- 13. Notification Channels • App defines a channel for each type of notification it sends • User has channel-level notification controls
- 17. Visual Hierarchy
- 18. Snoozing
- 19. Google Play App Signing
- 20. Current Signing process If you lose you signing key it cannot be retrieved
- 21. Google Play App Signing Google Play app signing helps developers to secure their app signing keys
- 22. How to?
- 24. Resetting upload key Contact the Google Play Developer Support via the Help center https://support.google.com/googleplay/android- developer
- 26. Derived APKs
- 27. Auto multiple APKs • APKs are smaller • Can support more devices • No need to create multiple APKs during development
- 28. Testing
- 31. Autofill framework in Android O
- 32. Annotate XML for Auto fill
- 33. Architecture Guide and Components • Google’s opinion on how an app architecture should be built • Fundamental Components which help you build your app • https://developer.android .com/topic/libraries/archi tecture/index.html
- 34. Firebase – What’s new • Firebase Performance Monitoring • Firebase Analytics – Stream View and Debug View
- 36. Use traces to get performance context • Using custom traces, you can understand the context in which performance issues take place, and more easily address them. • You can also make use of automated traces, like app startup time.
- 37. Keep your eyes on network behavior • Automated monitoring of HTTP/S requests. • Track response times, success rates, payload sizes and latency.
- 38. Pinpoint the origin of issues Break down both trace and network data into dimensions like app version, country, device and OS level to get to the bottom of issues.
- 39. Automatic traces • App start traces, which measure the time between when the user opens the app and when the app is responsive. • App in background traces, which measure the time when the app is running in the background. • App in foreground traces, which measure the time when the app is running in the foreground and available to the user.
- 40. Firebase Analytics - Stream View
- 41. Firebase Analytics - Debug View
- 42. References • Android O Notifications: https://developer.android.com/preview/features/notification-channels.html https://developer.android.com/preview/features/notification-badges.html • Google Play App Signing: https://support.google.com/googleplay/android-developer/answer/7384423?hl=en • Auto fill Framework in Android O: https://developer.android.com/preview/features/autofill.html • Architecture Components and Guide: https://developer.android.com/topic/libraries/architecture/guide.html • Firebase Performance Monitoring, Stream View and Debug View: https://firebase.google.com/docs/perf-mon/ https://support.google.com/firebase/answer/7229836?hl=en https://firebase.google.com/docs/analytics/debugview • Android Instant Apps: https://developer.android.com/topic/instant-apps/index.html