Ranter
Join devRant
Do all the things like
				++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
				Sign Up
			Pipeless API
				From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
				Learn More
			Comments
		- 
				
				
py2js27248yThinking ahead you can go either way. Both works like a charm. But if he is comfortable is django then he should use that only - 
				
				
donnico12118yYou can hack your way in django as fast as in flask IMHO.
I would go with flask only when the resources are a concern (IOT) - 
				
				@donnico resources aren't an issue here. Just which has a better turnaround time for prototyping products.
 - 
				
				
donnico12118y@ibrahmin13 if there is 10% chance that the prototype is going to grow in a project go with django 
Related Rants
- 
						
							
rhapsody914
When your company launches a new mobile, hands it to you for free and also lets you engrave on it. - 
						
							
practiseSafeHex9So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles ... - 
						
							
nblackburn6When you show people a working prototype of what they asked for and they immediately start point out flaws. I... 

Off late I've been having a lot of debate with my friend about using Flask over Django for prototyping some feature. I side with Flask, since the development time is much lesser than Django and doesn't need to follow a lot of rules.
Issue here is, I prefer flask and he prefers Django.
Need opinion on this sort of problem, where a prototype for a feature in a product has to be built. It maybe integrated into the end product, which is in Django, or may not be.
question
django python
django
product
prototype
flask