Fast Gesture based android launcher
C-Rank Grade: B (Solid) - 78/100
External PR Merge Rate: 100%
Response Time: 3h
First Timer Success: 100%
Elnix90/Dragon-Launcher has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Elnix90/Dragon-Launcher respond to incoming external pull requests in approximately 3.1 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 77.7 places Elnix90/Dragon-Launcher in the B tier.
The external contributor pull request merge rate for Elnix90/Dragon-Launcher is 100.0%, based on public PR activity from non-core contributors.
Elnix90/Dragon-Launcher currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/Elnix90/Dragon-Launcher?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~15 hours (45% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Requirements I checked for duplicate feature in both opened and closed Summary I would like the status bar time (and possibly date) elements to be capable of receiving timezone/offset format specifiers. Problem I am often communicate and travel across the pond, and having the GMT offset available available at a glance is a huge help. This helps to know whether or not my phone has updated timezones between multi-leg flights, and also correctly temporally localize screenshots. Proposed Solution Right now the backend is using Kotlin's local datetime struct and standard datetime utils which construct formatters from strings. I would have thought the formatter constructor had a protocol for falling through and parsing the Java core timezone formats even in the event of lacking timezone data, like e.g. ISO C99 strftime and the date utility, but unfortunately it rejects the Java timezone/offset formats of x/X, z/Z, V, and 0 in both the time and date elements. Likely this is because the loc
Requirements I checked for duplicate feature in both opened and closed Summary Add: Number of version When is the backup created overwrite pervious or create new more options (I have no ideas RN) Problem No response Proposed Solution No response Alternatives Considered No response Additional Context No response
Requirements I've checked for duplicate issues in both opened and closed Description every after reboot i can't open recent using gesture (and via navbar actually) unless i do re switch (switch to default then back to Dragon Launcher) Steps to Reproduce reboot android after reboot try to open recent via gesture or navigation won't work Expected Behavior it should work Actual Behavior not working Version 2.4.1 Device and version Vivo Y100 4G FunTouchOS 15 based on A15 Logs dragon_logs_20260211_095812.txt Additional Context welp it's either android bug or app bug is possible to implement a workaround? and here's a footage about this issues
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 Elnix90/Dragon-Launcher, 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 Elnix90/Dragon-Launcher acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
Elnix90/Dragon-Launcher has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. 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 77.7 places Elnix90/Dragon-Launcher in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Elnix90/Dragon-Launcher currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Elnix90/Dragon-Launcher 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.