Every year, Google releases a source formula for a I/O Android messenger app several weeks after a developer conference. The 2018 version is critical for a “comprehensive rewrite” featuring Architecture Components, Kotlin, Material Theming, and other complicated elements.
The annual recover is designed to denote best practices for formulating an app used by thousands of attendees to get critical updates, book sessions, and navigate a I/O conference. This 2018 rewrite follows a Android team’s “current recommendations for building complicated apps.”
In regulating Architecture Components introduced during I/O 2017 and finalized after that year, a app is some-more modular, testable, and maintainable. Google sum a app’s pattern in a blog post, and provides a following blueprint of a altogether structure for developers.
Meanwhile, several Firebase services are implemented, including Cloud Firestore, Firebase Cloud Functions, Firebase Cloud Messaging, and Remote Config. Kotlin is also used, with Google job it an “easy choice” to use Android’s newest upheld programing language:
We desired Kotlin’s expressive, concise, and absolute syntax; we found that Kotlin’s support for reserve facilities including nullability and immutability done a formula some-more resilient; and we leveraged a extended functionality supposing by Android Ktx extensions.
On a pattern front, a group records that while a app launched before Material Theming, they “managed to hide a integrate in like a new Bottom App Bar with inset Floating Action Button. Its use authorised Google “to incorporate a lot of a conference’s branding elements,” speaking to how a latest iteration of Material Design allows developers to improved customize and compute an app.
The app is accessible for developers on Github.