> How did you check that assumption? This is a guesstimate. Most well-to-do individuals will not stick to old phones that do not match their outward looking st

> How did you check that assumption? This is a guesstimate. Most well-to-do individuals will not stick to old phones that do not match their outward looking status. > Does the stack to be used represent the innovation itself? No. But the stack should help easily build web app that look and feel like mobile app. The users of the app will be on-the-move individuals. They may not like visiting a website everytime they want some information. But building a mobile app(iOS and/or Android) is not affordable at this juncture. > Are you doing this in order to learn a new stack (i.e: a fun project where the objective is learning about single page application stacks)? If not, I'd disregard that and go with the stack I'm most productive with to solve the actual problem at hand and deliver value. No, it is not to learn new stack. The original question I posed stems from the requirement that the web app should be as easy to use as mobile app, and should not put off the users from using the app regularly and also should not drain their device battery.