Telegram vs GmsCore
Telegram and GmsCore share 8 technologies: activity-compose, core-ktx, androidx.core:core, androidx.fragment:fragment, androidx.appcompat:appcompat, androidx.biometric:biometric, androidx.credentials:credentials, and com.google.zxing:core. Both are written in Java.
What they share and what sets them apart
DrKLO
Telegram
Telegram for Android source
Java30.2kRead on November 7, 2026, at commit 7be672eWhat is Telegram built with?Only in Telegram
- Stripe
- blitz-traits
- com.google.android.gms:play-services-wearable
- navigation-compose
- androidx.car.app:app
- androidx.lifecycle:lifecycle-runtime-ktx
- skrifa
- anyrender
- anyrender_vello_cpu
- blitz-dom
- blitz-paint
- com.google.android.gms:play-services-maps
- compose-bom
- kurbo
- material3
- parley
- play-services-location
- ui
- vello_cpu
- androidx.dynamicanimation:dynamicanimation
- androidx.interpolator:interpolator
- credentials-play-services-auth
- core
- ext-strikethrough
- peniko
pillow
- androidx.exifinterface:exifinterface
- android_logger
- log
In common
- activity-compose
- core-ktx
- androidx.core:core
- androidx.fragment:fragment
- androidx.appcompat:appcompat
- androidx.biometric:biometric
- androidx.credentials:credentials
- com.google.zxing:core
microg
GmsCore
Free implementation of Play Services
Java15.2kRead on November 8, 2026, at commit a03b082What is GmsCore built with?Only in GmsCore
- Jetpack Compose
- androidx.activity:activity
- datastore
- JetBrains
- lifecycle-livedata-ktx
- lifecycle-runtime-ktx
- lifecycle-service
- navigation-fragment-ktx
- navigation-ui-ktx
- preference-ktx
- androidx.preference:preference
- Huawei
- androidx.recyclerview:recyclerview
Google- androidx.mediarouter:mediarouter
- androidx.camera:camera-view
- com.google.accompanist:accompanist-systemuicontroller
- coil-compose
- coil-svg
Side by side
TelegramGmsCore
SizeLines written by people and agents, without generated ones; code files, without tests.
Telegram2,112,466 lines written3,486 code files
GmsCore219,411 lines written2,272 code files
Who writes itA commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
Telegram1.3% of its commits signed by AIWith Claude Code
GmsCore0% of its commits signed by AIWith Cursor
ActivityFrom GitHub and its history, on the day SeeRepo read it.
TelegramLast push November 7, 2026613 commits30,239 stars
GmsCoreLast push November 4, 20262,543 commits15,237 stars
TestsThe files that test the code, and the share of code files a test imports.
Telegram300 test files3.3% of its code files have a test that imports them
GmsCore2 test files0.1% of its code files have a test that imports them
Frequently asked questions
Which is bigger, Telegram or GmsCore?
Telegram, with 2,112,466 lines written; GmsCore has 219,411.
The proof: DrKLO/Telegram's code at commit 7be672e
Which has more GitHub stars, Telegram or GmsCore?
Telegram, with 30,239 stars; GmsCore has 15,237.
The proof: DrKLO/Telegram on GitHub
Which has more tests, Telegram or GmsCore?
Telegram, with 300 test files; GmsCore has 2.
The proof: DrKLO/Telegram's code at commit 7be672e
Which was updated more recently, Telegram or GmsCore?
Telegram: its last push was on November 7, 2026, and GmsCore's on November 4, 2026.
The proof: DrKLO/Telegram's commits on GitHub
Which has more commits signed by AI, Telegram or GmsCore?
Telegram: an AI signed 1.3% of its commits, with Claude Code.
See inside your code, today.
Paste your repo and see it drawn, part by part: a medium one in under a minute.
Free, no account.

