- From: Appelquist Daniel (UK) <Daniel.Appelquist@telefonica.com>
- Date: Sun, 20 Oct 2013 11:17:12 +0100
- To: "public-web-mobile@w3.org" <public-web-mobile@w3.org>
- CC: Tobie Langel <tobie@w3.org>, Robert Shilston <robert.shilston@ft.com>
From: Robert Shilston <robert.shilston@ft.com> Date: Friday, 18 October 2013 19:58 >[snip] > >This is certainly a very interesting conversation. However, I wonder >whether spending lots of effort on identifying gaps and pushing forwards >initiatives to close them will mean web developers are permanently trying >to catch up and > feel second-rate citizens in the mobile world. I think it there is >value in considering where the web is already ahead, or where it has the >potential to be ahead. Then lets celebrate those AND ensure that we're >remaining ahead. Let's make native applications > feel they need to catch up with the web rather than vice-versa. I do not disagree. However I think we have to look squarely at why native app platforms are currently the approach of choice for mobile application developers even though they are not cross-platform. The mobile Web has unique advantages - linkability, cross-platform deployment, etc... but developers are still choosing to go native. The research that Dimitris is sharing with us is looking at that aspect: if the Web can learn from the success of native app development and incorporate certain aspects of native approaches - e.g. APIs - then we can start to close that gap. We will start to see more app developers embracing the Web as a development and deployment platform of choice. I think there is room in this discussion both for shoring up the Web platform / closing the gap AND also for exploring where the Web differentiates and pulls ahead of native platforms. But we cannot be in denial of the fact that native app platforms are kicking the Web's ass right now. Otherwise we are just fiddling while Rome burns. Dan
Received on Sunday, 20 October 2013 10:18:17 UTC