Up to now b69ced23d1532431cd960efb5ea63a24e26c0a69, the lib/ structure looks like:

lib/
├── app/
│   ├── backend/
│   │   ├── database/
│   │   ├── entity/
│   │   │   └── entities.dart
│   │   ├── handler/
│   │   │   └── handlers.dart
│   │   └── repository/
│   │       └── repositories.dart
│   ├── bloc/
│   │   ├── blocs.dart
│   │   └── challenge/
│   │       └── bloc.dart
│   ├── model/
│   │   └── models.dart
│   ├── util/
│   │   └── utils.dart
│   └── view/
│       ├── challenge/
│       │   ├── component/
│       │   │   └── components.dart
│       │   └── page/
│       │       └── pages.dart
│       └── widget/
│           └── widgets.dart
├── device_service
│   └── device_services.dart
└── main.dart

Anyone has a better idea on it?

• I have some basic requirements:

  • Easy to maintain (Scalable)
  • Easy to understand (Intuitive)
  • Improve code readability and Resonate with the dart code

• From my experience, the dart module system, at least in the keywords design, is more like the ES6 (e.g. export...), and a little similar usages about python module(e.g. as,show...) and some dart other usages (e.g.hide...), so what kind of inspiration can we get from these features? 😕

Willing to listen to yours opinion ! 😉

Sometimes, making the to-do items may not be able to complete the task as expected (In fact, I usually meet this situation), we need a mechanism that can easily inherit the outdated items, whether in UI / UX or data structure design.
Waiting for the result of careful thinking:thinking: