How We Develop Mobile Applications - Pt 2 - Android

Getting our environment setup for Android
By Joshua Kovach

Now that you know what your mobile application will do and look like, it’s time to get your various environments set up. Here’s our list of things we check off at Collective Idea for creating an Android app.

How We Develop Mobile Applications

Best practices from Collective Idea
By Tim Bugai

Developing a mobile application that works on both iOS and Android takes a bit of work. Here are some best practices to get you going.

Retrofitting Espresso

How to get Espresso to wait for RxJava's background schedulers
By Joshua Kovach

You don’t need an IdlingResource, and sleep() is fickle. Make Espresso wait for your observables running on background schedulers with this one cool trick!

Your User Can’t Click Your Floating Action Button

And you can fix it in one line
By Victoria Gonda

An easy way to make your Android app’s main action more accessible for people using screen readers.

Stubbing your Android Intents

Know your intent was sent without the Activity opening
By Victoria Gonda

When we stub an intent, we are able to intercept it so the intent is never sent to the system, and specify how it should respond. This can be helpful in your Android tests when you need to know if an intent was sent, but you don’t actually need the Activity to start. This can be accomplished by using espresso-intents.

Testing for Android Intents Using Espresso

By Victoria Gonda

Using espresso-intents for testing Android Activity Intents