Five chips under the app bar, each carrying its count, scrolling sideways. The row is outside the list rather than its first item, because a control that scrolls away is a control the reader has to scroll back for -- and the list it filters is as long as the group's whole signing history. It scrolls rather than wraps for the same reason from the other side: five counted chips do not fit the sixty characters `readableContent` holds the column to at the largest text size a reader can ask for, and a row reflowing to a second line moves the list under the thumb about to tap it. Unfiltered, the two sections stay. Filtered, they go: "waiting for you" against "everything else" is a distinction the reader has already made by tapping, and heading a single-state list with it would answer a question nobody asked. A room with nothing in it gets no chips at all. Five chips reading 0 over an empty screen would be five ways of saying what the empty state says once. The screen also picks up the state widgets it never had -- `LoadingDataIndicator`, `ErrorState` with an explicit `onRetry = null` because a room missing from this device will not appear by looking again, and `EmptyState` with a message per filter. That last one is the point: one shared default is how five different absences here came to say one thing. A group never asked to sign and a queue the reader has worked through are not the same fact, and the second is not an absence at all -- it keeps the queue's own icon and reads as finished. `initialFilter` reaches the screen and is applied in the view model's `init`, so a `Loaded` handed in for a preview cannot open with its chips saying one thing and its rows showing another. Nothing passes it yet. Fourteen screen tests, and the audit's budgets all still met: 0 hardcoded colours, 0 dp literals in spacing positions, 0 title-case strings, both floors held. 1329 jvm tests pass; the Android target compiles. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…