Permalink
Browse files

Initiate release sequencer! Standby on my mark...launch! [initial com…

…mit]

#mobilewood / Night Donkey present Future Friendly.
  • Loading branch information...
0 parents commit f99cd41fac3aca73aaf057af8ae4fa3659704c77 @lyzadanger lyzadanger committed Sep 20, 2011
@@ -0,0 +1 @@
+.DS_Store
@@ -0,0 +1,36 @@
+AddDefaultCharset utf-8
+AddType text/cache-manifest .appcache
+Options +FollowSymLinks
+RewriteEngine on
+RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
+RewriteRule ^(.*)$ http://%1/$1 [R=301,L]
+<IfModule mod_setenvif.c>
+ <IfModule mod_headers.c>
+ BrowserMatch MSIE ie
+ Header set X-UA-Compatible "IE=Edge,chrome=1" env=ie
+ </IfModule>
+</IfModule>
+
+# Add gzip compression
+<IfModule mod_deflate.c>
+ AddOutputFilterByType DEFLATE text/html
+ AddOutputFilterByType DEFLATE text/plain
+ AddOutputFilterByType DEFLATE text/xml
+ AddOutputFilterByType DEFLATE text/css
+ AddOutputFilterByType DEFLATE application/javascript
+ AddOutputFilterByType DEFLATE application/x-javascript
+ AddOutputFilterByType DEFLATE application/x-httpd-php
+ AddOutputFilterByType DEFLATE application/rss+xml
+ AddOutputFilterByType DEFLATE application/atom_xml
+</IfModule>
+
+# Cach(e)ing!!! Woop!
+<IfModule mod_expires.c>
+ # Enable expirations.
+ ExpiresActive On
+ # Cache all files for 2 weeks after access (A).
+ ExpiresDefault A1209600
+</IfModule>
+
+Header unset ETag
+FileETag None
@@ -0,0 +1,15 @@
+# Future Friendly
+## [futurefriend.ly](http://futurefriend.ly)
+
+A manifesto, thinking points and resources for the future-friendly web. Built lovingly at #mobilewood by:
+
+Stephanie Rieger
+Jeremy Keith
+Josh Clark
+Brad Frost
+Lyza Danger Gardner
+Luke Wroblewski
+Bryan Rieger
+Jason Grigsby
+Scott Jenson
+Scott Jehl
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,91 @@
+Proprietary solutions will define possibilities of device and interaction.
+But will have to retreat to standards. But what to standardize?
+Standards will break down under this overwhelming load.
+
+Future friendly:
+
+Reduction.
+
+Data portability: API first. Data exchange is one way to go. Run faster to create new stuff. And future friendly.
+- interoperability between service and data source
+- flexibility and fluidity, like html and json. it gives.
+- push and pull data.
+- read/write.
+- long-range data integrity as format.
+
+Device profiling
+- small number of profile device categories simplify problem
+- short term stems chaos
+- long term creates market by creating established categories
+- animal, vegetable, mineral
+- high-level. nitty gritty can wait til later.
+
+Inter-profile interactions.
+- delegation to and interaction between multiple devices.
+- push content across points
+- you are a collection of devices that is part of an ecosystem.
+- commonality of experience across all.
+
+
+BROWSER GHETTO
+
+Web vs native is just today's problem. The problem that is that there's a caste system of favored technologies. So we want to get to a point that data and services should not be trapped in a caste system. How do we avoid a caste system?
+
+Caste is formed by notions of browsing vs doing, of complexity and polish vs simplicity and accessibility. We need to change browsers from being engines of consumption to engines of creation, which is currently the domain of the app. How do we close the distance so that browser apps and native apps are indistinguishable. Why choose?
+
+The fix:
+
+Transformation
+Encapsulation
+Abstraction
+
+* Make content addressable and available by any user agent on any device, understanding that security is an issue. Browser is my secretary. I should be able to get all of my data, all of my files at any time through a URL. This is the iCloud/Dropbox dream, it's the browser as both personal and public file system.
+
+* This should include random-access addressability to any portion of content in any medium. Not just the whim of a developer who has dropped an anchor link in, or a chaptered audio book, or a timecoded video. But random access.
+
+* All content should be addressable, and all people should be able to create addressable content. Abstract away notions of FTP and protocols and make it easy to write/create addressable content. A farmer in west africa can share and download crop reports with an easy-tocreate permanent address to that document or concept.
+
+* This content must be neutrally and semantically formatted such that it is transformable in presentation, structure, and content. It is not tied to device or presentation or context.
+
+* Browsers should be better at sharing the individual's state and location within that address, saving that back to the network.
+
+* This is about statefulness of time and location across medium and context. I'm reading on my laptop, I go on a walk and start LISTENING at same point.
+
+* The browser itself should be invisible.
+
+* You should be able to encapsulate content and features and save that as an "app."
+
+* This is currently the domain of experts, but regular people should be able to create the same. An easier automator/pipes/fluid/this-then-that.
+
+* Portable and shareable. Anybody can create and share an app, like the Chrome Web Store, or dashboard widgets are a primitive.
+
+* This encapsulation should abstract what is being encapsulated, it's just an app no matter what it's made out of.
+
+One piece of the solution also addresses a follow-on problem, where's the PAIN. Building native apps is overwhelming. Yet the browser itself is a native app. A huge problem with native apps is that we have to keep building our own browser each and every time. One fix is a better browser that ALL can use.
+
+Show, don't tell. One fix: Phonegap browser.
+
+* For shame. You already have a browser that should do what you do.
+* Empowering users to use the web at the cutting edge of the specification.
+* Empower to make full use of their device.
+* The browser itself would be zen garden.
+
+CONTENT LIKE WATER
+
+Not sufficiently structured to enable reuse. Can't do anything actionable with it. Inevitably, tools are holding us back because they don't help it. But also, behavior is a problem, we have to WANT to do it.
+
+Structured content first: Core content devoid of container, but to an extra level. Microcontent. More malleable, more enhanceable in the future.
+
+Markup structure.
+
+Single URI and canonical link.
+
+Generally fluid layer of contextual enhancement, not just of presentation but of relationships, behavior, presentation, mix up architecture in different context, narrative too, social layer.
+
+Simple, concrete ways to change their behavior.
+
+Lack of tangible value. Not clear why. Not structured right. Now we can convince people:
+
+You will be able to do more with your content. SAVE MONEY, get value. The sooner you do it, the more value you get.
+
+METADATA IS THE NEW ART DIRECTION.
@@ -0,0 +1,71 @@
+<!DOCTYPE html>
+<html manifest="manifest.appcache">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, minimum-scale=1.0">
+ <title>Future Friendly</title>
+ <link href="styles.css" rel="stylesheet">
+</head>
+<body id="manifesto">
+
+<header role="banner">
+ <h1><img src="assets/fflogo.png" alt="Future Friendly" title="Future Friendly"></h1>
+ <p>In today's incredibly exciting yet overwhelming world of connected digital devices, these are the truths we hold to be self-evident:</p>
+</header>
+
+<ul id="truths">
+ <li id="disruption-will-accelerate"><strong>Disruption will only accelerate.</strong> The quantity and diversity of connected devices&mdash;many of which we haven't imagined yet&mdash;will explode, as will the quantity and diversity of the people around the world who use them.</li>
+ <li id="infrastructure-fail"><strong>Our existing standards, workflows, and infrastructure won't hold up.</strong> Today's onslaught of devices is already pushing them to the breaking point. They can't withstand what's ahead.</li>
+ <li id="proprietary-first"><strong>Proprietary solutions will dominate at first.</strong> Innovation necessarily precedes standardization. Technologists will scramble to these solutions before realizing (yet again) that a standardized platform is needed to maintain sanity.</li>
+ <li id="standards-slow"><strong>The standards process will be painfully slow.</strong> We will struggle with (and eventually agree upon) appropriate standards. During this period, the web will fall even further behind proprietary solutions.</li>
+</ul>
+
+<section id="hope">
+ <header>
+ <h2>A New Hope</h2>
+ </header>
+ <p>But there's hope. While we can't know exactly what the future will bring, we can:</p>
+ <ol>
+ <li id="acknowledge">Acknowledge and embrace unpredictability.</li>
+ <li id="be">Think and behave in a <a href="thinking.html">future-friendly way</a>.</li>
+ <li id="help">Help others do the same.</li>
+ </ol>
+ <p>The future is ours to make &mdash;friendly.</p>
+</section>
+
+<section id="signatories">
+ <header>
+ <h2>Undersignums</h2>
+ </header>
+ <img src="assets/signed.png" alt="Signatures of the names that follow">
+ <ul>
+ <li class="vcard"><a href="http://www.lukew.com" class="fn url">Luke Wroblewski</a></li>
+ <li class="vcard"><a href="http://designmind.frogdesign.com/blog/author/beyond-mobile/" class="fn url">Scott Jenson</a></li>
+ <li class="vcard"><a href="http://bradfrostweb.com" class="fn url">Brad Frost</a></li>
+ <li class="vcard"><a href="http://adactio.com" class="fn url">Jeremy Keith</a></li>
+ <li class="vcard"><a href="http://lyza.com" class="fn url">Lyza D. Gardner</a></li>
+ <li class="vcard"><a href="http://scottjehl.com" class="fn url">Scott Jehl</a></li>
+ <li class="vcard"><a href="http://yiibu.com" class="fn url">Stephanie Rieger</a></li>
+ <li class="vcard"><a href="http://userfirstweb.com" class="fn url">Jason Grigsby</a></li>
+ <li class="vcard"><a href="http://yiibu.com" class="fn url">Bryan Rieger</a></li>
+ <li class="vcard"><a href="http://globalmoxie.com/" class="fn url">Josh Clark</a></li>
+ </ul>
+</section>
+
+<nav role="navigation">
+ <ul>
+ <li><a>Home</a></li>
+ <li><a href="thinking.html">Thinking</a></li>
+ <li><a href="resources.html">Resources</a></li>
+</ul>
+</nav>
+
+<footer role="contentinfo">
+ <ul>
+ <li>We're <a rel="license" href="http://creativecommons.org/licenses/by/3.0">Creative Commons friendly.</a></li>
+ <li><a href="https://twitter.com/grigs/mobilewood/members">Talk to us.</a></li>
+ </ul>
+</footer>
+
+</body>
+</html>
@@ -0,0 +1,17 @@
+CACHE MANIFEST
+
+#version 1.1
+
+CACHE:
+
+/assets/fflogo.png
+/assets/signed.png
+
+/index.html
+/thinking.html
+/resources.html
+
+/styles.css
+
+NETWORK:
+*
@@ -0,0 +1,83 @@
+<!DOCTYPE html>
+<html manifest="manifest.appcache">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, minimum-scale=1.0">
+ <title>Future-Friendly Resources</title>
+ <link rel="stylesheet" href="styles.css">
+</head>
+<body id="resources">
+
+<header role="banner">
+ <a href="index.html"><img src="assets/fflogo.png" alt="Future Friendly" title="Future Friendly"></a>
+ <h1>Future-Friendly Resources</h1>
+</header>
+
+<p>In the spirit of embracing unpredictability, here are some resources to help you start thinking and acting in a future-friendly way. Please help us extend the list of worthwhile forward-thinking resources.</p>
+
+<section id="landscape">
+ <header>
+ <h2>Landscape</h2>
+ </header>
+ <ul>
+ <li><a href="http://www.slideshare.net/yiibu/letting-go-9109114" rel="external">Letting Go</a></li>
+ <li><a href="http://designmind.frogdesign.com/blog/the-coming-zombie-apocalypse-small-cheap-devices-will-disrupt-our-old-school-ux-assumptions.htm" rel="external">The Coming Zombie Apocalypse</a></li>
+ <li><a href="http://precious-forever.com/2011/05/26/patterns-for-multiscreen-strategies/" rel="external">Multiscreen Patterns</a></li>
+ <li><a href="http://www.lukew.com/ff/entry.asp?1320" rel="external">First-Person User Interfaces</a></li>
+ <li><a href="http://www.lukew.com/ff/entry.asp?862" rel="external">Networked Consumer Device Platforms</a></li>
+ </ul>
+</section>
+
+<section id="context">
+ <header>
+ <h2>Context</h2>
+ </header>
+ <ul>
+ <li><a href="http://www.cloudfour.com/on-mobile-context" rel="external">On Mobile Context</a></li>
+ <li><a href="http://www.lukew.com/ff/entry.asp?1393" rel="external">There Is No Mobile Web</a></li>
+ <li><a href="http://yiibu.com/articles/wider-context/" rel="external">A Wider Context</a></li>
+ <li><a href="http://adactio.com/journal/4443/" rel="external">Context</a></li>
+ <li><a href="http://mark-kirby.co.uk/2011/the-mobile-context/" rel="external">The Mobile Context</a></li>
+ <li><a href="http://www.uxbooth.com/blog/its-about-people-not-devices/" rel="external">It's About People, Not Devices</a></li>
+ </ul>
+</section>
+
+<section id="content">
+ <header>
+ <h2>Content</h2>
+ </header>
+ <ul>
+ <li><a href="http://www.slideshare.net/stephenhay/structured-content-first" rel="external">Structured Content First</a></li>
+ <li><a href="http://endlesslycontent.com/2011/08/04/structured-content-shifting-context-responsive-design/" rel="external">Structured Content, Shifting Context</a></li>
+ <li><a href="http://endlesslycontent.com/2011/06/30/content-first/" rel="external">Content First?: Semantics, Structure, and Why We Should Care</a></li>
+ </ul>
+</section>
+
+<section id="approach">
+ <header>
+ <h2>Approach</h2>
+ </header>
+ <ul>
+ <li><a href="http://www.lukew.com/presos/preso.asp?26" rel="external">Mobile First</a></li>
+ <li><a href="http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/" rel="external">COPE: Create Once, Publish Everywhere</a></li>
+ <li><a href="http://www.lukew.com/ff/entry.asp?940" rel="external">Integration Across Networked Devices</a></li>
+ </ul>
+</section>
+
+<nav role="navigation">
+ <ul>
+ <li><a href="index.html">Home</a></li>
+ <li><a href="thinking.html">Thinking</a></li>
+ <li><a>Resources</a></li>
+ </ul>
+</nav>
+
+<footer role="contentinfo">
+ <ul>
+ <li>We're <a rel="license" href="http://creativecommons.org/licenses/by/3.0">Creative Commons friendly.</a></li>
+ <li><a href="https://twitter.com/grigs/mobilewood/members">Talk to us.</a></li>
+ </ul>
+</footer>
+
+</body>
+</html>
Oops, something went wrong.

0 comments on commit f99cd41

Please sign in to comment.