Let me take you on a beautiful journey. Flask: You start to ride a bike. Being a noob you mess up a lot of times. And, get hurt over and over. You learn things now. Django: You start to ride a bike. But, a plot twist. You learn riding a bike by observing others. You sit on their back and see how much smoothly they do ride. Now, either situations are possible: You copy them flawlessly and become a pro. You mess things up badly, end up injuring self and dumbstruck about how things are done. Now the choice lies with you. You know your caliber better than anyone. Coming to the point, Flask and Django are both awesome in their own aspects. Flask can help you learn and get the feel of how things are carried out in backend development and how frontend can be improved exponentially with a correct backend setup. And the learning curve is much gentle as compared to Django. But the problem lies in doing much on your own messes things up at large scale, hence slows down the product
Me, Mine and Myself