Permalink
Switch branches/tags
Nothing to show
Find file
Fetching contributors…
Cannot retrieve contributors at this time
98 lines (87 sloc) 5.34 KB
<!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 Thinking</title>
<link rel="stylesheet" href="styles.css">
</head>
<body id="thinking">
<header role="banner">
<a href="index.html"><img src="assets/fflogo.png" alt="Future Friendly" title="Future Friendly"></a>
<h1>Future-Friendly Thinking</h1>
</header>
<p>We want to make things that are future friendly. By anticipating what's next, we can react to today's concerns but also build long-term value for people and businesses. The following ideas have been on our minds recently. Help us explore them further or suggest new ones.</p>
<section id="laser-focus">
<header>
<h2>Laser Focus</h2>
</header>
<p>We can't be all things on <strong>all</strong> devices. To manage in a world of ever-increasing device complexity, we need to focus on what matters most to our customers and businesses. Not by building lowest common-denominator solutions but by creating meaningful content and services. People are also increasingly tired of excessive noise and finding ways to simplify things for themselves. Focus your service before your customers and increasing diversity do it for you.</p>
<ul>
<li><a href="http://adactio.com/journal/4523/">Content First</a></li>
<li><a href="http://www.lukew.com/ff/entry.asp?933">Mobile First</a></li>
<li><a href="http://www.alistapart.com/articles/orbital-content/">Orbital Content</a></li>
</ul>
</section>
<section id="orbit-around-data">
<header>
<h2>Orbit Around Data</h2>
</header>
<p>An ecosystem of devices demands to be interoperable, and robust data exchange is the easiest way to get going. Be responsive to existing and emerging opportunities by defining your data in a way that: enables multiple (flexible) forms of access and notifications; uses standards to be interoperable; focuses on long term integrity; includes meaningful and permanent references to all content; supports both read and write operations.</li>
</ul>
<ul>
<li><a href="http://blog.programmableweb.com/2009/10/13/cope-create-once-publish-everywhere/">COPE: Create Once, Publish Everywhere</a></li>
<li><a href="https://bagcheck.com/blog/8-bagchecking-in-the-command-line">Bagchecking in the Command Line</a></li>
<li><a href="http://jenson.org/the-ux-of-data/">The UX of Data</a></li>
</ul>
</section>
<section id="universal-content">
<header>
<h2>Universal Content</h2>
</header>
<p>Well-structured content is now an essential part of art direction. Consider how it can flow into a variety of containers by being mindful of their constraints and capabilities. Be bold and explore new possibilities but know the future is likely to head in many directions.</p>
<p>Highly capable smart devices, simple constrained devices, interoperable devices and (a whole lot) more are part of our future. Structure and store your content accordingly.</p>
<ul>
<li><a href="http://www.alistapart.com/articles/future-ready-content/">Future-Ready Content</a></li>
<li><a href="http://www.lukew.com/ff/entry.asp?1529">Adaptive Web Content</a></li>
<li><a href="http://www.markboulton.co.uk/journal/comments/structure-first-content-always">Structure First. Content Always.</a></li>
</ul>
</section>
<section id="unknown-vessel">
<header>
<h2>Unknown Vessel, Identify</h2>
</header>
<p>Reacting to every device variance makes inclusive design extremely challenging. A high-level, close-enough set of standards for device types can simplify the process of adaptation. Additional, detailed profile information can supplement these standards.</p>
<p>A taxonomy of device types can align manufacturers today while still allowing new devices types to emerge tomorrow.</p>
<ul>
<li><a href="http://detector.dmolsen.com/">Detector</a></li>
<li><a href="http://stephanierieger.com/an-introduction-to-the-yiibu-profile-tool/">An introduction to the Yiibu Profile Tool</a></li>
<li><a href="https://developers.facebook.com/blog/post/2012/01/24/device-experiences---responsive-design/">Device Experiences &amp; Responsive Design</a></li>
</ul>
</section>
<section id="command-fleet">
<header>
<h2>Command your Fleet</h2>
</header>
<p>Having a wide range of devices in our lives enables us to distribute tasks and information between them. When an experience is managed within a device collection, each device can tackle the interactions it does best. This negates the need to tailor all aspects of a service to every device and allows us to work within an ecosystem of device capabilities instead.</p>
<ul>
<li><a href="http://precious-forever.com/2011/05/26/patterns-for-multiscreen-strategies/">Multiscreen Patterns</a></li>
<li><a href="http://www.lukew.com/ff/entry.asp?1523">Beyond Mobile</a></li>
<li><a href="http://www.lukew.com/ff/entry.asp?828">Designing for Sensors</a></li>
</ul>
</section>
<nav role="navigation">
<ul>
<li><a href="index.html">Home</a></li>
<li><a>Thinking</a></li>
<li><a href="come-aboard.html">Come Aboard</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>