Learn

Release Desktop And Web

Desktop and web releases are different products, not just extra build commands.

Web

flutter build web --release

Then serve build/web through a static server and test browser behavior. Do not rely on flutter run -d chrome as release evidence.

Check:

  • Renderer/build flags.
  • Base href and hosting path.
  • Browser support matrix.
  • Accessibility semantics.
  • Bundle size and load performance.
  • SEO/content constraints.

Windows

flutter build windows --release

For Microsoft Store release, validate package identity, MSIX/AppX packaging, icons, Partner Center setup, version constraints, and package validation.

macOS

flutter build macos --release

For App Store release, treat this like Apple release work: Bundle ID, signing, archive, TestFlight/App Store Connect, icons, and review.

Linux

flutter build linux --release

Official Flutter deployment docs emphasize Snap Store packaging through snapcraft/LXD. If you choose Flatpak, AppImage, direct .deb, or another route, document that as a project-specific release decision.

Gotcha: A desktop build folder is not a distribution plan. Users need signed, packaged, installable, updateable artifacts.