If you use Pidcat, there might be issues running the tool if your device is on M+. The issue has been fixed on master but hasn’t been released yet.

Today was the day.

They say all relationships go through a rough patch at two, seven, then ten years. I don’t remember who said it, but someone told me that many years ago.

One of the things we are taught in Android is that we should gracefully handle different layouts based on screen sizes. With more and more things being not just screen size-specific but also OS version-specific, this is one thing I think a lot more devs need to pay attention to. Today was my turn to do just that.

I have been playing with data binding more and more over the last couple of weeks. This week, it’s all about creating a dialog with stuff dictated by a value from an enum.

Say you have a simple layout file:

Sometimes, you can’t help it. You need to look at what happened in the past to understand what is happening in the present (wow).

It has been a month since IO and in case you missed it, I got to chat with Kaushik of Fragmented. And by golly, I made it into an episode! At that point I was about to lose my voice, so I sound really husky. :p

I have previously written about debugging and how Watches can help make inspecting things in your code easier. Today, I would like to reiterate how powerful Watches can be.

One of the most common sources of bugs (at least of my bugs) is math. I have been working on dynamically resizing a View the past days, and it was driving me nuts! I needed to consider preserving aspect ratio, device density, original view size, etc etc. Math is hard guys!