The Android team at Orion Labs has been using Tuple for a few months now. Our team is distributed across the country and using Tuple has really helped synchronous connections on the team. I thought I would share a few simple tips/tricks to get the most of the experience.
This is part 2 in a series about different caches available to Android Gradle projects. In part 1 we walked about the benefits provided by Gradle’s cache of incremental builds and the build cache directory. In the second half here, we talk about Android’s build cache, the Gradle daemon, and dependency caching
There are several ways Gradle stores information between builds to drastically reduce subsequent build times. You may be familiar with some of these methods, but what’s important is that they build upon each other gradually improving build speed. If you are only benefiting from one, then you have something to gain by also looking into the others.
I’m sharing the story of a bad situation I had ordering a new phone through Google Fi. It turned into a two month long ordeal where the service got worse and worse. At every turn the Google Fi team was presented with a chance to make things better and every time they blew it. I’m sharing this because I hope a long form review of the process is helpful to other potential Google Fi customers.
I want to get this out quick without a lot of polish because something is better than nothing.
We use Spoon to aggregate our end-to-end tests and capture screenshots of our Android app. In order to save these screenshots, our app’s
AndroidManifest.xml needs to declare the
However this is the only reason that our app needs this permission. We don’t write to external storage any other time in the actual app. So my goal was to remove this permission from our app manifest and see if I could instead declare it our test