jetc.dev Newsletter Issue #102
1.1.0 is… not yet stable! But, we now have an
rc03, in addition to
(what? that’s not your favorite subject?!?)
Reviewing the release notes for the latest Jetpack Compose update!
This past week, we got
1.1.0-rc03. There were no obvious significant changes, though
Google reiterates that Compose Material widgets have minimium touch target sizes.
We also got
1.2.0-alpha02. Among other changes, this alpha includes:
Mouse wheel scrolling support for
onPreRotaryScrollEvent()modifiers (for watches with crowns that rotate)
We also got an update to Glance, which includes a new
artifact. More on this below!
One Off the Stack, One Off the Slack
You’ve got questions. That’s understandable!
Sometimes, you want to react to key events outside of having something like a
TextField() with the focus. For example, you might be interested in responding
to D-pad input from a remote control in a TV app. How to do that in a Compose-friendly
way is the subject of this week’s highlighted Stack Overflow question.
We often have the opportunity to provide “key” objects to composables. When the key
changes, the composable will get recomposed. But, we see some samples where
the key is a constant. We explore whether or not that’s a good idea in this week’s
#compose Slack thread.
Posts, videos, and other new information related to Jetpack Compose!
We have had alpha releases of Glance for a while, but only with support for app widgets. Now, the second half of Glance is out, with support for creating tiles in Wear OS apps. Tiles on Wear OS fill a similar role as do app widgets on phones and tablets, and now our code can be similar as well (and composable as a bonus)!
Medium user Pedro wanted to use Compose Material but with a theme that was based
only partially on
MaterialTheme(). This requires a bit of reverse-engineering,
to determine how Compose Material composables use
MaterialTheme(), so alternative
typography, shapes, etc. can be applied.
Medium user Frank continues our tour of Navigation for Compose. In this case, Frank examines how state — not events — can handle navigation from composable to composable, to better align with how Compose operates.
Sebastian Lobato Genco created the Resaca library
that I mentioned two weeks ago. In this post, Sebastian explains the rationale behind
creating Resaca and its
rememberScoped() function, to try to have narrower viewmodel-style
objects for use by specific reusable composables.
ConstraintLayout is very popular in the classic
View system, but not everybody
realizes that there is a ConstraintLayout for Compose UI as well. Shrey Sindher
walks us through why you might want
ConstraintLayout in a composable and how
ConstraintLayout capabilities — such as guidelines and chains —
translate to a Kotlin DSL.
Chips are popular UI elements. Kamaldeep Kumar reviews how to create various styles of chips from scratch using basic composables.
Other Interesting Links
- Video: Speed Development Using Jetpack Compose
- State Management in Android Jetpack Compose
- Medium: Achieving better baseline alignment for fonts in Jetpack Compose
- Medium: Speed Up Mandelbrot Drawing on Android Jetpack Compose
- Into the Compose-Verse, A beginner guide to Android Development With Jetpack Compose
- Medium: Introduction to Jetpack Compose
- Medium: Traditional MVVM with Jetpack Compose and StateFlow
- Medium: How to implement pagination in Firestore using Jetpack Compose?
100% pure code!
Tanawin Wichit created a set of libraries that combine to provide a Material3-based,
responsive media selection UI. The library handles rendering the previews of the
media, and you get a list of
Uri objects back representing the selections.
Other Interesting Links
- GitHub: MhmoudAlim / Compose-Ratingbar-library
- GitHub: Size0f / android.compose.squircle
- GitHub: keygenqt / compose-routing
…And One More Thing
@Preview in the IDE. Showkase
also lets us use
@Preview-annotated composables for screenshot testing.
For me, the next step is: use
@Preview as part of generating documentation.
Principally, my concern is for library documentation. Having screenshots (or GIF animations) of composables is really quite useful for developers hunting for a library that might solve particular UI concerns. Having up-to-date screenshots be generated automatically as part of publishing the documentation can be a big win. Manually generating screenshots is a pain, which means that either:
We don’t get many screenshots, or
Those screenshots may not be maintained and could be out of sync with the actual code base
However, the value of documentation is also valid for in-house use by development teams. While Showkase works nicely in-app, browsing composables in the app may or may not be the most efficient course of action for bulk knowledge transfer (think: onboarding new team members).
In principle, the
@Preview-rendering logic from the IDE could be made available
for documentation Gradle tasks. After all, the IDE is not running Android. Or,
perhaps we could get something out of Compose for Desktop that serves the same role.
This idea is in the “Coming Soon!” list for Showkase. Between them and other independent developers, with luck, we can get something in this area in the not-too-distant future.
- 2022-05-17: Google I|O 2022 videos! Compose beta01! Layout()! State! drawBehind()! Credit cards! App intros! And... what's a horologist?!?
- 2022-05-10: StateFlow vs. State! Design systems! MotionLayout! Text editing problems and solutions! And... modal sheets that are actually modal?!?
- 2022-05-03: @aditlal and @JorgeCastilloPr on design systems! KMP + Compose + SwiftUI! Dropdowns! FABs! And, what does Google I|O 2022 have in store for Compose UI developers?