build VS packages

The official documentation is here. It's not very beginner friendly. Therefore, it might be easier to look at the examples.

In the first part of this series of posts, we discussed how Flutter and -Dart in general- makes use of builders to generate source code during the build process.

build: "Defines the basic pieces of how a build happens and how they interact."

build_runner

Having spent about 6 months each with SwiftUI and Flutter I vastly prefer working with Flutter. Swift is a far more ambitious language but really doesn't live up to it's own marketing. Many of the features are half down (generics and protocols are both full of holes). Dart on the other hand doesn't have half as many nice features but the one's that are there are rock solid. Reified generics in particular is far nicer to work with (Swift's compiler gets regularly gets lost on type resolution and then doesn't give you any way to give it hints). Dart also seems to be heading in the right direction. It's added null safety and the upcoming metaprogramming features should fill in many of the gaps that are currently filled by the very practical but clunky https://pub.dev/packages/build.

I am one of the authors of the build package (https://github.com/dart-lang/build) which does effectively expose a plugin system. We take the approach of creating a wrapper script that actually just generates the real program (adds imports to the plugins, registers them, etc) and then it just runs that program. There are several downsides to this approach though (primarily, slow startup).

There's a similar project from Google: https://github.com/flutter/packages/tree/main/packages/rfw

rfw is used by Google's Gemini LLM to generate UI.

rfw runs on the web/android/ios/macos/linux/windows, anywhere where Flutter runs.

I am trying out google_maps_flutter's example on iOS, and I couldn't figure why when I drag the map, the map pans to a different location when I release. Does it happen to anyone?

For the minimal app, you can simply try example of image picker here.

see: https://github.com/flutter/packages/pull/2650

(TL;DR: Flutter Apps come with this set of rules by default: https://github.com/flutter/packages/blob/main/packages/flutter_lints/lib/flutter.yaml)

But be aware that go_router does not preserve the navigation state within the shell routes yet. It is being worked on though ( https://github.com/flutter/packages/pull/2650 )

In this article, we have discussed how to use go_router in your Flutter app as well as some of its features, like route parameters, query parameters, named routes, handling errors, and redirection. This is just a beginner's guide for getting started with go_router. If you want to learn more, visit the official go_router API documentation.

you should use path parameters so that it supports web https://github.com/flutter/packages/blob/main/packages/go_router/example/lib/path_and_query_parameters.dart