Google releases source code for I/O app 2018
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 –
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. Read More
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 –
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. Read More


Comments
Post a Comment