Newsletter Issue #22

Published: 2020-07-14

In this week’s issue, we look at streams of immutable objects, with a particular emphasis on StateFlow. We also have some dialogs, look at supplying sample data to our composable previews, and watch some FABs go 💥.

One Off the Stack, One Off the Slack

You’ve got questions. That’s understandable!

Once again, there were few good answers in Stack Overflow in the android-jetpack-compose tag.

Immutability and Changes

In short, Compose likes streams of immutable objects.

Composable Commentary

Posts, videos, and other new information related to Jetpack Compose!

Building an Exploding FAB Transition With Jetpack Compose

Joe Birch returns, this time where he blows up innocent little FABs who never meant any harm to anyone… 😁

Change my mind or Android development transformation to Jetpack Compose & Coroutines

Andrey Beryukhov has a lengthy post exploring creating a basic Compose app, using StateFlow and MVI-style architecture.

Sample Data in Compose Previews

Jossi Wolf explores @PreviewParameter. You can add this annotation to a single parameter of a @Preview-annotated function, to teach the preview system how to obtain some data, such as sample data to use in rendering the preview.

The Journey of Jetpack 🚀 — Introduction

Manuel Ernesto has a series of posts exploring various aspects of the Jetpack. This post is an introductory look at Compose, for newcomers to the subject.

Kotlin Jetpack Compose

Ebubekier Sezer offers another introduction-to-Compose post, for newcomers.

Resource Roundup

100% pure code!

GitHub: husseinala / neon

Hussein Aladeen offers a wrapper API around different image-loading libraries (Glide and Picasso) to tie them into composables.

GitHub: vanpra / compose-material-dialogs

Pranav Maganti is back, this time with some Material Design-styled dialogs implemented in Compose, including single- and multiple-choice list dialogs.

…And One More Thing

Just a quick reminder: Google is not scheduled to release another Compose and Compose UI set of updates until July 22. So, if you were wondering where dev15 was, we should be getting it next week.

At least, it is probably dev15.

According to Google’s stated timeline, in theory we are due for the first alpha release within the 9 weeks or so. Conceivably, this delay is setting the stage for that first alpha.

However, I doubt it. Based on the Kotlinlang Slack discussions, there still seem to be quite a few larger changes due, ones that I would expect (hope?) would land before the alpha series begins. This skipped cycle could be tied to some of that work, or it could simply be slowing the development pace a bit to allow engineers to relax and perhaps get a bit of time off.

Of course, for all we know, Google will change the naming scheme to something totally different, and we will get the turboSystem5000 release instead.

But, probably, we will get dev15, and get to see what changes are in store for us.