Dispatch Issue # 8

Use the statusBarsIgnoringVisibility WindowInset instead!

Modifier.windowInsetsPadding(
    WindowInsets.statusBarsIgnoringVisibility
)

This window inset ensures that your padding is calculated based on the status bar's height, regardless of its visibility. Your UI elements stay put, and your users stay happy.

Why This Works: The statusBarsIgnoringVisibility insets give you the raw size of the status bar area, even when it's hidden. This way, you can maintain consistent layout spacing without unexpected shifts when the system UI changes visibility.

😆 Dev Delight

OVER.MY.DEAD.BODY

Gradle builds are temporary. Deprecating APIs are permanent 😬

📢 Public Service Announcement

If you're upgrading your compileSdk to 35 (Android 15), you might be in for a surprise. It turns out that using Kotlin's list.removeFirst() or list.removeLast() functions can cause your app to crash spectacularly. 😱

Wait, what? Let's unpack this.

In Kotlin, List is mapped to MutableList, and with Android 15 introducing new List.removeFirst() and List.removeLast() APIs, the Kotlin compiler gets a bit confused. It starts resolving calls to list.removeFirst() to the new platform APIs instead of the Kotlin standard library extensions.

So, if you recompile your app with compileSdk set to 35 and minSdk lower than 35, and then run it on Android 14 or lower, you'll be greeted with a lovely runtime error:

java.lang.NoSuchMethodError: No virtual method removeFirst()Ljava/lang/Object; in class Ljava/util/ArrayList;

Ouch! 😬

Use the NewApi lint option in the Android Gradle Plugin to catch these sneaky new API usages.

./gradlew lint

The Fix? The removeFirst() and removeLast() function calls can be replaced with removeAt(0) and removeAt(list.lastIndex) respectively in Kotlin. Starting Android Studio Ladybug | 2024.1.3, it also provides a quick fix option for these errors.

🤔 Interesting Tidbits

The Great Vesting Schedule Shuffle 💰

While this isn't strictly Android development, it's something that affects many of us in the tech industry. Have you noticed companies getting creative with their equity vesting schedules lately?

Amazon's well-known for their quirky 5/15/40/40 vesting schedule, but Google, Uber, Coupang, ByteDance, and Stripe are joining the party with their own unique twists. It's like they're playing a numbers game, and we're all just trying to keep up! 🎲

What's the deal? Companies are adjusting vesting schedules to better align with market conditions, retain talent, and manage compensation costs. For us developers, it means being extra vigilant when evaluating job offers. That tantalizing first-year grant might look great, but what's happening in years two, three, and beyond?

Why do Compose APIs use Present Tense Callbacks?

Ever wondered why callback lambdas in Compose are named in the present tense, like onClick instead of onClicked? Is it just a quirky stylistic choice? Let's delve into the rationale.

The reasoning is all about semantics. When you see onClick, it's akin to saying "on click event," suggesting that this function is called when a click is happening, not after it has happened. Using the present tense implies immediacy and aligns with the idea that the callback might influence the outcome.

For instance, in a TextField, the onValueChange callback doesn't just inform you that the value has changed—it gives you the opportunity to decide whether the value should change. If it were named onValueChanged, it would suggest that the change has already occurred, which isn't necessarily accurate.

As you can tell, the Compose team put in a lot of thought in coming up with the right APIs and this is one fun detail that I uncovered in some old Slack conversations ✌🏻 So the next time you write a callback in Compose, remember: Present tense keeps you in the present moment 🧘‍♂️

The performance implications of onGloballyPositioned

Performance is king, and when it comes to Compose modifiers, choosing the right one can make a meaningful difference. After all, the Modifier system revamp was one of the very first large improvements Google invested in to improve the performance of Jetpack Compose. Let's talk about Modifier.onGloballyPositioned in particular.

While onGloballyPositioned is incredibly powerful, it comes with a performance cost. Most of us know this already, however, most don’t know why it has such a bad rep.

This modifier gets called whenever any node in the UI tree is placed, which can be quite expensive 😱 It's similar to using ViewTreeObserver. OnGlobalLayoutListener in the old View system—powerful but potentially heavy.

Enter Modifier.onPlaced

If you only need to know when your Composable has been placed by its parent, onPlaced is your friend. It focuses on the node itself and won't trigger when ancestor nodes are placed. This can lead to significant performance improvements, especially in complex UIs. However, there might be valid use cases where you might need to know the position of the node relative to the screen and the ancestor might’ve placed again. In those cases, this modifier might not help so it’s important to know what you are working with and it’s limitations.

When to Use Which:

1. Use onGloballyPositioned when you need to know the global position in the window or screen coordinates, perhaps for creating overlays or implementing drag-and-drop features across different parts of the UI.
2. Use onPlaced when you're only interested in your Composable's position relative to its parent, and you want to avoid the overhead of monitoring the entire UI tree.

🎥 Media Player

One of my favorite videos this year was watching this 10 year old girl use the Cursor IDE to make a fun little website using AI. This is such a wholesome video but more importantly highlights how LLMs are removing barriers to entry in becoming software engineers. If you are an AI pessimist, watch this video and change your mind in real time because there’s no way you can watch it without feeling inspired about the future of programming and the role AI is going to play in enabling more people to build their ideas.

🦄 How you can help?

👉🏻 If you enjoyed this newsletter, I'd greatly appreciate it if you could share it with your peers and friends. Your support helps me reach more Android developers and grow our community. Writing this newsletter takes time and effort, and it truly makes my day when I see it shared within your network. Consider tweeting about it or sharing it in your team's Slack workspace. Thank you!

👉🏻 If you find this newsletter or any of my other free websites or open source contributions useful, consider supporting my work 🙏🏻

👉🏻 Get my Maker OS Notion Template that I use to run my life on Notion. If you are into productivity, you will appreciate it! Here’s a quick preview of what it looks like—

On that note, here’s hoping that your bugs are minor and your compilations are error free.