-
Notifications
You must be signed in to change notification settings - Fork 1
/
provider-actions.html
148 lines (135 loc) · 5.66 KB
/
provider-actions.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
<!DOCTYPE html>
<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="content-type">
<title>Improving Web Apps Gap From Provider Perspective</title>
<link rel="stylesheet" href="http://www.w3.org/2007/08/video/style.css" type="text/css">
<link rel="stylesheet" href="http://www.w3.org/2007/08/video/print.css" type="text/css"
media="print">
<link rel="stylesheet" href="http://www.w3.org/2013/06/mobile-web-app-state/style.css"
type="text/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>Improving Web Apps Gap From Provider Perspective</h1>
</div>
<div 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, based on the analysis of <a href="http://w3c-webmob.github.io/gap-analysis/provider-webapps.html">how Web apps
currently fare from a provider perspective</a>, discusses some possible
actions that could be pursued to reduce Web apps weaknesses and increase
their existing advantages.</p>
<p>See also the <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>.</p>
<h2>Action Plans for Improving Web Applications from Provider Perspective</h2>
<p class="issue">These are very sketchy ideas that need to be further
developed and turned into concrete action plans if and when they're deemed
appropriate.</p>
<h3>Development cost</h3>
<h4>Hiring / training developers</h4>
Training? Best Practices?
<h4>Writing code</h4>
<br>
<h4>Finding documentation and guidance</h4>
WebPlatform.org?
<h4>Finding libraries</h4>
<br>
<h4>Reporting platform bugs</h4>
<ul>
<li>Provide a one-stop bug reporting system for the Web (managed
by a W3C bug squad?)</li>
<li>Provide integrated views of various open bugs systems among
browsers (à la <a href="http://www.chromestatus.com/features">Chrome
dashboard</a>)?</li>
</ul>
<h4>Debugging and diagnostics</h4>
<ul>
<li>Push <a href="https://docs.google.com/document/d/1Yw_qNMCnGsWQRsdcrifzh_kzFey-ThQ3yp-DmxuJxvg/edit?pli=1">Web
Application Diagnosis</a> API</li>
<li>Workshop on debugging tools?</li>
</ul>
<h4>Testing</h4>
Improve Web Driver API to include more chrome-based interactions
<h3>Deployment cost</h3>
<h4>Getting authorization to deploy</h4>
<br>
<h4>Uploading the app</h4>
<br>
<h4>Advertising the app</h4>
Promote searchability of apps and associated reviews?
<h4>Protecting the app code and operations</h4>
Relationship between Browsers and Trusted Environments?
<h3>Maintenance cost</h3>
<h4>Getting user input and feedback</h4>
Better identity management
<h4>Keeping up with incompatible changes in the platform</h4>
<br>
<h4>Getting visibility into future new features of the
platform</h4>
<br>
<h3>Expected outcomes</h3>
<h4>Reaching out to as many users as possible</h4>
<br>
<h4>Getting paid</h4>
Standardize a payment API
<h4>Getting recognition</h4>
<br>
<h4>Enabling social change</h4>
<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:dom@w3.org">dom@w3.org</a>> / <a href="http://twitter.com/dontcallmedom">@dontcallmedom</a><br>
Last Modified: $Date: 2013-09-18 07:41:36 $</address>
</div>
</body>
</html>