Recap of the google io 2017
•
0 likes•146 views
A talk given by me at the June "Mumbai Android Developers (MAD)" meetup. I gave a recap of the Google I/O 2017 from a user as well as developer point of view. Being an Android meetup, we concentrated on the Android launches, framework updates and the overall momentum change in the tech world.
Report
Share
Recap of the google io 2017
- 1. Recap Of Google I/O 2017the
- 2. 3 8000+ 424+
- 3. Main Theme?
- 4. Mobile First to AI first
- 5. “It will take all of us working together, to bring the benefits of technology to everyone” - Sundar Pichai
- 7. ● Google Lens ● Photos - Suggested Sharing ● Photos - Shared Libraries ● SmartPhone VR ● Tango AR ● Chromecast 360 support ● Cloud TPUs ● Google.ai ● Machine Learning Engine ● TensorFlow 1.2 ● Progressive Web Apps ● Polymer
- 8. A total of 60+ launches for Android which directly impact us
- 9. ● Actions on Google ● ● ● Architecture components ● Play services update ● Support Library update ● Android Instant Apps ● Android Go ● ● Kotlin ● ● Play Console Dashboard ● ● Android Studio Profilers ● ● Firebase Cloud functions ● ● Flutter ● Android Things
- 10. My Top 5 Picks
- 11. Kotlin ● Makes development faster and enjoyable ● ● ● A new language learnt ● ● ● Server-side development
- 12. Architecture Components ● Way to develop architect apps better ● Handles majority some of the challenges we face with the framework ● Makes lifecycles more stable clear ● Embraces the advances of third-party libraries and supports them ● Less boilerplate than Sqlite, but with the same speed ● Provides each component separately
- 13. Phone number selection & SMS Reading Current flow: ● Phone number entered ● Phone number sanity checked ● Number sent to server ● Server sends OTP msg ● We create broadcast-receiver ● We ask for “Read SMS” permission ● We receive broadcast ● We pass it to the activity to continue Cons: ● User takes time ● User may make mistakes ● User thinks app will read all SMSs ● User does not give permission ● User does not enter OTP ● User leaves app ● Project manager is angry, developer is sad
- 14. Phone number selection & SMS Reading Your app receives a broadcast with the content.
- 15. Android Studio Profilers CPU Usage? - Adding logs to functions, finding bottlenecks, fixing issue, removing logs Memory Leaks? - LeakCanary Network Debugging? - Stetho, Chuck, NetworkInterceptor (OkHttp) Handle dependencies in Release and Debug builds CPU Profiler - Info about the time taken by code on the CPUs and threading info Memory Profiler - Identify memory leaks at runtime, click to piece of code and fix faulty code Network Profiler - View and debug the network calls. OkHttp also supported
- 16. Instant Apps ● Users use 4-6 apps weekly ● Most apps uninstalled in a day ● Older apps uninstalled to make space for other apps ● Download, install, view, uninstall ● Uninstalls impacts Google Play standings ● App runs through Google Play as a native app ● Activated via “App Links” ● No installation needed. Internet needed. ● Android 6.0+ (Coming to 5.0+ soon) ● Requires your project to be build in modules. 8 Step process ● Modularization is complicated and should be done for core business as of now
- 17. Special Mentions Android Go ● ● Play Console ● ●
- 18. Summary Not everything is for you “right now” Always best to know what is out there! Play, Create sample apps, Upload to Github, Share, Learn! Use only stable elements in business apps Report bugs and request features to the Google team ● Kotlin ● Architecture components ● Phonenumber selection & SMS reading ● Android Studio profilers ● Instant Apps ● ●
- 19. Thanks!