Goal for this part
Show a simple activity log for moves.
Treat 11-Activity as the source of truth for this checkpoint. If your local tree drifted, re-clone that folder rather than mixing files from neighbors.
What you should already know
You do not need prior Compose experience for part 1. Later parts assume you finished the earlier snapshots on the same machine.
- JDK 17+ and a working Gradle wrapper are available
- You can run
./gradlew runfrom a terminal - You have a desktop session for the Compose window
Why Compose fits Boardlane
Compose Desktop lets you build native window UIs with the same declarative Kotlin you use on Android—great for a board of cards without HTML chrome.
Columns of cards map cleanly to LazyColumns. Keep board mutations in a small repository so recomposition stays cheap.
After you run the snapshot, you should recognize the behavior described in the goal—before you move on. If the window (or server) never appears, stop and fix the run steps.
Code shape
Snapshots stay small on purpose. Look for this kind of core call as you read the folder:
db.execute("INSERT INTO cards(title, column_id) VALUES (?, ?)", title, columnId)How to run it
Clone the teaching repo, open 11-Activity, install what the README asks for, then run ./gradlew run.
git clone https://github.com/michaeldunga1/fcc-compose-kanban.git
cd fcc-compose-kanban/11-Activity
./gradlew build
./gradlew runCommon mistakes
- Ignoring platform-specific install notes in the snapshot README
- Hiding a feature in the UI without enforcing it in code
- Leaving trash/spam actions irreversible
- Forgetting a status message after a bulk action