Likewise, if you are concerned about mobile usage, that has nothing to do with the stack - you can code responsive design and accessible markup on any stack.
C and C++ :)
I am evaluating using Wt, Bootstrap, jQuery and PostgreSQL. But that may not be the best option both to scale the app and the team going forward.
> Learning a new stack for a new app is a great learning experience, but not the most effective way to launch a product.
Initial pain may provide better dividends afterwards, that is my line of thought at this moment. But I may bite the bullet and just go with Wt as I am comfortable using it.
The requirement here is that the web app should look and feel like mobile app so that the user is not put off from using it regularly. Also, the web app should not drain the user's device battery. Not all stacks can handle that efficiently.