Ryan Harter

Flattening my Dependency Graph Jesse Wilson Jesse explores a Gradle module structure that he likes.

Public Mirror Mark (from unsigned.io) Mark explains why he is stepping back from public-facing interaction with his Reticulum projects, and invites anyone who wants to use or continue the project.

I recently reviewed some code at work that made me pause.

I was recently pruning and organizing my RSS subscriptions and indirectly came across Jake Wharton’s hiring page.

Over the past few years I’ve been driving an architecture and tech spec review process at work.

A couple of months ago I was pair programming with a colleague, sharing my screen, and he was amazed to see the number of branches I had in my git repo.

I’ve been using feature gates for a long time.

I was recently working on showing thumbnails for files, and found that the image loading code was surprisingly complex.

When I joined Dropbox almost 2 years ago, I was asked to help improve the screenshot testing experience, resulting in Dropshots.

I recently gave a presentation about how Dagger works under the hood, and I was once again struck by the elegance of the javax.inject.Provider interface.

The other day I happened to notice an interesting question that Michał Zieliński shared in an Android Graphics channel that I frequent.

As Gradle projects and their teams grow, modularization becomes an important tool to help ensure developers can continue to be productive without stepping on each other’s toes.

When coming up with ideas for new ways to solve problems in my code, there are usually a number of unknowns.

As I’ve been refactoring a fairly large section of Pigment, my coloring book app for adults, I came across some SQL code which I haven’t touched in a very long time and didn’t seem quite right.

I’ve used Cashapp’s SQLDelight for years in my Android apps.

When I updated my blog about a month ago, my primary goals were to simplify and modernize things.

Sam Edwards recently posted his strategy for wrapping mock objects to avoid using verbose syntax and facilitate reuse.

Before joining Pixite I spent several years as a freelance Android developer.

A common challenge when writing Android apps is properly scoping objects: if they outlive the lifecycle in which they’re needed then we are wasting memory and they can be leaked, but if we recreate objects too soon then we could be duplicating work when we

LiveData has become an important part of many Android apps.

The AndroidX ViewModel has become a central component in many modern Android apps.

When building development projects on your local workstation speed is important.

Many CI services use an incrementing build number to identify builds.

As I’ve written before, I’m always on the lookout for a great continuous integration and delivery system.

A couple of weeks ago I bought a Google Pixelbook.

A few months ago I was tasked with rewriting the subscription code for Pigment, the coloring book app I work on at Pixite.

For a long time I’ve been in search of a good continuous integration server for Android.

This is the third article in a series on AutoValue.

In my last article, I gave a basic introduction to AutoValue, the code generating annotation processor that makes immutable value types in Java easy.

Value types in Java are hard.

There may be a shortage of love on the internet for AsyncTasks, but that doesn’t mean they don’t have their uses.

I come from the consulting world, where it’s common to try to make everything a library.

RxJava is all the rage in the Android world lately, and with good reason.

Shortly after our initial release of the Pack Store in Fragment earlier this year, other companies started contacting us wanting Fragment on their App stores, as well.

Remember the olden days of Android development?

I’ve finally done it.

We’ve all seen posts about why you should use custom views when applicable and how it can help you properly encapsulate your application code.

One of my favorite new devices from Google is the Chromecast.

One of the most powerful, yet sometimes overlooked, features of Android is the Intent system.

Modern Android apps often make use of gesture interaction to provide fluid, natural interaction with the app.

One of the most important factors in determining whether or not people will buy your app is the rating.

Last week I released Fragment for Android.

In November 2013, Ben Guerrette from Pixite reached out to me after reading my post about my experience being featured on the Google Play.

As a freelance Android developer, I’ve gotten the opportunity to work with many different client environments when it comes to building and releasing Android (and other) apps.

On a recent client app, I ran into a situation where I needed an arbitrary number of EditText fields based on a selected value, where the user could enter people’s information.

In the last post we created a basic Android project using Android Studio templates.

Two months ago, after an unfortunate incident with my Nexus 5 and tile floor, I decided to hop off the Nexus train and get a Moto X.

This is the third post in my Start to Finish series.

This is the second post in my Start to Finish series.

If you checkout the Android Development community on Google+, you’ll find a lot of people asking how to get started building an app for Android.