Two problems with native applications: 1. The systems and hardware they run on are usually controlled by one company. 2. There's no View Source. Where would

Two problems with native applications: 1. The systems and hardware they run on are usually controlled by one company. 2. There's no View Source. Where would we be if 'native' applications had won over the '[worst is better][1]' approach of the web? What do you do if you lose your phone and the only way to get information is through an app that was installed on it? [Alex Martelli][2]: > Our culture’s default assumption is that everybody should always be striving for perfection – settling for anything less is seen as a regrettable compromise. This is wrong in most software development situations: focus instead on keeping the software simple, just “good enough”, launch it early, and iteratively improve, enhance, and re-factor it. This is how software success is achieved! Good enough is usually good enough and can be accomplished through a web browser if your design is good and not compromised by 'business decisions'. There is a place for native apps. Communication applications such as Whatsapp are a good example. Applications whose main purpose is to provide information, such as websites, are not. Finally, lets not forget that the internet is not a thing, [it's an agreement][3]. [1]: http://hypertexthero.com/logbook/2013/07/europython-2013-notes/#goodenough http://hypertexthero.com/logbook/2013/07/europython-2013-not... [2]: https://ep2013.europython.eu/conference/talks/good-enough-is-good-enough https://ep2013.europython.eu/conference/talks/good-enough-is... [3]: http://worldofends.com/ http://worldofends.com/