Confusing package recommendation: flutter_command in addition to package:provider

[chriskeeble]

Page URL

https://docs.flutter.dev/app-architecture/case-study/ui-layer/

Page source

https://github.com/flutter/website/tree/main/src/content/app-architecture/case-study/ui-layer.md

Describe the problem

In the Architecture Case Study you suggest package:provider - and then shortly after in the next section you recommend using flutter_command - is this not unnecessary if using provider ? If so, a little more clarity would be useful to the likely audience of these pages.

Expected fix

Make it clear (if) flutter_command is not necessary in addition to using package:provider.

Additional context

No response

I would like to fix this problem.

• [ ] I will try and fix this problem on docs.flutter.dev.