Here is a rapid pros/cons on flask-api for the moment:
Pros:
ease of use for default use cases
-> Switch Flask's app with FlaskApi's app and on we go. This does not deal with edge cases though (see the following points)
default renderers are enough for our use case
extending renderers and parsers is simple (added YAMLRenderer example from doc rDWUI612c7a23)
default rendering policy is good! Just need to set decorators for deviant other use cases
-> We've got mainly apis for the moment and less html endpoints... but this may change in the future...
-> An issue is opened about automagically detect when html is needed but no implem just yet (https://github.com/tomchristie/flask-api/issues/13)
exception handling not symmetrical with default use case (That is it does not obey the client's 'Accept' header for errors...)
-> dev was needed and done here - rDWUIb5fba341 (effort were made to keep the flask errorhandler decorator which is nice)
our @jsonp decorator stopped working, some dev was needed to make it back online again -> rDWUI6063c7e1 (the result is quite pleasing since we removed more code than adding it though)
low maintenance at the moment (the main contributor stepped down and is focused on Django rest https://github.com/tomchristie/flask-api/33)
-> quoting the readme: 'Status: Flask API is not currently under active development. This will be reassessed once the Django REST framework Kickstarter project reaches completion.'
no deb for packaging flask-api just yet... (i installed using sudo pip3 install ...)