Skip to content

Instantly share code, notes, and snippets.

@TimonVS
Created March 1, 2016 15:36
Show Gist options
  • Save TimonVS/b54bc5b017524f763a8e to your computer and use it in GitHub Desktop.
Save TimonVS/b54bc5b017524f763a8e to your computer and use it in GitHub Desktop.
<section ng-if="::vm.item.description" class="item-description clearfix" ng-class="{'shorten': vm.shorten}" ng-bind-html="::vm.safeDescription"><p>I’ve been working on the Projectcampus Android application since September, and I must say I’ve learned a lot about Android and personally think the application is coming along nicely.</p>
<p>It all started as a very simple list of hardcoded data, but gradually grew to make use of various Android components such as a Content Provider, Authenticator, Sync Adapter and even custom views. Besides these components I’ve learned about using various mainstream libraries such as Retrofit, OkHttp, Glide, Butterknife, Eventbus, Crashlytics and the Android Support Library.</p>
<p>Retrofit powers the REST communication with the Projectcampus backend in combination with EventBus. EventBus is exactly what it sounds like, an event bus. This makes it possible to launch a REST request from anywhere in the application and also to allow any part of the application to receive any REST response. EventBus is also used for other inner-application communication.<br>Glide is an image loading and caching library used for the various images used throughout the application. All of the networking is backed by OkHttp.<br>Butterknife is a view "injection" library for Android and is used to reduce the amount of boilerplate code. Crashlytics is used to report crashes and errors.<br>The Android Support Library is used for a couple of things like Material support for API levels below 21, Toolbar and new Swipe Refresh Layout.</p></section>
I’ve been working on the Projectcampus Android application since September, and I must say I’ve learned a lot about Android and personally think the application is coming along nicely.
It all started as a very simple list of hardcoded data, but gradually grew to make use of various Android components such as a Content Provider, Authenticator, Sync Adapter and even custom views. Besides these components I’ve learned about using various mainstream libraries such as Retrofit, OkHttp, Glide, Butterknife, Eventbus, Crashlytics and the Android Support Library.
Retrofit powers the REST communication with the Projectcampus backend in combination with EventBus. EventBus is exactly what it sounds like, an event bus. This makes it possible to launch a REST request from anywhere in the application and also to allow any part of the application to receive any REST response. EventBus is also used for other inner-application communication.
Glide is an image loading and caching library used for the various images used throughout the application. All of the networking is backed by OkHttp.
Butterknife is a view "injection" library for Android and is used to reduce the amount of boilerplate code. Crashlytics is used to report crashes and errors.
The Android Support Library is used for a couple of things like Material support for API levels below 21, Toolbar and new Swipe Refresh Layout.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment