Get started with Flock, without losing your baseline

Start with a record of the SDK that already builds your app. Then evaluate Flock in a separate project checkout with an explicit repository and revision.

Record the baseline → Isolate the candidate → Repeat target checks → Keep or roll back.

Flock is a community fork of Flutter. Nest contains tooling for maintaining that fork. A working Flutter app does not need a fork simply because one exists: the useful reason to evaluate one is a specific change you can test.

1. Record the working environment

   In the project that currently builds, capture the Flutter version and doctor output. Note your target, operating system and package lockfile. Keep this baseline before changing the SDK.

2. Choose the repository deliberately

   The Flock project now links to join-the-flock/flock. Its 2024 documentation used a different GitHub organisation. Read the current repository and the FVM fork documentation before selecting a ref.

3. Isolate the trial

   Use a separate checkout and a project-specific SDK selection. Do not delete a shared SDK cache just to follow an old article. Save the previous configuration and record how you will select it again.

4. Prove the change

   Reproduce the same case with the baseline and candidate. Record analysis, tests and the actual target build separately. A successful version command proves which SDK ran; it does not prove that your app works.

5. Keep or roll back

   Keep the candidate only when the intended change passes and the checks you selected for your app also pass. Retain both environment records and a repeatable way to select the previous SDK.

flutter --version
flutter doctor -v

# In the trial checkout, with the intended SDK selected:
flutter analyze
flutter test
# Build the platform your app actually ships, for example:
flutter build web

A configuration you can inspect

This is the project-specific repository pattern in the Flock documentation. master is a moving reference, not a frozen release. Confirm that the ref exists in the selected repository and check the installed revision after using your installed FVM version.

{
  "flutter": "master",
  "flutterUrl": "https://github.com/join-the-flock/flock.git"
}

Use the configuration inspector to spot missing values and moving refs. It reads text locally; it does not install FVM, contact GitHub or resolve a revision. For a complete trial record, follow the SDK evaluation worksheet.

Reading the original instructions

The source snapshot below preserves the earlier setup guide. Its 2024 version output and cache-removal advice describe that period. They are not a current compatibility statement.

{
  "flutter": "master",
  "flutterUrl": "https://github.com/join-the-flock/flock.git"
}

Flutter SDK: Channel: Master is not installed.
? Would you like to install it now? (y/n) › yes

Flutter 3.27.0-1.0.pre.200 • channel master • https://github.com/join-the-flock/flock.git
Framework • revision 452ef96537 (16 hours ago) • 2024-10-22 12:37:14 +0000
Engine • revision e6856502b5
Tools • Dart 3.7.0 (build 3.7.0-47.0.dev) • DevTools 2.40.1

fvm flutter --version

fvm flutter pub get

fvm flutter run

fvm flutter build

etc.