Playing with elevation in Android 🥧 (part 1)
With Android Pie we gained the ability to tint our shadows. This mini-series looks into how this works and how to make the most of it.
Sebastiano Poggi
45 posts
Kotlin and Android #3 — Know your properties
tl;dr Kotlin properties are awesome and super powerful, but each form comes with a bunch of gotchas. Make sure you fully understand them…
Kotlin and Android #2 — Treacherous properties
Developers love properties in Kotlin, but a property is not always the right choice. Getting carried away can be risky, so when should we avoid properties?
Kotlin and Android #1 — by lazy
Many people love by lazy, but it's easy to underestimate and misuse it. When should you use lateinit, and when is by lazy a better choice, as an Android developer?
Kotlin and Android — An opinionated series (intro)
In this series we're going to be looking at a few common patterns I have seen Android developers use in Kotlin, and see what's the good and bad in each, and when to use them.
Quick Android Studio tip: debug logs without code
Instead of writing debug logging code, you can take advantage of the IDE tools. No more log statements forgot here and there!
Ooga-chaka: Git hooks to enforce code quality
Use git hooks to prevent code formatting and static analysis from making your CI unhappy.
Playing with elevation in Android
Material Design dictates sheets must have a shadow, and most devs think that it cannot be customised beyond the elevation value. But they're not exactly right…
Where do layout_* attributes belong?
Not all attributes are created equal. Some are more equal than others, so where should you put your layout_* attributes?