He is really passionate about programming and does believe that good software would one day make the world a better place to live. All the Apple hardware, the Human Interface Guidelines, and the Web 2.0 standards make him do his best.
Deployment and Iterating for Web vs. Mobile Apps
With a web application, deployment is entirely within your domain. Trying new things and iterating quickly are easy to do and processes like partial roll outs, A/B testing, and continuous deployment are well documented and battle tested. Users are not shocked if some part of a web application morphs subtly from time to time. For example, I’m willing to bet most people have been in Google Search experimental group at least once.
Contrast this to mobile application development. Application updates are explicit and user initiated. Review times are long. Partial roll outs, A/B testing, and continuous deployment are impossible or difficult (especially on iOS). Users do not have experience with half baked features popping up and being suddenly removed — they see the application as lacking polish and react negatively.
There is simply no room for half baked features in mobile application development. You need to think carefully about what segments of the feature are released in what order, and you must make sure what you do release is fully baked.
(Source: iamthewalr.us)