-
Notifications
You must be signed in to change notification settings - Fork 1
/
provider-webapps.html
254 lines (253 loc) · 9.22 KB
/
provider-webapps.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Web Apps Gap Analysis From Provider Perspective</title>
<link rel="stylesheet" href="http://www.w3.org/2007/08/video/style.css">
<link rel="stylesheet" href="http://www.w3.org/2007/08/video/print.css"
media="print">
<link rel="stylesheet" href="http://www.w3.org/2013/06/mobile-web-app-state/style.css">
<style>figure { text-align:center; margin: 1em; }
figcaption { font-style: italic;}
dd { margin-bottom:1em;}
dt { margin-bottom: 0.2em;}
dd p:first-child { margin-top: 0.5em;}
p.continued { margin-bottom: 0em;}
th.category { color: #E2EDFE; background-color:#005A9C;}
td ul { margin:0; padding:0;}
td ul li { margin-left:0.7em;}
div.issue, div.note {
clear: both;
margin: 1em 0;
padding: 1em 1.2em 0.5em;
position: relative;
}
.issue {
background: none repeat scroll 0 0 #FBE9E9;
border-color: #E05252;
}
.issue, .note {
border-left-style: solid;
border-left-width: 0.5em;
padding: 0.5em;
}
tbody {
page-break-inside:avoid;
}
/*table { margin:0 -5em;}*/
</style>
</head>
<body>
<div id="page">
<h1>Web Apps Gap Analysis From Provider Perspective</h1>
</div>
<main id="main">
<p class="logo">
<a href="http://www.w3.org/">
<img alt="W3C" src="http://www.w3.org/Icons/w3c_home"/>
</a>
</p>
<h2>Status</h2>
<p>This is a draft, work-in-progress analysis derived from the <a href="http://www.w3.org/wiki/Closing_the_gap_with_native">“Closing
the Gap with Native” Headlight task force</a>.</p>
<h2>Introduction</h2>
<p>To compare the various existing mobile apps development approaches, two
main perspectives can be taken:</p>
<ul>
<li>from the end-user perspective: how well the said development approach
will make it possible to provide the best possible user experience;</li>
<li>from the content and service provider perspective: how well the said
development approach will optimize their costs and benefits.</li>
</ul>
<p>This document applies the <a href="http://w3c-webmob.github.io/gap-analysis/provider-comparison-framework.html">separately developed model to
analyze a give mobile app development approach from provider perspective</a>
to Web applications.</p>
<p>See also:</p>
<ul>
<li><a href="http://w3c-webmob.github.io/gap-analysis/provider-actions.html">Proposals to reduce the gaps of Web applications from a provider perspective</a></li>
<li><a href="http://w3c-webmob.github.io/gap-analysis/ux-comparison-framework.html">Framework to compare mobile apps development approaches
from a user experience perspective</a></li>
</ul>
<h2>Web Applications Strengths and Weaknesses from a Provider Perspective</h2>
<table>
<caption>Strength/Weakness for the provider experience for Web apps on
mobile</caption>
<thead>
<tr>
<th>Provider experience parameter</th>
<th>Strength</th>
<th>Weakness</th>
</tr>
</thead>
<tbody>
<tr>
<th colspan="3">Development cost</th>
</tr>
<!--
<tr><th scope="row"></th><td></td><td></td><td></td></tr>-->
<tr>
<th scope="row">Hiring / training developers</th>
<td>A lot of Web developers</td>
<td>Not many Web developers know how to develop good Web apps for
mobile</td>
</tr>
<tr>
<th scope="row">Writing code</th>
<td>Plenty of IDEs for the Web</td>
<td>Support for responsive approaches?</td>
</tr>
<tr>
<th scope="row">Finding documentation and guidance</th>
<td>Lots of Web-related sites and forums</td>
<td>Lack of authoritative content?</td>
</tr>
<tr>
<th scope="row">Finding libraries</th>
<td>Lots of them</td>
<td>Hard to find the right one, esp. with mobile constraints</td>
</tr>
<tr>
<th scope="row">Reporting platform bugs</th>
<td>Technologies are developed in public</td>
<td>
<ul>
<li>Hard to find the right forum to target</li>
<li>Hard to distinguish between browser bug and platform bug</li>
</ul>
</td>
</tr>
<tr>
<th scope="row">Debugging and diagnostics</th>
<td>
Same Web platform on desktop and mobile makes it somewhat easier to
debug
</td>
<td>
<ul>
<li>Growing but still very limited toolset</li>
<li>Toolset almost always browser-specific, thus hard to apply
interoperably</li>
<li>Memory management particularly poor</li>
<li>Browser/device-specific bugs particularly hard to pinpoint</li>
</ul>
</td>
</tr>
<tr>
<th scope="row">Testing</th>
<td>
Lots of automated testing tools, incl. on mobile
</td>
<td>Hard to test chrome-based user interactions (e.g. consent dialog)</td>
</tr>
</tbody>
<tbody>
<tr>
<th colspan="3">Deployment cost</th>
</tr>
<tr>
<th scope="row">Getting authorization to deploy</th>
<td>None required</td>
<td><br>
</td>
</tr>
<tr>
<th scope="row">Uploading the app</th>
<td>Mostly seamless</td>
<td><br>
</td>
</tr>
<tr>
<th scope="row">Advertising the app</th>
<td>As open as anything else on the Web</td>
<td>
<ul>
<li>No well-known central location with high visibility for users</li>
<li>No well-known ways for users to describe well-rated apps</li>
</ul>
</td>
</tr>
<tr>
<th scope="row">Protecting the app code and operations</th>
<td>Server-side component out of reach to client-side attackers</td>
<td>Hard to get as thorough protection of client-side as available to
native apps</td>
</tr>
</tbody>
<tbody>
<tr>
<th colspan="3">Maintenance cost</th>
</tr>
<tr>
<th scope="row">Getting user input and feedback</th>
<td>Use the Web</td>
<td>No one-click infrastructure to share comments associated to a
given identity (assuming reputation is an incentive)</td>
</tr>
<tr>
<th scope="row">Keeping up with incompatible changes in the platform</th>
<td>Platform evolutions are decided in the open</td>
<td>Hard to keep track of these evolutions</td>
</tr>
<tr>
<th scope="row">Getting visibility into future new features of the
platform</th>
<td><ul><li>Platform evolutions are decided in the open</li><li>Anyone can be part of the decision process</li></ul></td>
<td><ul><li>Hard to keep track of these evolutions</li><li>Getting involved takes a lot of time</li></ul></td>
</tr>
</tbody>
<tbody>
<tr>
<th colspan="3">Expected outcomes</th>
</tr>
<tr>
<th scope="row">Reaching out to as many users as possible</th>
<td>
<ul>
<li>Web works everywhere</li>
<li>URLs make it easy for users to spread the word</li>
</ul>
</td>
<td>Hard to design apps that work well across many devices, browsers,
culture, etc.</td>
</tr>
<tr>
<th scope="row">Getting paid</th>
<td>Each provider can pick its most appropriate payment system</td>
<td><ul><li>No general one-click solution to payment</li><li>Advertizing networks less developed for mobile Web</li><li>Lack of off-line adverts</li></td>
</tr>
<tr>
<th scope="row">Getting recognition</th>
<td>Neutral?</td>
<td><br>
</td>
</tr>
<tr>
<th scope="row">Enabling social change</th>
<td>
<ul>
<li>No commercial entity in a position to censor</li>
<li>Availability to many more devices to lower cost</li>
</ul>
</td>
<td><br>
</td>
</tr>
</tbody>
</table>
</main>
<div id="footer">
<p style="text-align:left;margin-left:0;margin-right:auto;"> <span style="font-size: 10pt"><a
href="http://webinos.org/"><img alt="Webinos logo" src="http://www.w3.org/2012/08/web-and-automotive/webinos.png"
style="float: left"></a> This project is funded by the European
Union through the
Seventh Framework Programme (FP7/2010-2013) under grant agreement
n°257103
<a href="http://webinos.org/">webinos</a></span> </p>
<hr>
<address><a href="http://www.w3.org/People/Dom/">Dominique
Hazaël-Massieux</a> <<a href="mailto:[email protected]">[email protected]</a>>
/ <a href="http://twitter.com/dontcallmedom">@dontcallmedom</a><br>
Last Modified: $Date: 2013-09-18 07:41:36 $</address>
</div>
</body>
</html>