Google releases source code for I/O app 2018

July 11, 2025 Prithi Pal Thakur

It has become a tradition for Google to release the source code of I/O event Android app after several weeks of the event.

This annual release is done to demonstrate best practices for app development. Developers can take a look at the code to get a better understanding of Google’s best practices for Android App Development.

App architecture

Google’s I/O 2018 app represents a complete rewrite of the application. The app has moved from ContentProvider+SyncAdapter architecture to Architecture Components.

It’s Google’s Android Team current recommendation for developing modern apps for Android. Google has used Kotlin for the rewrite of the application.

Here is the general overview of the app’s architecture –

google-io-18-Architecture.webp

Repository layer is used for handling data operations. Data comes from different data sources –

  • User Data is stored in Cloud Firestore (either remotely or in the local cache)
  • User settings and preferences are stored in SharedPreferences
  • Conference Data is stored remotely and is fetched and stored in the memory

Repository modules are responsible for handling all the data operations.

Dagger2 is used for dependency injection.

Espresso is used for basic instrumentation tests and JUnit and Mockito for unit testing.

Firebase

The Firebase platform has now matured and the use of Firebase technologies has now increased. Following are the Firebase components used in I/O 2018 –

Firebase Cloud Firestore

It is Google’s source for all user data

Firebase Cloud Functions

Firebase Cloud Functions are used to run the backend code. The reservation function, checking user’s status, checking space availability all depends upon on Cloud Functions.

Firebase Cloud Messaging

Cloud Messaging is used to inform the app about any sort of changes in conference data using a ping-and-fetch model.

Firebase Remote Config

Remote Config is used to inform users about WiFi information, conference schedule, etc in a lightweight manner.

Kotlin

Google made the choice of rewriting the app from scratch in Koltin to bring the modern Android architecture. Using Kotlin for the rewrite is an easy choice because –

  • Kotlin’s syntax is expressive, concise, and powerful
  • Support for safety features including nullability and immutability
  • Enhanced Functionality using Android Ktx extensions

Material theming

At I/O 2018, The Material Design team announced Material Theming which give apps the ability to customize Material Design to bring more personalization of their product’s brand.

As the app was released before Material Theming, so they could not use all of the new components but managed to sneak a few including a new Bottom App Bar with inset Floating Action Button.

schedule-169x300-1.webp

The app is available for developers on Github.

Prithi is currently working as Android Architect at VT Netzwelt. He is having 12+ years of industry experience. Prithi has worked on different technology stacks including Android, Kotlin, iOS, Java, J2EE, React Native, Flutter, Web Services. Prithi is currently exploring AI and ML in Mobile app development.

Related Posts

Mobile App Development

Ride-Hailing App Development, Costs, Tech, and How to Launch

Planning a ride hailing app? Get 2026 cost ranges, tech stack, and a clear step by step launch plan. Know when to buy white label or build custom.

August 12, 2026 Himangi Papneja

Cross-platform App Development

Native vs Cross-Platform App Development in the Age of AI Coding Agents

Compare native vs cross-platform app development in 2026. See how AI coding agents affect cost, performance, code review, React Native, Flutter and KMP.

August 11, 2026 Himangi Papneja

Mobile App Development

Swift vs React Native: 10 Reasons to Choose Swift for iOS in 2026

Swift vs React Native in 2026: compare performance, Apple features, security, maintenance, cost, and use cases to choose the right framework for your app.

August 4, 2026 Prithi Pal Thakur