What we usually do (even in huge projects) is we just start by defining the UI.
Once you have the UI you can break it into tasks.
But I'd say that if you're doing a personal project just go screen by screen till you're done. Also, make it work first, don't get too fancy. You can always make it better later.
I learned as a beginner that when I tried very very hard to come up with a good design that I'd end up throwing it away anyway. So don't try. Just make a minimal thing work and then refactor it into shape later.
Nothing better than watching something work rather than a bunch of code that does nothing yet because you still have to implement 20 classes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What we usually do (even in huge projects) is we just start by defining the UI.
Once you have the UI you can break it into tasks.
But I'd say that if you're doing a personal project just go screen by screen till you're done. Also, make it work first, don't get too fancy. You can always make it better later.
I learned as a beginner that when I tried very very hard to come up with a good design that I'd end up throwing it away anyway. So don't try. Just make a minimal thing work and then refactor it into shape later.
Nothing better than watching something work rather than a bunch of code that does nothing yet because you still have to implement 20 classes.