DEMO的页面push生硬
建议使用默认的 Navigator.pushName
这么生硬的DEMO很影响Flutter在开发者技术选型时的判断

It would be great to see, how to properly implement refreshing + pagination + search.

Web socket as data Provider

todos_repository_simple explains nicely about the benefits of using repository as singleton. But no where it's mentioned how to handle the web sockets.

How can I use web socket (webSocket and fileStorage) instead of rest (webClient and fileStorage) ?

Some key points between web socket and rest.

• The name itself signify socket

This step: https://firebase.flutter.dev/docs/messaging/usage/#web-tokens under 2. describes that firebase-messaging-sw.js should be created and included into index.html.
The example has nothing like that: https://github.com/FirebaseExtended/flutterfire/blob/master/packages/firebase_messaging/firebase_messaging/example/web/index.html

Is it not required anymore with the latest automatic init

What could be improved

Based on this issue: flame-engine/flame#954, I noticed that we could also go for the same approach for the packages' unit/widget tests execution,