GmsCore vs DiPlay
GmsCore and DiPlay share 5 technologies: Jetpack Compose, androidx.activity:activity, activity-compose, lifecycle-runtime-ktx, and com.google.zxing:core. GmsCore is written in Java and DiPlay in Kotlin.
What they share and what sets them apart
microg
GmsCore
Free implementation of Play Services
Java15.2kRead on November 8, 2026, at commit a03b082What is GmsCore built with?Only in GmsCore
- datastore
- core-ktx
- JetBrains
- lifecycle-livedata-ktx
- lifecycle-service
- navigation-fragment-ktx
- navigation-ui-ktx
- androidx.core:core
- preference-ktx
- androidx.appcompat:appcompat
- androidx.preference:preference
- androidx.fragment:fragment
- Huawei
- androidx.recyclerview:recyclerview
- androidx.mediarouter:mediarouter
- androidx.camera:camera-view
- com.google.accompanist:accompanist-systemuicontroller
- androidx.credentials:credentials
- androidx.biometric:biometric
- coil-compose
- coil-svg
In common
- Jetpack Compose
- androidx.activity:activity
- activity-compose
- lifecycle-runtime-ktx
- com.google.zxing:core
shihabal3amri
DiPlay
Independent CarPlay receiver for compatible Android head units. Wired and wireless public preview.
Kotlin13.5kRead on November 10, 2026, at commit 615b32cWhat is DiPlay built with?Only in DiPlay
- app-projected
- androidx.core:core-ktx
- androidx.car.app:app
- appcompat
- ui-graphics
- androidx.media3:media3-ui
Side by side
GmsCoreDiPlay
SizeLines written by people and agents, without generated ones; code files, without tests.
GmsCore219,411 lines written2,272 code files
DiPlay177,301 lines written562 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.
GmsCore0% of its commits signed by AIWith Cursor
DiPlay28.5% of its commits signed by AIWith Claude Code, GitHub Copilot, and Codex
ActivityFrom GitHub and its history, on the day SeeRepo read it.
GmsCoreLast push November 4, 20262,543 commits15,237 stars
DiPlayLast push October 28, 2026957 commits13,529 stars
TestsThe files that test the code, and the share of code files a test imports.
GmsCore2 test files0.1% of its code files have a test that imports them
DiPlay490 test files63.9% of its code files have a test that imports them
Frequently asked questions
Which is bigger, GmsCore or DiPlay?
GmsCore, with 219,411 lines written; DiPlay has 177,301.
The proof: microg/GmsCore's code at commit a03b082
Which has more GitHub stars, GmsCore or DiPlay?
GmsCore, with 15,237 stars; DiPlay has 13,529.
The proof: microg/GmsCore on GitHub
Which has more tests, GmsCore or DiPlay?
DiPlay, with 490 test files; GmsCore has 2.
Which was updated more recently, GmsCore or DiPlay?
GmsCore: its last push was on November 4, 2026, and DiPlay's on October 28, 2026.
The proof: microg/GmsCore's commits on GitHub
Which has more commits signed by AI, GmsCore or DiPlay?
DiPlay: an AI signed 28.5% of its commits, with Claude Code, GitHub Copilot, and Codex.
The proof: the commits each tool signed in shihabal3amri/DiPlay
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.

