Tammy: a modular Matrix messenger
summary
A modular Matrix client built on a three‑layer stack: Kotlin Multiplatform Trix SDK (Apache) for Matrix core and crypto, a Trix Messenger layer exposing view models, and a UI product implemented with Compose Multiplatform called Tammy. Live demo shows working chat, images, notifications and a multi‑account feature with separate databases and encryption. Timmy is a white‑label/configured variant with about 20 feature diffs and 15 view changes (PIN gating, central phonebook, enforced room pruning). Most code is common (~95%), platform specifics ~5%; some features like reactions and calls remain unimplemented.
AI-written summary · about
chapters (14)
- 0:00Introduction to Tammy
- 1:28Why another Matrix messenger
- 3:40Problems with forking clients
- 4:43Three years of layered architecture
- 6:51Introducing Trix and Trix Messenger
- 9:23Meet Tammy: the UI layer
- 10:08Live demo of Tammy
- 13:40Introducing Timmy: TI messenger
- 18:17Same app, different configurations
- 20:23Extending Tammy for custom use cases
- 23:57Use cases beyond healthcare
- 25:01Where to find the code
- 26:06Licensing details
- 26:27Q&A session
related talks
16mMessaging @Scale
28mBetter apps, less code, more platforms
43mTrio- Compose Architecture with Mavericks
43mMobius-Loopy UI Architecture
17mMercury: A Messaging Framework for Modular UI Components
42mWhat’s New in Compose Multiplatform
57mBuilding a production ready Chat SDK using Jetpack Compose
46mShipping "Smart UI" with RemoteCompose