Library / SDK
zino-hofmann/graphql-flutter avatar
zino-hofmann/graphql-flutter

graphql-flutter: a Dart GraphQL client built on Streams, with caching, polling and one feature marked out of service

A GraphQL client for Flutter, bringing all the features from a modern GraphQL client to one easy to use package.

3,267 stars639 forksDartMIT

At a glance

What is it?
zino-hofmann/graphql-flutter is a Dart monorepo holding a pure Dart GraphQL client and a Flutter widget layer on top of it. This article covers how the two packages divide the work, what the cache and links do, and where the project tells you something does not work.
Who is it for?
Choose graphql-flutter when you want a GraphQL client for Dart or Flutter that handles caching, polling, subscriptions and uploads in one place, and when you can live without built-in code generation. Avoid relying on Automatic Persisted Queries, which the project itself marks out of service, and plan to add a separate codegen tool if you want typed results.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 57 days ago.
What is it written in?
Mainly Dart, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • zino-hofmann/graphql-flutter3,267 ★ · -2
Star history
Repository2026-09-242026-11-15
zino-hofmann/graphql-flutter3.3k3.3k

-2 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two packages in one repository: a Dart client and a Flutter wrapper

The repository is a monorepo with two packages. The package named graphql is a client implementation that talks to any GraphQL server, and graphql_flutter is a set of Flutter widgets wrapped around the graphql API. The split has a practical consequence. If you write a command line tool, a server or any Dart code without a Flutter dependency, the graphql package is the one that applies. The widget package is only for code that runs inside a Flutter app.

The project describes itself as a collection of packages to work with a GraphQL server in Dart and Flutter. Its license is MIT and the primary language is Dart. The README says the engineers at Zino App BV originally created and published the package, and that the community has since contributed. Detailed documentation for each feature lives in the per-package READMEs, so the root README works as a map rather than a manual.

Streams are the core idea, with Apollo as the stated inspiration

The introduction claims the project combines the benefits of GraphQL with the benefits of Streams in Dart to deliver a high-performance client. It also names the Apollo GraphQL client as the source of inspiration. In GraphQL terms the benefit for the client is fewer requests and therefore less data usage, and for the programmer the shape of a request mirrors the shape of the response, which makes requests easier to reason about.

Streams show up in the feature list as query polling and rebroadcasting, documented under client.watchQuery and ObservableQuery in the graphql package README. A watched query is an observable that emits new results over time, so your UI listens to it instead of calling once and forgetting. The consequence is that you need to be comfortable with Dart streams and with disposing of subscriptions, since a long-lived observable that nobody closes keeps polling for as long as it lives.

Caching is in memory or persistent, and the cache can be edited directly

The feature list names in-memory and persistent caching, with the persistence section in the graphql README. It also lists client-state management through a direct cache access API. Together these mean the cache is not a black box: you can read and write entries yourself, which is how local state ends up living in the same store as server data.

Optimistic results are a related feature, and the link points at the graphql_flutter README under optimism. That placement tells you something. Showing an expected result before the server answers is documented in the Flutter widget package, so a pure Dart user should check what the graphql package alone exposes before relying on it. The listing also includes GraphQL Upload and operation cancellation, each with its own section in the graphql package README, so file uploads and cancelling in-flight requests are handled by the client rather than by extra code of your own.

Automatic Persisted Queries are marked out of service

One row in the feature list carries a warning sign instead of a tick: Automatic Persisted Queries, labelled out of service. The link goes to a section named persistedquerieslink, which carries an experimental warning and an out-of-service warning in its anchor.

The consequence is simple. If your server and your bandwidth plan depend on sending query hashes instead of full query text, this client cannot be counted on to do that for you today. A team that adopted the feature from an older example should check the persisted queries section before upgrading. It is also a useful signal about the rest of the list: the maintainers mark broken features openly instead of leaving a tick on them, which makes the ticked rows more credible than a list where everything is green.

Links make the client modular, and the codegen is somewhere else

The modularity entry points to a section on links. A link is the piece that sits between your operation and the network, so transport, authentication and error handling can be swapped or stacked without rewriting the client. That is the mechanism that lets one client talk to any GraphQL server.

What the package does not do is generate typed Dart classes from your schema. The README sends you to companion tools instead: graphql_flutter_bloc, graphql_codegen and graphql-cache-inspector. A community article in the same README describes using graphql_flutter with artemis for code generation and graphql-faker for API prototyping. The consequence for your project is a second dependency and a second build step if you want typed results. Without one, you handle results as maps and own the casts. The cache inspector is a separate pub.dev package for looking inside the cache while you debug.

Release tags follow two schemes, and the last release was in March 2026

The recent releases show two naming patterns. The v-packages-v5.3.0 release was published on 14 March 2026, graphql-v5.2.3 on 21 October 2025, and v5.2.2 on 7 September 2025. The package-prefixed tag suggests releases are cut per package, while the others use a plain version, so when you read a changelog, check which package a tag belongs to before assuming it applies to the one you installed.

The last push to the repository was on 19 September 2026, and the project is not archived. That is a push, not a release, so the newest published version is still 5.3.0 in the list above. A changelog-v3-v4.md file in the root records the older major version changes, a useful reference if you are migrating an old app.

Contributing runs through melos 2.9.0 and a Makefile

The Makefile defines how the monorepo is built and tested. The dep target activates melos at a fixed version and a changelog tool, then runs melos bootstrap. The two commands in the Makefile that matter to a new contributor are:

code
dart pub global activate melos 2.9.0;

and the full CI target, which is `make ci`, chaining dep, check_client and check_flutter. Other targets run format, analyze, test and coverage for the client and the Flutter package separately, and changelog targets run inside packages/graphql and packages/graphql_flutter.

Two practical points follow. The Makefile pins melos to 2.9.0 explicitly, so if bootstrap fails on your machine, that pin is the first thing to compare against your installed tools. And because the repository also contains an example directory, an examples directory and a flake.nix, you have more than one place to see the client in use before you write your own code.

Editorial conclusion

Choose graphql-flutter when you want a GraphQL client for Dart or Flutter that handles caching, polling, subscriptions and uploads in one place, and when you can live without built-in code generation. Avoid relying on Automatic Persisted Queries, which the project itself marks out of service, and plan to add a separate codegen tool if you want typed results.

Frequently asked questions

Why use GraphQL instead of REST with graphql-flutter?

The project says GraphQL means fewer requests and less data usage on devices, and that requests have the same structure as the response. graphql-flutter adds Streams, caching and polling on top of that idea.

What is GraphQL and why use it in a Flutter app?

GraphQL is a query approach where the request shape matches the response shape. graphql-flutter is a Dart client for it, with queries, mutations, subscriptions, caching and uploads, plus Flutter widgets.

What is the downside of GraphQL when using graphql-flutter?

The clearest gap in this client is that Automatic Persisted Queries are marked out of service. Typed code generation is also not built in, so you add a tool such as graphql_codegen.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. zino-hofmann/graphql-flutter on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zino-hofmann-graphql-flutter.svg)](https://hysenlabs.com/projects/zino-hofmann-graphql-flutter)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/zino-hofmann-graphql-flutter.svg)](https://hysenlabs.com/projects/zino-hofmann-graphql-flutter)

Was this useful?