The product manager should be worried that their developers have been preventing the app from being used as apps should be able to be used (e.g multi-window mode).

They're merely being made to implement something that they should have already been supporting. It takes more effort to just block it.

Thinking about configuration changes isn't optional.

Imagine a website trying to prevent the browser window from being resized or breaking when it does. Android apps can't disable configuration changes and need to react to them correctly without losing state using the tools available.

Today is my last day at Google. I joined as an intern almost 18 years ago, and it still feels like it was yesterday. I'm incredibly grateful that I got to work with so many amazing and talented folks, but I'm also excited to try something new. First step: a few months of travel and photography :)

Look at how Wolt engineers created this seamless collapsing toolbar and cross-fade animation using CoordinatorLayout behaviors, RecyclerView, and nested scrolling.

Top-tier Android UX 👍 #androiddev

Not gonna lie, Wolt engineers went all-out on this app!

I'm really fascinated by how the horizontal RecyclerView tracks the current category, depending on the current scroll position of the vertical RecyclerView.

The circular reveal and the CoordinatorLayout behavior is cherry on top! Super cool.

oh no

Introduce a new customizable shadow framework.

This includes DropShadowPainter and InnerShadowPainter as
well as the DropShadow/InnerShadow dependencies.

android-review.googlesource.com/c/platform/f...