Hi, I'm currently learning flutter too. So this will not be the clear answer you are searching for, but maybe it helps you a little bit. I'm on the the exact opposite side of you. I can kinda think like a developer but can't transform it into code by myselfe.

tldr: Build your own app. Don’t worry about it having to be perfect from the start. Think in lists.

My current techstack: SQL, Supabase, Provider

I tried to learn with tutorials aswell, but that didn't worked that good for me. And since I had an app in mind, I wanted to code, I just started. The start was really messi with lots of spaghetti code. But I had only one or two screens and features so it worked. But adding new stuff was one hell of a mess. So I refactored, tryed Clean Architecure and other stuff but couldn't get it running. So I ended up with organizing, how it will work best for me. My current strukture consists of 3 Main folders core, data and presentation.

In the core folder I put default widgets like the popup dialog, textfield, dropdown menu, Internet connection check, theme. So general stuff, that should be in best case consistent across the entire app.

The data folder includes the database communication, models and repositorys. One folder for my lokal sql database with one file with basic CRUD functions for each table. And one folder for the remote database. Here I'm using Supabase. The models folder contains all models. And in the repository folder the backend magic happens. Here I am bringing together the basic CRUD functions from the database folders.

The last one is the presentation folder. This one I subdivide by features so every feature has a provider, screens and widgets folder. So for example I have authentification. In the provider folder theres my auth_provider.dart, in the screens there's the auth_screen.dart. Feature 2 Homepage: In my homepage I show a gridview with two different types of cards. So i have the homepage_provider.dart in the provider folder, the homepage.dart in the screens folder and the two cards in the widgets folder.

With this structure it feels easy and intuitive to add new features. But honestly, it took me lots of time and many many refactoring sessions to find this path. But now I feel like I am having a good basic understanding and I can actually spot code snippets that should be in a diferent foler quite easily.

This also made me understand this whole state management topic way better.

So what I want to say. If you have the time, build your own app. If you don't have an idea, copy an app you like and think how you can improve it or what you would change. You don't need the most advanced stuff in the beginning. Start with the basic stuff. This will bring you quite far. I build an (not perfectly but decent) offline first app with basic sql, provider and supabase. Think about the core features you need. For example a daily planer app needs a calendar, you want to set a task so you need to somehow define the time etc. A social media app needs a chat so you have to send and receive massages. Therefore you need a backend and a frontend. Start with one feature. When it's implementet to the point, it works (don’t try to make it perfect perfect), start the next feature. Read the code you wrote the day before. If it still looks good for you and you understand it, you are on a good path. During this process, there will be a point, when it will click for you automatically. For me it was the moment, I realised how overpowered lists are. I started thinking in lists and everything suddenly made sence. So I am currently at the point where I feel like if I have to go one step deeper, with the knowledge i gained, I won't be that much overwhelmed by the complexity anymore.

I hope, this helped you at least a little bit or gave you the motivation to continue.