> Like water flowing downhill, users gravitate to the best experiences This is quite the loaded statement & a self-fulfilling prophecy in practice. It's quite

> Like water flowing downhill, users gravitate to the best experiences This is quite the loaded statement & a self-fulfilling prophecy in practice. It's quite common to see a full page prompt to download the App in big letters, and tiny text to continue onto the mobile site. Of course it's a better experience to use the app. The first experience of the mobile website is an intrusive advertisement saying "use the app". Given an apples to apples comparison, I find that mobile apps often don't have all of the features of the website. Youtube comments is a good example. You simply cannot edit comments on the mobile app. Native Mobile apps also fragment development effort. This leads to a worse overall platform experience, since the development is fragmented to n platforms (don't forget about Windows & Firefox phones). When new features need to be added, they need to be developed on all platforms. The more complex the feature-set & UX, the worse this issue becomes. This fragmentation is mitigated by using a tool like PhoneGap. However, you still have added complexity via versioning. It's overcome-able. My current project has a rich mobile web experience. We also use phonegap, so all development is in sync. The featureset is complex & rapidly evolves. There are many edge cases. It would not be a practical business with n codebases.