-
Notifications
You must be signed in to change notification settings - Fork 1
/
provider-comparison-framework.html
131 lines (119 loc) · 4.96 KB
/
provider-comparison-framework.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
<!doctype html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Comparing mobile apps platforms from a 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>Comparing mobile apps platforms from a 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 proposes a model to analyze a give mobile app development approach from provider perspective. To that end, it identifies the various high level operations a provider will be confronted to create, deploy and maintain a mobile application on the market.</p>
<p>See also:</p>
<ul>
<li><a href="http://w3c-webmob.github.io/gap-analysis/provider-webapps.html">Application of this framework to Web apps compared to native apps</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>A Framework for comparing mobile apps approaches from a provider perspective</h2>
<p>To make it sustainable to provide a given application, content and service providers need an environment that reduces as much as possible the costs of developing, deploying and maintaining a given application, and maximizes the expected outcome, which can be, but is not necessarily, of monetary nature.</p>
<p>The following parameters are taken into account to assess the costs:</p>
<dl>
<dt>Development cost</dt>
<dd>
<ul>
<li>Hiring / training developers</li>
<li>Writing code</li>
<li>Finding documentation and guidance</li>
<li>Finding libraries</li>
<li>Reporting platform bugs</li>
<li>Debugging and diagnostics</li>
<li>Testing</li>
</ul>
</dd>
<dt>Deployment cost</dt>
<dd>
<ul>
<li>Getting authorization to deploy</li>
<li>Uploading the app</li>
<li>Advertising the app</li>
<li>Protecting the app code</li>
</ul>
</dd>
<dt>Maintenance cost</dt>
<dd>
<ul>
<li>Getting user input and feedback</li>
<li>Keeping up to date with changes (in particular incompatible ones) in the platform</li>
<li>Getting visibility into future evolutions of the platform</li>
</ul>
</dd>
<dt>Expected outcomes</dt>
<dd>
<ul>
<li>Reaching out to as many users as possible</li>
<li>Getting paid</li>
<li>Getting recognition</li>
<li>Enabling social change</li>
</ul></dd>
</dl>
<div class="issue">Expected outcomes is a bit hand-wavy: is there another better way to phrase this? Are there other high level outcomes we should include?</div>
<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>
</div>
</body>
</html>