A community01 / Evaluate
A fork with a reason.
Keep the working baseline and make an SDK trial you can reverse.
Plan your trial →Flock + Nest / Official home
Flutter.
Meet your
flock.
A community fork. A clearer path through the hard parts. Flock and Nest are back at their official home: flutterfoundation.dev.
Built on open source. Choose deliberately. Test what matters.
Find a reason
Start with a reproducible blocker. A fork is useful when you can name the change you need.
A better next step.
From a specific blocker to evidence you can share.
02 / Understand
Know the layer.
Separate framework source, native engine artifacts and tooling.
Read the layer map →03 / Contribute
Bring the evidence.
A reproducible issue is the start of a useful conversation.
Prepare a report →The flight desk
Less guesswork.
More useful context.
Inspect a configuration or assemble a report. Both tools run locally, with no account and no project-text upload.
Open the developer tools →FVM / CONFIGURATION
{
"flutter": "master",
"flutterUrl":
"https://github.com/join-the-flock/flock.git"
}A moving ref needs an exact installed revision.
Inspect your config ↗The ideas behind Flock.
Original articles. Real dates. Room for the details.
2024-10-27 / Matt Carroll
We're forking Flutter. This is why.
The Flutter team has a labor shortage. We're forking Flutter so that the community can accelerate Flutter's development.
2024-10-31 / Matt Carroll
The Three Stages of Flock
These are the three major phases of Flock development.
2024-10-29 / Matt Carroll
Introducing Flock and Nest at Flutter Silicon Valley
I announced Flock and Nest at Flutter Silicon Valley on October 24th, 2024.
Build your evidence, one step at a time.
New field guides for selecting an SDK, reading failures and maintaining a fork.
- Which Flutter SDK is actually running?
Trace a terminal, IDE and FVM invocation to the SDK used in a Flutter or Flock investigation.
- Reduce a Flutter failure without losing the trigger
A controlled method for turning a large application failure into a small shareable reproduction.
- Read Nest’s assembly and publication workflows
Follow the checked Nest source from trigger through assembly to remote publication, without confusing configuration with a successful run.
- Trace a Nest engine artifact to its build inputs
Read the engine workflow’s target matrix, revision identifiers and artifact destinations before trusting a binary.
Flock extends Flutter through community work. Nest provides tools for maintaining forks. This site brings together the project’s original writing and practical guides for making a grounded development decision.