# Monogram: Open-Source Telegram Client for Android Built with Kotlin and Jetpack Compose
Developers have released Monogram — an unofficial Telegram client for Android. The project uses Kotlin, Jetpack Compose, and TDLib. The code is available on GitHub under GPLv3. The client focuses on native Material Design 3, high performance, and minimal resource consumption. The authors emphasize active development with frequent updates and possible bugs.
The motivation behind its creation is issues with the official client: overly complex monolithic code, delays in publishing source code, and a controversial redesign incorporating iOS elements like background blur and translucency. Monogram addresses these problems by ensuring transparency and adherence to Android standards.
Technical Foundation and Key Features
Networking, MTProto, and end-to-end encryption are handled via TDLib in C++. The client logic is built with modern Android tools to optimize performance.
Key features:
- UI built with Jetpack Compose and Material Design 3: built-in media components reduce CPU/GPU load.
- MapLibre for rendering maps and geodata.
- Session protection: system biometrics for local.
This delivers smooth animations and battery savings compared to monolithic alternatives.
Risks of Popular Alternative Clients
Research by RKS Global uncovered vulnerabilities in 8 clients. Most send data to Russia or use Firebase Analytics in violation of official Telegram policy.
Tested projects:
- Telegram Official.
- Telegram X.
- Plus Messenger.
- Nekogram.
- Graph Messenger.
- Telega.
- iMe.
- F-Droid (Forkgram, Mercurygram).
Problems:
- Telega, Graph Messenger, iMe send data to Russian servers.
- Plus Messenger, Graph Messenger, iMe, Nekogram include Firebase Analytics (Google tracks usage).
- Ad SDKs: Graph Messenger (6), iMe (15+), Plus Messenger (1). Traces of VK in Telega and iMe.
- Telega swaps MTProto servers for its own proxies in RF.
The official client disables Firebase, but forks reactivate it.
Key Points
- Monogram uses TDLib for secure MTProto, avoiding custom proxies.
- Full compliance with Material Design 3 without iOS knockoffs.
- Open source under GPLv3 ensures transparency.
- Minimal resource usage: Compose + native components.
- Active development, but with bugs — aimed at middle/senior devs.
Prospects for Developers
The project is ideal for learning Jetpack Compose in a real-world scenario. The architecture is modular, unlike the official monolith. MapLibre integration demonstrates replacing Google Maps without vendor lock-in.
For contributors: focus on TDLib integration performance and biometrics. Testing MTProto edge cases is essential due to criticism of forks.
— Editorial Team
No comments yet.