<?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>Andi Friedman &#187; wap</title>
	<atom:link href="http://www.andifriedman.com/index.php/tag/wap/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.andifriedman.com</link>
	<description>A work in progress.</description>
	<lastBuildDate>Sun, 18 Jul 2010 18:05:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A comparison of mobile technologies &#8211; Part 2: WAP or mobile web</title>
		<link>http://www.andifriedman.com/index.php/2007/08/a-comparison-of-mobile-technologies-part-2-wap-or-mobile-web/</link>
		<comments>http://www.andifriedman.com/index.php/2007/08/a-comparison-of-mobile-technologies-part-2-wap-or-mobile-web/#comments</comments>
		<pubDate>Sat, 04 Aug 2007 12:39:10 +0000</pubDate>
		<dc:creator>Andi</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[wap]]></category>

		<guid isPermaLink="false">/?p=84</guid>
		<description><![CDATA[WAP stands for Wireless Application Protocol. As the definition states, WAP is in fact a protocol or standard which has many different facets to it. The most common use of the protocol is in the production of &#8220;WAP sites&#8221; or mobile websites. Traditionally, WAP sites were created using a language called WML (Wireless Markup Language) [...]]]></description>
			<content:encoded><![CDATA[<p><strong>WAP</strong> stands for <strong>Wireless Application Protocol</strong>. As the definition states, WAP is in fact a protocol or standard which has many different facets to it. The most common use of the protocol is in the production of &#8220;WAP sites&#8221; or mobile websites. Traditionally, WAP sites were created using a language called WML (Wireless Markup Language) which allowed sites to be created which were almost a collection of &#8220;cards&#8221; which the user navigated between. <span id="more-84"></span>Nowadays, most sites use WAP 2.0 which is essentially a light-weight version of XHTML (the markup language of traditional websites).</p>
<p>The use of the mobile web is currently quite limited due to several factors including:</p>
<ul>
<li>Lack of education and understanding of the general public of how to access WAP sites.</li>
<li>Inherent navigational difficulties of mobile browsers (typing in URLs on a phone is quite a tedious process).</li>
<li>Setup requirements for connectivity settings and data services.</li>
</ul>
<p><strong>What are mobile website or WAP sites good for?</strong></p>
<ul>
<li>Providing access to rich media information including text, images, audio and video (via download).</li>
<li>Downloading content such as images, video and applications.</li>
<li>Capturing structured, formatted information or data which must be validated in some way (examples include a booking, reservation, customer information, order, etc.).</li>
<li>Simple &#8220;conversational&#8221; interactions &#8211; where the state of the interaction must be maintained or where the context is important.</li>
<li>Membership-type requirements and restricting access to information or services via a login system.</li>
</ul>
<p><strong>What are mobile website or WAP sites not good for?</strong></p>
<ul>
<li>Applications for use in areas with limited or unstable connectivity.</li>
<li>Client-side processing (i.e. performing some custom action on the recipient&#8217;s device such as storing or retrieving information).</li>
<li>Highly interactive or &#8220;suspend and resume&#8221; type situations.</li>
<li>Smart client applications where most processing should be offline and only synchronisation performed online.</li>
<li>Interfaces which require any degree of complexity beyond simple images and form elements.</li>
</ul>
<p><strong>What is the extent of device support?</strong></p>
<ul>
<li>Most phones, even those in the lower tier have some level of WAP support.</li>
<li>In South Africa, many of the network operators (as of this blog) do not have data services enabled by default which means some users&#8217; phones may not be set up to access WAP.</li>
<li>This situation is changing quite rapidly however.</li>
</ul>
<p><strong>Example application</strong></p>
<p>The <a title="Website will open in a new window" href="http://www.qpid.co.za/" target="_blank">Qpid</a> service has a mobile website which provides access to frequently asked questions, privacy concerns and other information which allows users to learn about the system without needing to find a PC. You can access the site from your mobile phone by navigating to http://m.qpid.co.za.</p>
<p>The Qpid WAP site is very simple. We developed a more advanced mobile website for one of our clients which allows call centre agents to produce deals for customers from a web interface and send a WAP push (link to the WAP site) which contains the specific deal information (product photo, pricing, etc) &#8211; all whilst on the phone to the customer.</p>
<p>This post forms part of a series on a <a title="Return to comparison of mobile technologies" href="http://www.clyral.com/za/blogentries/view/17/a-comparison-of-mobile-technologies.html">comparison of mobile technologies</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.andifriedman.com/index.php/2007/08/a-comparison-of-mobile-technologies-part-2-wap-or-mobile-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
