For sure you can create a basic view with a ModelSerializer by hiding all the complexity, but very often it won't be enough to build what you want to build, and therefore you will have to search trough the documentation how things works.
In my opinion both Flask and Django are good for learning purposes, but Flask requires the user to handle more complexity than Django, which is not always the best thing if you want to learn
By using Flask first, you also end up thinking "wow, every time I build a flask app I go through these same repetitive steps. Would be nice if they were automated". Then you find they are automated in Django.
If you learn the solution first, it seems irritating and sometimes you never understand the problem that it's solving.
If you don't know what magic Django is doing for you, it feels restrictive to do stuff the Django way.
Mostly because the structure can be absolutely any shape, the last one I went onto used the Django structure, but it may as well have just been Django.
TL;DR - Flask for education and simple projects. Django for creating CRUD apps where you just need it to work.
Shameless plug -- I wrote this comparison[0] which shows how "Hello, World" is written in Flask and Django, and goes over some pros and cons of each in more detail. The editors added the "Why Flask might be better" part to the title, which caused most of the discussion about the post to turn into a flame war, but I tried to be as objective as possible (although I do prefer Flask -- another shameless plug for my book[1] Flask by Example).
[0] https://www.codementor.io/garethdwyer/flask-vs-django-why-fl...
[1] https://www.packtpub.com/web-development/flask-example