FlutterCook / about

A cookbook for open-source Flutter.

FlutterCook indexes the open-source Flutter and Dart ecosystem — libraries, UI components, state management, animation, backend, and AI — and pairs that index with hand-written articles and free browser tools for app developers.

Who writes this

FlutterCook is run by Trung Hieu, a mobile developer working with Flutter, iOS and Android. It is a personal project, not a company: there is no editorial team behind the byline, and no one pays to appear on it. The same notes are published in Vietnamese on trunghieu-it.blogspot.com.

Corrections, licensing questions and privacy requests all go to the same place — see contact. Paid guest posts and link exchanges are declined.

What is written, what is compiled

Being straight about this matters, because the two kinds of page are not the same thing:

  • Written by hand — the 350 blog posts, the 19 news digests, the guides, the Screenshot Studio tool, and these standing pages. This is the part of the site worth your time.
  • Compiled from public metadata — the 510 recipe pages. Each one is assembled from the GitHub API (stars, forks, last commit, topics, the repository's own description) and pub.dev, laid into a shared template. They are a searchable directory of the ecosystem, not original writing.

Because the recipe pages are compiled rather than written, they carry noindex and they carry no advertising. They exist so you can find a package and get to its real documentation quickly, and they link straight out to the source repository on every entry. Star counts and commit dates are snapshots from the last build, so treat them as approximate — the trends page pulls live numbers instead.

Built in the open

Source and demos live at github.com/fluttercook. The site is built with Astro, is fully static, and is deployed to GitHub Pages. There is no account system and no server of our own — what that means for your data is set out in the privacy policy.

How the ecosystem is ranked

Repositories are ranked by stars weighted for recent activity, then adjusted by hand: long-standing "must-know" packages are kept even when their star growth has flattened, and abandoned projects drop off regardless of historical popularity. Nothing in the ranking is sponsored.