Why does a Flutter web app generally need particular additional attention paid to properly supporting browser navigation, such as the browser's own back and forward buttons working correctly as a typical web user would already genuinely expect?

Since Flutter was originally designed first and foremost for mobile, where the concept of a shared browser address bar and separate back and forward buttons simply does not exist at all, a Flutter web app needs to be properly and deliberately configured using Navigator 2.0 or a dedicated routing package like go_router to correctly and reliably update the actual browser's own URL as a user navigates between different screens within the app, ensuring the browser's own native back and forward buttons work correctly exactly as any typical web user would already fully expect them to from any other regular website they have ever visited.

final router = GoRouter(
  routes: [
    GoRoute(path: '/', builder: (context, state) => HomeScreen()),
    GoRoute(path: '/products/:id', builder: (context, state) => ProductScreen()),
  ],
);