The intent of designing in terms of clean architecture is to support scale up.

Today everything is saving in shared preferences, Tomorrow if I would like to save it in local db.

The code which I am going to write will not pollute existing code, I would create a new adapter and change just DI configuration.

The next day the requirement arrives to save it in an external api.

Again The code which I am going to write will not pollute existing code, I would create a new adapter and change just DI configuration.

Dependency Injection is key to clean architecture.

It might not require ,if you just want an UI load it in memory and display it and app does not require any more changes.

That's why the title is clean architecture experiment, not another app developed in flutter :)