On the 10th of November 2015, I had the opportunity to give a talk about Dagger 2 at Droidcon Paris. Slides are in French and available on Speaker Deck. Code from live coding is available on Github. Finally, the video has been released on Youtube.

Writing tests is painful, it is not the part of our job we all prefer, however it is mandatory. Indeed, it allows us to guarantee behaviors, features and non-regression. Therefore, since it is such a pain but so important, we need great tools to help us. Truth is one of them.

This article is a translation of an article I wrote in French and published on Xebia blog.

When developing an Android application, we often, if not always, have to make network calls. So we regularly need to launch ourselves the backend application on our computer to develop and test.

However, our IP address is unique to each developer and forced them to change their build.gradle. This change presents a risk since such modifications can be pushed on the Git repository and cause problems to the environment of other developers. Therefore, how do we make our Android app directly know our backend and therefore our local IP address?

Even better: is it possible to handle this directly on the build? This is what we will see in this short article.

I recently gave a talk to my backend colleagues about the network stack we use on Android. This stack uses okio, OkHttp and Retrofit. Slides are in French and available on Speaker Deck. Code from live coding is available on Github. The idea between this talk was to show how much powerful OkHttp/Retrofit are and how stupid it would be to not use it when backend server needs to consume other backend APIs. We, on Android, are obviously experts on this subject and therefore have great tools at your disposal.

This article is a translation of an article I wrote in French and published on Xebia blog.

In the Android community , access to samples , tutorials , articles on the latest widget or library is commonplace. However , it is very difficult to get good articles or documentation on the development of an architecture for testing an Android application.