Uploaded July 2019 | Updated November 2026, 3 hours ago
📗 Learn from the written tutorial & get the project files 👇👇
resocoder.com/flutter-moor-ep2
👨💻 Do you write good code? Find out now 👇
resocoder.com/good-code-quiz
Moor is a powerful library for using an SQLite database from your Flutter apps by writing pure Dart code. In the first part of this series, we've only touched the basics of this package. Let's now take a look at some of the more advanced queries and also how to keep your code clean by separating it into Data Access Objects.
All of the code for queries currently lives inside the AppDatabase class itself. At the moment, that's perfectly fine - we are only dealing with Tasks. We have to think into the future though. Once we would start adding comments, habits and who knows what else into the app, placing all of the queries together would create a mess.
To separate the queries dealing with tasks (and in the future, with comments and habits), we can use data access objects (DAOs). The functionality of the queries will remain unchanged, they will only be moved to a new and cleaner place.
Go to the website for more information, code examples, and articles:
● resocoder.com
Follow me on social media:
● instagram.com/resocoder
● facebook.com/resocoder
● twitter.com/resocoder
● gab.ai/resocoder
📗 Learn from the written tutorial & get the project files 👇👇
resocoder.com/flutter-moor-ep2
👨💻 Do you write good code? Find out now 👇
resocoder.com/good-code-quiz
Moor is a powerful library for using an SQLite database from your Flutter apps by writing pure Dart code. In the first part of this series, we've only touched the basics of this package. Let's now take a look at some of the more advanced queries and also how to keep your code clean by separating it into Data Access Objects.
All of the code for queries currently lives inside the AppDatabase class itself. At the moment, that's perfectly fine - we are only dealing with Tasks. We have to think into the future though. Once we would start adding comments, habits and who knows what else into the app, placing all of the queries together would create a mess.
To separate the queries dealing with tasks (and in the future, with comments and habits), we can use data access objects (DAOs). The functionality of the queries will remain unchanged, they will only be moved to a new and cleaner place.
Go to the website for more information, code examples, and articles:
● resocoder.com
Follow me on social media:
● instagram.com/resocoder
● facebook.com/resocoder
● twitter.com/resocoder
● gab.ai/resocoder
![Flutter Firebase & DDD Course [8] - Sign-In Form UI
📗 Get the code 👇👇
https://github.com/ResoCoder/flutter-ddd-firebase-course
📧 Get Flutter news 📰 and resources:
👉 http://flutter.education
👨💻 Do you write good code? Find out now!
https://resocoder.com/good-code-quiz
Its finally time to create the user interface which will allow our users to sign in. This will come with everything necessary, including displaying the validation error messages coming from the value objects.
Go to my website for more information, code examples, and articles:
● https://resocoder.com
Follow me on social media:
● https://instagram.com/resocoder
● https://www.facebook.com/resocoder
● https://twitter.com/resocoder Flutter Firebase & DDD Course [8] - Sign-In Form UI](https://i.ytimg.com/vi/KfuUkq2cLZU/mqdefault.jpg)
![Flutter TDD Clean Architecture Course [1] – Explanation & Project Structure
📗 Learn from the written tutorial 👇👇
https://resocoder.com/flutter-tdd-clean-architecture-ep1
👨💻 Do you write good code? Find out now!
https://resocoder.com/good-code-quiz
Keeping your code clean and tested are the two most important development practices. In Flutter, this is even more true than with other frameworks. On one hand, its nice to hack a quick app together, on the other hand, larger projects start falling apart when you mix the business logic everywhere. Even state management patterns like BLoC are not sufficient in themselves to allow for easily extendable codebase.
This is where we can employ clean architecture and test driven development. As proposed by our friendly Uncle Bob, we should all strive to separate code into independent layers and depend on abstractions instead of concrete implementations.
Go to my website for more information, code examples, and articles:
● https://resocoder.com
Follow me on social media:
● https://instagram.com/resocoder
● https://www.facebook.com/resocoder
● https://twitter.com/resocoder Flutter TDD Clean Architecture Course [1] – Explanation & Project Structure](https://i.ytimg.com/vi/KjE2IDphA_U/mqdefault.jpg)


![Flutter Firebase & DDD Course [16] - Watching Notes on Firestore
📗 Get the code 👇👇
https://github.com/ResoCoder/flutter-ddd-firebase-course
📧 Get Flutter news 📰 and resources:
👉 http://flutter.education
👨💻 Do you write good code? Find out now!
https://resocoder.com/good-code-quiz
The application layer responsible for continuously loading notes from the repository (in other words - watching the notes) is implemented. Now its time to get into the details on how to watch the notes using Firestores real-time capabilities.
Go to my website for more information, code examples, and articles:
● https://resocoder.com
Follow me on social media:
● https://instagram.com/resocoder
● https://www.facebook.com/resocoder
● https://twitter.com/resocoder Flutter Firebase & DDD Course [16] - Watching Notes on Firestore](https://i.ytimg.com/vi/LGSC7TiAcSY/mqdefault.jpg)





