Sidekick for Flutter: desktop version management

The Flutter version switching problem Sidekick addresses

Sidekick targets a specific part of Flutter development: managing the SDK versions available to a developer. Flutter projects can require different SDK releases, and finding the right binary is more involved than opening an arbitrary release page and manually replacing an existing installation. Sidekick puts that version-management task in a desktop interface that supports Linux, macOS, and Windows.

The README identifies version management, release exploration, and version search across apps as concrete features. It also lists version sandboxing under the name "playground." That wording suggests Sidekick is intended to let a developer try more than one SDK environment, although the README does not describe the sandbox boundary, persistence behavior, or project selection flow. Those details should be treated as unknown until confirmed in the application or installation wiki.

This is not a code editor, build pipeline, test runner, or general-purpose Flutter IDE. Its value is narrower: reducing the desktop work associated with locating and managing Flutter versions. It is best suited to developers who already use Flutter and recognize the difference between the Flutter SDK and the application being built.

Sidekick's repository layout and implementation boundary

The repository is written primarily in Dart and contains the conventional implementation areas of a Flutter desktop application. Directories named `lib/`, `test/`, `localizations/`, `assets/`, `linux/`, `macos/`, and `windows/` show that UI code, tests, translations, resources, and three desktop targets belong to the project. The `pubspec.yaml`, `pubspec.lock`, and `analysis_options.yaml` files indicate a standard Dart package structure, while platform packaging material appears in `AppImageBuilder.yml`, `snap/`, and `Sidekick.desktop`.

Based on that layout, Sidekick is not a thin shell around one documented shell script. It is a Flutter desktop codebase with its own presentation assets, platform runners, localization files, tests, and packaging configuration. However, the README does not expose the service layer, version-discovery logic, SDK installation behavior, or data flow between Flutter releases and the UI. It would therefore be speculative to claim that Sidekick downloads SDK archives itself, edits shell profiles, or uses a particular Flutter API.

The localization directory and README's language list also indicate that the interface has been prepared for multiple languages. The documented language list includes Arabic, Basque, German, English, Ukrainian, Spanish, Japanese, Swedish, Portuguese, Korean, Polish, and Italian. Exact menu names and whether every listed feature is fully translated are not documented.

Installing Sidekick and performing a first version check

The README does not provide package-manager commands, build flags, or system requirements. It points users to the GitHub releases page for the latest downloadable build and separately links to the Microsoft Store. It also links to an installation wiki. Because those pages are outside the README, an exact command-based tutorial cannot be reproduced without inventing steps.

A first supported route begins with opening the project's latest release page and selecting the build appropriate for the operating system. Windows users are also directed to the Sidekick listing in the Microsoft Store. Linux and macOS users are directed to the release page. The README does not identify package formats, minimum macOS or Windows versions, architecture support, or whether a downloaded artifact requires separate installation.

After opening Sidekick, the first useful check is to use its Flutter version-management area to review the releases it presents. The README explicitly says Sidekick can manage Flutter versions and explore releases, so that is a safe initial path. It does not document exact button labels, refresh behavior, download prompts, or success messages. Those interface details must be verified in the installed application. This first-use procedure is intentionally short because the project documentation does not support a more specific sequence.

Version search and playground trade-offs

Searching versions across apps addresses a real desktop usability problem: developers often know the SDK version they need but may not immediately know where its release is published. Sidekick reportedly brings that search into its interface. The README does not specify the search syntax, result fields, offline behavior, or whether searches cover stable, beta, and other release channels.

Version sandboxing, presented as a playground in the feature list, appears designed for trying an SDK without treating it as the sole global choice. That interpretation fits the word "sandboxing," but the README does not specify whether the playground copies an SDK, creates a separate directory, changes environment variables, or is discarded after use. The absence of those details matters. A version experiment is useful only if its isolation, retention, and cleanup behavior match the developer's expectations.

The practical limitation is therefore not a proven defect but a documentation boundary. Sidekick presents itself as a GUI for development-support tools, yet the README gives only a short feature list. It does not explain project-level integration, FVM configuration, CI behavior, channel selection, proxy requirements, or how conflicts between multiple installed SDK versions are resolved.

Sidekick compared with manual SDK selection

The clearest alternative described by the project documentation is manual Flutter SDK handling: locating a release through Flutter's own workflow and changing the SDK installation or local selection directly. That approach requires fewer desktop-management layers, but it leaves the developer responsible for tracking paths and selecting the correct SDK whenever an existing installation does not fit the task.

Sidekick changes the approach by placing release discovery and version management in one cross-platform graphical interface. The repository also includes `.fvm/` and `.fvmrc`, which places Flutter version selection within the project tooling context. The README does not explain whether Sidekick edits those files, reads them, integrates with FVM, or merely ships repository configuration, so Sidekick and FVM must not be described as interoperable based only on directory names.

For teams, command-line automation may also be the more appropriate alternative when Flutter selection must be reproducible in CI. Sidekick's documented scope is a desktop interface. It does not claim to provide CI configuration, build orchestration, or a server-side version manager.

Release history, maintenance signal, and BSD-3-Clause

The repository is not archived, and its last push was on 2026-10-14. Those are the only maintenance facts available, so they should not be expanded into a broader claim about release cadence. The documented release history is older: version 1.1.2 was released on 2023-06-28, version 1.1.1 on 2022-11-13, and version 1.1.0 on 2022-10-06.

This gap creates an adoption question. A recent push can include repository work without establishing that a new desktop release has been published. An engineer should therefore distinguish the state of the `main` branch from the version offered by the latest releases page. Compatibility with a particular Flutter SDK should be checked against the actual downloaded Sidekick build.

The repository uses the BSD-3-Clause license. That identifier permits use and modification under the license's conditions, but this review does not interpret those terms as legal advice. Organizations still need to review the actual `LICENSE.md`, preserve required notices where applicable, and account for the licenses of any separately distributed dependencies or packaged components.

Editorial conclusion

Sidekick is appropriate for Flutter developers who prefer a desktop interface for installing, locating, and trying SDK versions across Linux, macOS, or Windows. It is less suitable for developers who need documented project-wide version pinning, command-line automation, or evidence of frequent release activity. Before adopting it, verify that the current downloadable build works with the Flutter SDK and operating-system versions used by your team, and confirm how your CI and editor select Flutter versions.

Frequently asked questions

Official sources

1. Issues
2. leoafarias/sidekick on GitHub
3. License: BSD-3-Clause
4. README
5. Releases