Zulip mobile apps for Android and iOS, using Flutter.
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 44%
Response Time: 22h
First Timer Success: 25%
zulip/zulip-flutter has a recorded first-timer success rate of 25.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zulip/zulip-flutter respond to incoming external pull requests in approximately 21.8 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 51.9 places zulip/zulip-flutter in the B tier.
The external contributor pull request merge rate for zulip/zulip-flutter is 43.8%, based on public PR activity from non-core contributors.
zulip/zulip-flutter currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in zulip/zulip-flutter. Maintains strict focus on technical quality and test standards.
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/zulip/zulip-flutter?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 17:00 to 21:00 UTC (17:00 - 21: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 ~14 hours (55% approval). Large PRs (>500 lines) take ~104 hours (20% 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.
Alternative open-source projects with active maintainers in Dart.
Libraries supporting GraphQL in Dart
A library for building statically-typed React UI components using Dart.
Gleec Wallet
The server now has a notion of a user being "deleted" but still in the database, and still in the list of users sent to clients. This is a step beyond the existing "deactivated" state; the relevant differences are: Data like the name and avatar will have been scrubbed, replaced with placeholder data. The new is_deleted field on the user object will be true, to signal that this happened. We should look for this field, and when present avoid consulting other fields like user.fullName. Instead, we'll show e.g. "(deleted user)" for the name (akin to the existing "(unknown user)"). References #api documentation > new feature level: 490 #api design > flag for deleted users in UserProfile zulip/zulip#38374
Uploading a file inserts [...](...)\n\n where the cursor is -- with no proceeding whitespace. We should match the web behaviour of adding a newline before (if it's not at the start of a line already) and one one trailing newline. CZO discussion.
See #api documentation > new feature level: 475: GET /events: realm_user events with op: "update" are now sent when the date_joined field is updated after an imported stub user or a user created via the API logs in for the first time. GET /users, GET /users/{user_id}, GET /users/{email}, GET /users/me: The date_joined field is initially set to the account creation time and is updated to the time of first login for imported stub users and users created via the API. Tim elaborates that this means two changes for the mobile app: Showing something to the effect of "Imported on" rather than "Date joined" as the string if is_imported_stub is true for a user whose card information is being displayed. Being able to handle events that live-update is_imported_stub and date_joined if/when such a user joins in a way that converts the account from an imported stub into a real account. and offers a tip for manually testing those changes (and producing screenshots): There's a new "Imported u
The server recently introduced a new realm setting media_preview_size, in feature level 469. API changelog: PATCH /realm, POST /register, GET /events: Added a new media_preview_size realm setting that controls the size of image and video thumbnails in messages. We should follow that setting. References Server/web PR: zulip/zulip#37931 Server/web issue: zulip/zulip#37096
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 zulip/zulip-flutter, 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 zulip/zulip-flutter acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 43.8% were successfully merged into the primary branch.
zulip/zulip-flutter has a recorded first-timer success rate of 25.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 51.9 places zulip/zulip-flutter in the Solid tier.
The external pull request merge rate is 43.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zulip/zulip-flutter currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for zulip/zulip-flutter 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.