<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Codrops &#187; webapp</title>
	<atom:link href="http://tympanus.net/codrops/tag/webapp/feed/" rel="self" type="application/rss+xml" />
	<link>http://tympanus.net/codrops</link>
	<description>Useful resources and inspiration for creative minds</description>
	<lastBuildDate>Wed, 23 May 2012 09:46:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Fingers are Bigger than Mice &#8211; Design Concepts for Mobile Websites</title>
		<link>http://tympanus.net/codrops/2011/01/20/design-concepts-for-mobile-websites/</link>
		<comments>http://tympanus.net/codrops/2011/01/20/design-concepts-for-mobile-websites/#comments</comments>
		<pubDate>Thu, 20 Jan 2011 11:30:35 +0000</pubDate>
		<dc:creator>Patrick Cox</dc:creator>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[webapp]]></category>
		<category><![CDATA[website]]></category>

		<guid isPermaLink="false">http://tympanus.net/codrops/?p=3685</guid>
		<description><![CDATA[With smartphone subscriptions projected to climb above 50% of the market by the end of 2011, designing for mobile browsers and touch devices is now reaching critical mass. The days of only designing for desktop and laptop displays are long gone. Mobile devices, from phones to tablets, are taking over the market place and are [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-3716" title="FingersAreBiggerThanMice" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/FingersAreBiggerThanMice.jpg" alt="" width="580" height="315" /></p>
<p>With smartphone subscriptions projected to climb above 50% of the  market by the end of 2011, <em><strong>designing for mobile browsers</strong></em> and touch  devices is now reaching critical mass. The days of only designing for  desktop and laptop displays are long gone.</p>
<p>Mobile devices, from phones to tablets, are taking over the market  place and are <strong>growing in popularity</strong>. In 2011, tablet sales are projected  to overtake PC sales and smartphones sales will crush feature phones  sales. In addition, users still largely prefer using the mobile browser  on their devices more than native apps that have to be downloaded and/or  purchased.</p>
<p><strong><em>What does this mean?</em></strong> Its a great time to be a web designer&#8230; as long as you can keep up with the mobile browser trends.</p>
<p>I&#8217;ve compiled a little top ten list of design concepts and examples  that we should all be considering as we start to design websites in the  mobile space. Screen shots provided by the truly awesome, <a href="http://www.mobileawesomeness.com/">MobileAwesomeness.com</a>.</p>
<h3>1 &#8211; Use Semantic Markup</h3>
<p>We all know that we should separate content from presentation, but in  mobile web design we should consider going deeper. Semantic markup  should be used to <strong>properly convey meaning</strong> to the markup without any  extra presentation components like CSS or JS. Semantic markup creates a  better division of style vs content, provides better accessibility, less  code (smaller file sizes) and also allows any device to interpret your  website&#8217;s information better.</p>
<p>Plus, if a device&#8217;s browser turns off images, javascript or external  style sheets, the meaning of your website will still be clearly  presented to the user.</p>
<p>Here&#8217;s a couple of tips to get you started:</p>
<ul>
<li>Remove unnecessary images from your HTML code. Images reinforce  meaning, but are not themselves meaningful. Present images using the CSS  background properties or other methods.</li>
<li>Use tags that represent the meaning of the content, only use tags  that apply to the content itself. Examples: Use &lt;em&gt; for extra  emphasis and &lt;abbr&gt; to define an abbreviation. <a href="http://www.webdesignfromscratch.com/html-css/list-of-html-tags-with-semantic-usage/">See http://www.webdesignfromscratch.com/html-css/list-of-html-tags-with-semantic-usage/</a> for a complete list of tags and use cases.</li>
<li>Only use &lt;div&gt; to define large portions of content that are  directly related to each other. In other words, don&#8217;t be DIV happy! Use  &lt;ul&gt; for a list and use &lt;span&gt; for a smaller portion of  content.</li>
<li>Remember, semantic web is about meaning, not style.</li>
</ul>
<div id="bsap_1266918" class="bsarocks bsap_af25dfd2f1908889af7a1aa5f4dcbd9e"></div><div style="clear:both;"></div>
<h3>2 &#8211; Clearly Define Your Message</h3>
<p>Focus your mobile website on fewer tasks, tasks that directly  reinforce the main goals of your site. Since you have <strong>80% less room</strong>,  this means you have 80% less space for performing tasks. Mobile users  will not physically be able to access or perform a lot of tasks from one  page.</p>
<p>For example, on a large display it may be easy for your users to view  your latest products, check their shopping cart, fill out a simple  contact form, check the latest RSS entries and view your last six  tweets. But on a small mobile display they will not be able to do all of  this unless you shrink everything down so small they will need to pull  out their reading glasses just to view your site. Limited screen size  doesn&#8217;t mean you have to remove features, but you&#8217;ll need to simplify  what features and how many features you can contain on one view.</p>
<p>Instead of thinking about your mobile website in &#8216;pages&#8217;, <strong>think of it  in terms of &#8216;views&#8217;</strong> where each view may only contain one to three  tasks, goals or elements. Simplifying the users&#8217; view will not only  allow you to create a better mobile experience, but it may also help you  to define or realize the important goals of your website in general,  and that ain&#8217;t a bad thing.</p>
<p><img class="aligncenter size-large wp-image-3686" title="Screen shot 2011-01-18 at 7.49.11 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.49.11-AM-585x371.png" alt="" width="585" height="371" /></p>
<h3>3 &#8211; No Fluff</h3>
<p>Don&#8217;t use fluff to fill the extra spaces, there is no extra space on a  mobile device. Mobile devices have varying bandwidths and speeds, so be  cautious of the size of your site. Extra images, text, code and extra  junk not only clutter the display but they also increase load times.</p>
<p><strong>Load time is critical</strong> to mobile devices because users are generally  not sitting in front of their computers when viewing your mobile  version. Here&#8217;s a quick (and pretty lame) illustration; A user of a  bank&#8217;s mobile site may be waiting in line at Target and need to transfer  money from saving to checking in order to cover their purchase. They&#8217;re  not gonna want to wait very long for the banks&#8217; pretty branch images to  pop up.</p>
<ul>
<li>Don&#8217;t use unnecessary images and optimize the ones you will use.</li>
<li>Get rid of those long filler marketing paragraphs and bullet lists.</li>
<li>Reduce code bloat by using semantic markup and minimize style sheets and attachments.</li>
</ul>
<p><img class="aligncenter size-large wp-image-3687" title="Screen shot 2011-01-18 at 7.53.12 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.53.12-AM-585x372.png" alt="" width="585" height="372" /></p>
<h3>4 &#8211; Remember, No Hover State</h3>
<p>Mobile touch devices don&#8217;t have hover states, so don&#8217;t try to use  them. Design becomes more critical on mobile devices because you don&#8217;t  have a mouse to wave around exploring the page hunting for hover states  to indicate actions. <strong>You&#8217;ll need to be more creative</strong>, you&#8217;ll need to  visually indicate to the user that a particular element can be pushed or  pulled or manipulated in some way.</p>
<ul>
<li>Use buttons to indicate links, not underlined text.</li>
<li>Arrows on buttons and list items indicate a more details view.</li>
<li>Create textures such as gradient and/or beveled lines or dot grids to indicate pulls or other gestures.</li>
<li>Use CLEAR and FAMILIAR icons. Don&#8217;t make up new icons for standard actions like &#8216;add&#8217;, &#8216;edit&#8217;, or &#8216;back&#8217;.</li>
</ul>
<p>Some sites have tried to re-create a hover state where the user rests  their finger on an element or even touches it once. But when you design  for mobile, lose the hover crutch altogether. <strong>Don&#8217;t design work  arounds</strong>, just design your site to clearly indicate that something should  be clicked or swiped or pushed or moved&#8230; with so many gestures, don&#8217;t  hack an old browser method for use in a new technology.</p>
<p><img class="aligncenter size-large wp-image-3688" title="Screen shot 2011-01-18 at 7.59.26 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.59.26-AM-585x371.png" alt="" width="585" height="371" /></p>
<h3>5 &#8211; Large, Simple, Clear Typography</h3>
<p>If you don&#8217;t want your users to squint and get headaches when they  use your site, use larger type. Your &#8216;standard&#8217; or comfortable paragraph  type on a large display is around 14px, but on a mobile phone the  comfortable reading type for users is twice that. But large type on a  small screen means <strong>less room for information</strong> (which is always better for  the user).</p>
<ul>
<li>Remove non-relevant information and text from your mobile site.</li>
<li>Clearly define text, use simple terms and phrases.</li>
<li>Avoid a lot of line breaks in a sentence or small paragraph, reword you sentence if needed.</li>
<li>Consider using a &#8216;More Info&#8217; button that take the user to a new view that only contains more information.</li>
</ul>
<p><img class="aligncenter size-large wp-image-3689" title="Screen shot 2011-01-18 at 8.02.07 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-8.02.07-AM-585x746.png" alt="" width="585" height="746" /></p>
<h3>6 &#8211; Content Can Be Navigation</h3>
<p>One of the coolest things about touch devices is that content is  navigation. <strong>The user can directly interact with the screen</strong>, they don&#8217;t  need any other tools but their fingers. Anything on the screen can be  touched, pushed or moved, there is no need to use scroll bars to  indicate vertical or horizontal movement because the screen already  provides it. A simple list view can be used to convey information as  well as link to another view on your site. Think of your mobile site as a  giant (yet small) content gallery and be creative about how the user  moves through that gallery.</p>
<p><img class="aligncenter size-large wp-image-3690" title="Screen shot 2011-01-18 at 7.56.33 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.56.33-AM-585x368.png" alt="" width="585" height="368" /></p>
<h3>7 &#8211; Tame Your Palette</h3>
<p>Mobile phone displays are smaller and brighter than desktop or laptop  displays and people are usually closer to their mobile displays when  viewing them. In order not thoroughly annoy your user,<strong> lower  the color intensity</strong>.</p>
<ul>
<li>Avoid ultra bright neon colors (unless used sparingly as accents).</li>
<li>Avoid excessive use of intense colors or color schemes.</li>
<li>Select a color scheme that is more pleasant to the eye.</li>
<li>Don&#8217;t forget contrast. Color contrast looks great on mobile displays as long as its not overwhelming.</li>
</ul>
<p><img class="aligncenter size-large wp-image-3691" title="Screen shot 2011-01-18 at 7.53.38 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.53.38-AM-585x370.png" alt="" width="585" height="370" /></p>
<h3>8 &#8211; Always Use Clear Form Labels</h3>
<p>Always, always, always use clear and consistent form labels. Don&#8217;t  use obscure labeling conventions for inputs. <strong>Use the standard verbiage</strong> we all know and love, like User Name and Password, don&#8217;t use cutesy made  up labels like Nickname and Secret Code, unless you&#8217;re some ultra hip  web community where these are common terms already.</p>
<p>Another thing to consider using is pre-filled input elements where  the label is located inside the input itself. This does three great  things for you mobile web site; it clearly defines the form element,  dynamically indicates whether the field has been completed or not, and  reduces space on the screen.</p>
<p><img class="aligncenter size-large wp-image-3692" title="Screen shot 2011-01-18 at 7.58.37 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.58.37-AM-585x371.png" alt="" width="585" height="371" /></p>
<h3>9 &#8211; Provide Feedback</h3>
<p><strong>Mobile browsers aren&#8217;t static browsers</strong>. Remember to provide dynamic  feedback to your user. Mobile device browsers can run javascript just  like web browsers so why not provide your users with some instant  gratification. When a page is loading, show then it is loading with a  pretty animated swirly thing or a hansom progress bar. While a user is  filling our a form, let them know if they miss a required entry. After  they submit a form, pop a dialog box that says thanks and let them know  what&#8217;s gonna happen next.</p>
<ul>
<li>When a user touches something, change its visual state to indicate an action.</li>
<li>Use JS animation libraries like Jquery or Scriptaclulous to create dynamic feedback.</li>
<li>Show load animations on images that are still being processed. Don&#8217;t  just have blank spaces where images are waiting to be loaded.</li>
</ul>
<h3>10 &#8211; WHITE SPACE</h3>
<p>Most mobile devices are touch screens and fingers are bigger than  mice, so leave some space. Mobile devices do not have pixel perfect  interfaces so design your site with <strong>plenty of white space</strong>. Make sure  your &#8216;touchable&#8217; elements have plenty of room around them to be clicked  my a large finger, you don&#8217;t want you user aiming for one link and  hitting another.</p>
<ul>
<li>Use buttons, badges or icons for links instead of text links.</li>
<li>Add plenty of padding between content blocks to create clearly defined areas.</li>
<li>Larger line heights make text easier to read on smaller displays.</li>
</ul>
<p><img class="aligncenter size-large wp-image-3693" title="Screen shot 2011-01-18 at 7.55.01 AM" src="http://tympanus.net/codrops/wp-content/uploads/2011/01/Screen-shot-2011-01-18-at-7.55.01-AM-585x369.png" alt="" width="585" height="369" /></p>
<h3>More Information</h3>
<p>For more information on the best practices for <strong>implementing mobile  style  sheets or using mobile domain re-directs</strong>, check out these awesome   articles:</p>
<p><a href="http://www.alistapart.com/articles/return-of-the-mobile-stylesheet/">Return of the Mobile Stylesheet &#8211; A List Apart</a></p>
<p><a href="http://davidbcalhoun.com/2010/using-mobile-specific-html-css-javascript">Mobile Specific &#8211; David B Calhoun</a></p>
<p><a href="http://www.smashingmagazine.com/2009/01/13/mobile-web-design-trends-2009/">How to Build a Mobile Website &#8211; Smashing Magazine</a></p>
<p><a href="http://www.dailyblogtips.com/10-mobile-plugins-for-wordpress/">10 Mobile WordPress Plugins &#8211; Daily Blog Tips</a></p>
<p>References:</p>
<p><a href="http://www.lukew.com/ff/entry.asp?1258">Device Classes and Responsive Design &#8211; Luke W</a></p>
<p><a href="http://www.mobileawesomeness.com/">Mobile Awesomeness</a></p>
<p><a href="http://www.marketingcharts.com/interactive/smartphones-projected-to-overtake-feature-phones-next-year-12418/">Smartphones projected to overtake feature phones next year </a></p>
<p><a href="http://www.webpagefx.com/design-build-mobile-web-site.html">How to Design and Build a Mobile Website</a></p>
<p><a href="http://www.noupe.com/how-tos/mobile-web-design-tips-and-best-practices.html">Mobile Web Design: Tips and Best Practices</a></p>
<div class="googlead"><!-- wp_ad_camp_1 --></div>
]]></content:encoded>
			<wfw:commentRss>http://tympanus.net/codrops/2011/01/20/design-concepts-for-mobile-websites/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>JavaScript: Changing location or stylesheet according to device or browser</title>
		<link>http://tympanus.net/codrops/2009/08/26/javascript-changing-location-or-stylesheet-according-to-device-or-browser/</link>
		<comments>http://tympanus.net/codrops/2009/08/26/javascript-changing-location-or-stylesheet-according-to-device-or-browser/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 12:58:13 +0000</pubDate>
		<dc:creator>Mary Lou</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[iPhone Webapp]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[webapp]]></category>

		<guid isPermaLink="false">http://tympanus.net/bringiton/?p=17</guid>
		<description><![CDATA[Developing web applications for mobile phones sometimes brings the need to just create separate content for different devices.

Some time ago I had to create a web app that would look pretty on both, the iPhone and some Windows Mobile based device by HTC! In the end it came out to be simpler just to create another page for the WM device.

Here is a code snippet that I inserted in the header of the index page of the web app:]]></description>
			<content:encoded><![CDATA[<p>Developing web applications for mobile phones sometimes brings the need to just create separate content for different devices.</p>
<p>Some time ago I had to create a web app that would look pretty on both, the iPhone and some Windows Mobile based device by HTC! In the end it came out to be simpler just to create another page for the WM device.</p>
<p>Here is a code snippet that I inserted in the header of the index page of the web app:</p>
<p><span id="more-17"></span></p>
<pre class="brush: js">&lt;script type="text/javascript"&gt; 

 function browser(){
  var browser = navigator.userAgent;
  //alert(browser);

  //Windows Mobile
  if (browser.match("MDA_compact")|| browser.match("MSIE")) {
    window.location.href = "mda/index.html";
  }
 //iPhone &amp; Rest
  else{
   document.write('&lt;meta name="apple-mobile-web-app-capable" content="yes" /&gt;'
   +'&lt;link rel="apple-touch-icon" href="webapplogo.gif"/&gt;'    
   +'&lt;meta name="apple-mobile-web-app-status-bar-style" content="black" /&gt;'
   +'&lt;meta content="text/html; charset=utf-8" http-equiv="Content-Type" /&gt;'
   +'&lt;meta content="minimum-scale=1.0, width=device-width, maximum-scale=0.6667, user-scalable=no" name="viewport" /&gt;'
   +'&lt;link href="style.css" rel="stylesheet" type="text/css" /&gt;'
   +'&lt;link href="pie.css" rel="stylesheet" type="text/css" /&gt;'
   +'&lt;link href="chart.css" rel="stylesheet" type="text/css" /&gt;'
   +'&lt;link href="messages.css" rel="stylesheet" type="text/css" /&gt;'
   +'&lt;link href="news.css" rel="stylesheet" type="text/css" /&gt;'
   +'&lt;link rel="stylesheet" href="stylesheets/glider.css" type="text/css" media="screen" charset="utf-8"&gt;');   
   }
  }

 browser();

&lt;/script&gt;</pre>
<p>You might want to figure out first, how the target device/browser is called. Uncomment the <span style="color: #008000;">alert(browser)</span> line and get the name. Adapt the <span style="color: #008000;">browser.match(&#8220;Target_browser&#8221;)</span> and define what you want to do in that case, e.g. redirect to another page.</p>
<p><div id="bsap_1266918" class="bsarocks bsap_af25dfd2f1908889af7a1aa5f4dcbd9e"></div><div style="clear:both;"></div><br />
<br/><br/><br/></p>
]]></content:encoded>
			<wfw:commentRss>http://tympanus.net/codrops/2009/08/26/javascript-changing-location-or-stylesheet-according-to-device-or-browser/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  tympanus.net/codrops/tag/webapp/feed/ ) in 0.21009 seconds, on May 24th, 2012 at 12:48 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 24th, 2012 at 1:48 am UTC -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- Quick Cache Is Fully Functional :-) ... A Quick Cache file was just served for (  tympanus.net/codrops/tag/webapp/feed/ ) in 0.02419 seconds, on May 24th, 2012 at 1:35 am UTC. -->
