Multiple samples showing best practices in app and watch face development on Wear OS.
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 59%
Response Time: -
First Timer Success: 67%
android/wear-os-samples has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in android/wear-os-samples respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 54.1 places android/wear-os-samples in the B tier.
The external contributor pull request merge rate for android/wear-os-samples is 59.1%, based on public PR activity from non-core contributors.
android/wear-os-samples currently has 10 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in android/wear-os-samples.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/android/wear-os-samples?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (74% approval). Large PRs (>500 lines) take ~115 hours (27% approval). Keep your diff compact for rapid review.
Description Lint reports 42 bitmaps in res/drawable/, which has no density qualifier: 36 in WearTilesKotlin/app and 6 in WearWidget/app. They are Tile preview images (tile_preview_*.png), images used in Tile layouts (avatar*, photo_*), and Widget preview images (hello_widget_*.png, weather_widget_*.png). Android treats res/drawable/ as mdpi and scales bitmaps from it by the device density when they are loaded. On a typical xhdpi watch, each image is scaled to twice its width and height. That uses more memory and blurs the image. This report doesn't cover the IconLocation findings in WatchFaceFormat and WatchFacePush/samples. Watch Face Format images are drawn on a fixed canvas, so density folders don't apply to them. Environment Repository: android/wear-os-samples, main at 06cdb24c (the head of main on 2026-09-28) Command: ./gradlew lint, run in WearTilesKotlin (AGP 9.2.0), WearWidget (AGP 9.2.1). Each project uses the Lint version bundled with its own Android Gradle Plugin (AGP). JDK
Description Lint reports 175 outdated dependencies, plugins, SDK levels, and Gradle wrappers across all 9 samples. The repository has a Renovate configuration, but versions still differ widely between samples: Sample AGP Gradle Findings Complications 8.13.1 9.2.1 5 ComposeStarter 9.1.0 9.4.1 20 DataLayer 8.13.1 9.2.1 23 WatchFaceFormat 9.0.0 9.2.1 19 WatchFacePush 9.1.1 9.4.1 12 WearOAuth 8.13.1 9.2.1 27 WearSpeakerSample 8.13.1 9.2.1 25 WearTilesKotlin 9.2.0 9.4.1 15 WearWidget 9.2.1 9.4.1 29 In WatchFaceFormat, 5 of the findings are compileSdk values of 33 or 34 in Complications, Flavors, SimpleAnalog, SimpleDigital, and Weather. These findings depend on the date Lint runs, because they compare against the latest published versions. Environment Repository: android/wear-os-samples, main at 06cdb24c (the head of main on 2026-09-28) Command: ./gradlew lint, run in Complications (AGP 8.13.1), ComposeStarter (AGP 9.1.0), DataLayer (AGP 8.13.1), WatchFaceFormat/*
Description The adaptive launcher icons in ComposeStarter, DataLayer/Application, DataLayer/Wearable, WatchFacePush/app, and WearSpeakerSample have no <monochrome> layer, so they can't be shown as themed icons. Environment Repository: android/wear-os-samples, main at 06cdb24c (the head of main on 2026-09-28) Command: ./gradlew lint, run in ComposeStarter (AGP 9.1.0), DataLayer (AGP 8.13.1), WatchFacePush (AGP 9.1.1), WearSpeakerSample (AGP 8.13.1). Each project uses the Lint version bundled with its own Android Gradle Plugin (AGP). JDK: 21 Date: 2026-09-28 Lint rule MonochromeLauncherIcon: rule documentation · detector source Lint's explanation for MonochromeLauncherIcon: The system may use the coloring of the user's chosen wallpaper and theme to tint app icons. Providing a <monochrome> layer (which will be used for tinting) for every adaptive icon is strongly recommended, otherwise Android 16 QPR 2 and above will simply tint the color version of the icon, which may look unusual.
Description Lint reports 13 findings across 7 samples that don't change behavior, but are patterns developers shouldn't copy. Lint ID Findings Location ObsoleteSdkInt 5 res/mipmap-anydpi-v26/ in ComposeStarter, DataLayer/Wearable, WatchFacePush/app, WearSpeakerSample, WearTilesKotlin, which all have minSdk ≥ 26 UseKtx 3 Uri.parse(...) in DataLayer/Application and WearOAuth/oauth-device-grant StaticFieldLeak 2 private val context = getApplication<Application>().applicationContext in the two WearOAuth view models RedundantLabel 2 <activity android:label> that repeats the <application> label in WearSpeakerSample and WearWidget DefaultLocale 1 String.format("%02d", minute) in WearTilesKotlin/app/src/debug/.../golden/Alarm.kt The StaticFieldLeak findings are not real leaks, because the stored object is the application context. The warning goes away if the context isn't stored in a field. Environment Repository: android/wear-os-samples, main at 06cdb24c (the head of main
Description Lint reports 5 findings about exported components and backup settings in WearWidget, DataLayer, and WearOAuth. WearWidget: WeatherUpdateReceiver accepts broadcasts from any app. AndroidManifest.xml, line 116 exports the receiver without a permission, so any installed app can change the widget's weather. It's exported so that the README's adb shell am broadcast command can reach it. DataLayer: MigrationDataLayerService is exported without a permission. Application/src/main/AndroidManifest.xml, line 45 exports a Wearable Data Layer service that receives NODE_MIGRATED. The export is required, because Google Play services binds to the service from another process. WearOAuth and WearWidget: android:allowBackup without android:dataExtractionRules. WearOAuth/oauth-device-grant and WearOAuth/oauth-pkce set android:allowBackup="false", and WearWidget sets android:allowBackup="true". For apps that target API 31 (Android 12) or higher, allowBackup only controls cloud backup. It doesn'
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to android/wear-os-samples, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of android/wear-os-samples acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.1% were successfully merged into the primary branch.
android/wear-os-samples has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 54.1 places android/wear-os-samples in the Solid tier.
The external pull request merge rate is 59.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, android/wear-os-samples currently has 10 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for android/wear-os-samples are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.