forked from mozilla/mobile-opportunity
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathgoals.html
More file actions
18 lines (17 loc) · 5.12 KB
/
goals.html
File metadata and controls
18 lines (17 loc) · 5.12 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
<!DOCTYPE html><html><head><meta name="viewport" content="width=device-width, user-scalable=no, target-densityDpi=device-dpi"><title>Mobile Opportunity Project</title><base href="//mozillafordevelopment.org/"><a href="https://www.mozilla.org/" id="tabzilla">mozilla</a></head><body><div class="wrapper"><header><h1> <a href="">Mobile Opportunity Research</a></h1><p>This website documents the ongoing work by the Mobile Opportunity project team at Mozilla.</p><h3><a href="goals#goals">Goals</a></h3><h3> <a href="approach#approach">Approach</a></h3><h3> <a href="plan#plan">Plan</a></h3><!--<h3> <a href="voices#voices">Voices</a></h3><h3><a href="background#background">Background Data</a></h3><h3><a href="docs#docs">Mockups, Demos & Reports</a></h3><h3> <a href="questions#questions">Questions</a></h3>--><p>Our work is public. You can track our
<a href="wiki.mozilla.org/Mobile_Opportunity">wiki documentation</a>
, as well as our <a href="https://github.com/mozilla/mobile-opportunity/issues/milestones">issue tracking</a>.</p><p>This website is authored in github, edits via <a href="https://github.com/mozilla/mobile-opportunity/tree/master/_website">pull requests</a> or <a href="https://github.com/mozilla/mobile-opportunity/issues/new">issues</a> are welcome.</p></header></div><section><h1 id="goals">Assumptions and Goals</h1><p>The goals of this project are varied, befitting the potential long-term impact of the changes that we see possible.</p><p>We believe that for the internet to have the broadest positive impact, <b>everyone using the internet should be able to shape their digital lives</b>. This is not a new idea -- since the first years of the web, "normal people" creating web content has been a part of the web ecosystem. As that ecosystem has grown and evolved, and in particular with the advent of smartphones, the technical and access barriers to creating original content on the internet have grown dramatically. This shift is compounded by new control mechanisms (central appstores), user interface affordance challenges (traditional coding on a phone is impossible), and most striking for individuals without the time and money to learn the "stack" of skills and knowledge required to create and publish new content.</p><p>We hope to investigate possible remediations of this staggering bias which could help make it easier for <b>non-programmers</b>, especially in markets where phones will be the primary access point to the internet, <b>to access, modify and share locally relevant content <em>right on their phones</em></b>. We <em>do not</em> expect to provide someone with no programming skills the same generative power to create arbitrarily complex apps. Instead, we will identify specific use cases, categories of remixable/reconfigurable apps which, while likely limited, can provide a) a psychologically powerful feeling of agency, b) some direct utility, c) a glimpse that they <em>can</em> contribute meaningfully to their local internet life, and possibly entice them to learn and do more.</p><p>While many of us have been exploring related questions with the <a href="apps.webmaker.org">Mozilla Appmaker</a> project, we do not assume that any of the details of that project are necessarily useful here. That project's initial design was made for people in developed countries with access to high-bandwidth desktop computers, and we are well aware that many of the decisions made for that version of Appmaker are inappropriate in a mobile-only environment.</p><div class="sidebar"><p>While we will use terms like <em>research</em> and <em>hypothesis</em>, we do not claim to use a rigorous scientific approach. Given the time and budgetary constraints, we're hoping to articulate hunches (especially from collaborators in the field), learn about the perceived needs of a variety of user populations, build prototypes derived from those hunches, and test them qualitatitvely.</p></div><p>To find out more how we hope to tackle these goals, read our <a href="approach#approach">approach model</a>.</p> <div id="disqus_thread"></div>
<script type="text/javascript">
/* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
var disqus_shortname = 'mobileopportunity'; // required: replace example with your forum shortname
/* * * DON'T EDIT BELOW THIS LINE * * */
(function() {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
})();
</script>
<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
<a href="http://disqus.com" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>
</section></body></html><footer><link rel="stylesheet" href="googlefonts.css"><link rel="stylesheet" href="main.css"><script src="//mozorg.cdn.mozilla.net/tabzilla/tabzilla.js"></script>
<link href="//mozorg.cdn.mozilla.net/media/css/tabzilla-min.css" rel="stylesheet" /></footer>