<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
        <channel>
        <title>Jonathan Stark - ReadWrite</title>
        <link>http://readwrite.com</link>
        <description />
        <language>en</language>
        <copyright>Copyright 2012 SAY Media, Inc.</copyright>
        <managingEditor>readwriteweb@gmail.com</managingEditor>
        <docs>http://blogs.law.harvard.edu/tech/rss</docs> 
        <lastBuildDate>Mon, 04 Feb 2013 06:00:00 -0800</lastBuildDate>
        <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://rww.superfeedr.com/" />

                    <item>
                <title><![CDATA[Screen-Less Mobile Computers: Talking Changes Everything]]></title>
                <description><![CDATA[
                                        <img src="http://readwrite.com/files/styles/800_450sc/public/fields/shutterstock_103018946.jpg" />
                                        <p><em style="line-height: 1.538em;">Guest author Jonathan Stark i</em><em style="line-height: 1.538em;">s a mobile consultant, Web evangelist and an advisory board member at <a href="http://mobiquityinc.com/" target="_blank">Mobiquity</a>, a designer of customized mobile computing applications.</em></p>
<p class="p1">Until 2007, "computing" meant sitting down to use a PC with both hands. When smartphones came on the scene, we got used to computing with one hand while standing, walking - even running.</p>
<p class="p3">As great as they are, smartphones have a significant limitation: the touchscreen. You have to be able to look at the screen, and have at least one free hand to touch or type. If you're doing anything else - driving, cooking or changing a baby, for example - they're practically useless.</p>
<p class="p3">This limitation leaves us disconnected for big chunks of our day, which means that there is a demand for a screen-less mobile device. .</p>
<p class="p3"><strong style="font-size: 1.385em; line-height: 1.538em;"><em>You Talkin' To Me?</em></strong></p>
<p class="p3">How will we interact with these new devices? By talking to them.&nbsp;With Apple's Siri and Google Voice Actions and Voice Search, early versions of voice-controlled devices are already here. And more sophisticated versions are on the way.&nbsp;Yes, voice input is imperfect, but so was the touchscreen before <a style="line-height: 1.538em;" href="http://www.apple.com/" target="_blank">Apple</a> perfected it for the iPhone.&nbsp;</p>
<p class="p3">But it's not just about voice commands. A truly voice-activated device would listen to you 24/7. A phrase like, "I wonder . . .?" or, "Who was . . ?" spurs it to action: with blinding speed it searches the Web or your personal database to find the answer - and whispers it in your ear.</p>
<p class="p3">Imagine that your mobile device is proactive. It reminds you to grab an umbrella on a rainy day, or lets you know that a friend is at a nearby cafe and would like company. It learns your habits, your likes and dislikes, and becomes acquainted with your friends and family.</p>
<p class="p3">For example, say you favor a certain route to work; your mobile will tell you when there's an accident or construction blocking your way and suggests an alternative. Your best friend's birthday is coming up: your mobile knows that you're both basketball fans. It checks your calendar and that of the home team and finds tickets for an upcoming game.&nbsp;</p>
<p class="p3"><strong style="font-size: 1.385em; line-height: 1.538em;"><em>Be Prepared</em></strong></p>
<p class="p2">In this new world, designing a compelling mobile app just got a lot more interesting.&nbsp;Make a good smartphone app has never been easy. Now, remove the screen and try it again. Sounds impossible. But there are things developers can do to prepare for the next revolution.</p>
<p class="p4"><strong style="line-height: 1.538em;">1. Create Smart Content.</strong>You no longer know where your content will end up. Some devices support cascading style sheets (CSS), others don't; some render HTML, others won't. The screen-less mobile device is just on the horizon. This level of diversity requires that content be truly device-independent. Your content management system (CMS) should contain metadata describing the content, be free of display information (RTF, CSS, or HTML) and organized by what the content <em>is</em> (article, blog, or tweet, etc.) rather than its context (pages, screens and windows).</p>
<p class="p3"><strong style="line-height: 1.538em;">2. Build Open APIs.&nbsp;</strong>Content and services should be made available via Application Programming Interfaces. Think of these APIs as your core offering. Other departments in your organization, registered third-party developers and even consumers should have access them without requiring ongoing assistance.&nbsp;</p>
<p class="p4"><strong style="line-height: 1.538em;">3. Start Small.&nbsp;</strong>Smart content and open APIs are both back-end considerations. Once it's time for you to build a front-end, start by designing and building for the most resource-constrained device that exists. It's much easier to scale up from a small mobile experience than it is to shoehorn a big design into a little package.&nbsp;</p>
<p class="p2">When the smartphone market is disrupted by the next revolutionary mobile device, you're don't want to have to start over. The principles outlined above will prepare you in a way that is useful in today's mobile computing environment, and for the inevitable disruption to come.</p>
<p class="p2"><em>Image courtesy of <a href="http://www.shutterstock.com" target="_blank">Shutterstock</a>.</em></p>
<p>&nbsp;</p>
                    ]]></description>
                <link>http://readwrite.com/2013/02/04/screen-less-smartphones-talking-changes-everything</link>
                <guid>http://readwrite.com/2013/02/04/screen-less-smartphones-talking-changes-everything</guid>
                <category>App Development</category>
                <pubDate>Mon, 04 Feb 2013 06:00:00 -0800</pubDate>
                <author>Jonathan Stark</author>
            </item>
            </channel>
</rss>

