<?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>Locatrix &#187; Innovation</title>
	<atom:link href="http://locatrix.com/tag/innovation/feed" rel="self" type="application/rss+xml" />
	<link>http://locatrix.com</link>
	<description>Accelerating mobile innovation.</description>
	<lastBuildDate>Thu, 05 Apr 2012 06:36:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Behind The Scenes: Salamander</title>
		<link>http://locatrix.com/blog/behind-the-scenes-salamander</link>
		<comments>http://locatrix.com/blog/behind-the-scenes-salamander#comments</comments>
		<pubDate>Thu, 23 Apr 2009 04:16:42 +0000</pubDate>
		<dc:creator>Sam Collins</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[Mobile Devices]]></category>
		<category><![CDATA[mobile]]></category>
		<guid isPermaLink="false">http://locatrix.com/?p=719</guid>
		<description><![CDATA[Most developers writing web applications for mobile devices decide to: Develop for the most common devices. Develop so that it looks “kinda ok” on most devices. Use hacks to get it to work on a couple of other devices. Somehow &#8230; <a href="http://locatrix.com/blog/behind-the-scenes-salamander" class="morelink">Read more</a>]]></description>
			<content:encoded><![CDATA[<p>Most developers writing web applications for mobile devices decide to:</p>
<ul>
<li>Develop for the most common devices.</li>
<li>Develop so that it looks “kinda ok” on most devices.</li>
<li>Use hacks to get it to work on a couple of other devices.</li>
<li>Somehow use the <a title="WURFL" href="http://wurfl.sourceforge.net/">WURFL database</a>.</li>
</ul>
<p>Several of our <a title="Locatrix Communications - Solutions" href="http://locatrix.com/solutions/">solutions</a> revolve around displaying maps. We want the maps to fit to the width of each device. We also like to know what an acceptable base font size is. We want to know as much as we can about every device, so that our <a title="Locatrix Communications - Solutions" href="http://locatrix.com/solutions/">solutions</a> work perfectly regardless of device. We run Salamander behind every major (and minor!) <a title="Locatrix Communications - Solutions" href="http://locatrix.com/solutions/">solution</a> we develop here at <a title="Locatrix Communications" href="http://locatrix.com/">Locatrix Communications</a> to solve this.</p>
<p><a href="http://locatrix.com/labs/salamander">Salamander</a> lets developers write layout code for <strong>all devices at once.</strong> By allowing <strong>any service</strong> to get <strong>any attributes</strong> about <strong>any device</strong>. Mobile applications no longer have to look “kinda ok” on some devices. Applications become tailored to each device. For example:</p>
<ul>
<li>Display size</li>
<li>Supported WAP version</li>
<li>Supported Java version</li>
<li>Official support by an MNO</li>
<li>Default font size.</li>
</ul>
<p>The web-based front end of Salamander also allows us to instantly change and/or rollback changes on any device-specific attributes across all our <a title="Locatrix Communications - Solutions" href="http://locatrix.com/solutions/">solutions</a>. Additionally, it automagically pulls community updates from the <a title="WURFL" href="http://wurfl.sourceforge.net/">WURFL database</a>.</p>
<p>To call Salamander, we simply create a new Salamander object and then query the attributes we need.</p>
<pre style="font-size:9pt"><code>if (!isset($_SESSION['device'])
{
    require_once('/include/Salamander.class.php');
    $salamander = new Salamander("http://salamander.me");
    $_SESSION['device'] = $salamander-&gt;getSalamanderDevice($_SERVER["HTTP_USER_AGENT"]);
}
</code></pre>
<p>The Salamander class handles all the communications with the Salamander server. It returns an array of various required attributes for applications to query.</p>
<p>We then query attributes such as:</p>
<ul>
<li>$_SESSION['device']['baseFontSize']</li>
<li>$_SESSION['device']['imageType']</li>
<li>$_SESSION['device']['imageWidth']</li>
<li>$_SESSION['device']['imageHeight']</li>
<li>$_SESSION['device']['is3G']</li>
</ul>
<p>From there we resize images, set font sizes, enable/disable bandwidth intensive features, etc.</p>
<p>Want to try out Salamander with your applications? Want to send feedback? <a title="Sam Collins" href="mailto:sam@locatrix.com">Send me an email!</a></p>
]]></content:encoded>
			<wfw:commentRss>http://locatrix.com/blog/behind-the-scenes-salamander/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile Innovation: an Operator&#039;s Roadmap</title>
		<link>http://locatrix.com/blog/mobile-innovation-an-operators-roadmap</link>
		<comments>http://locatrix.com/blog/mobile-innovation-an-operators-roadmap#comments</comments>
		<pubDate>Wed, 08 Apr 2009 05:40:06 +0000</pubDate>
		<dc:creator>Mark White</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[LBS]]></category>
		<category><![CDATA[VAS]]></category>
		<guid isPermaLink="false">http://locatrix.com/?p=695</guid>
		<description><![CDATA[Robert Clark wrote a great opinion piece in last month&#8217;s Telecom Asia magazine, entitled &#8220;Mobile&#8217;s over-confidence problem&#8221;.  In it, he suggests that operators are currently doing okay &#8211; not great, but okay &#8211; leveraging the rise of mobile broadband, but &#8230; <a href="http://locatrix.com/blog/mobile-innovation-an-operators-roadmap" class="morelink">Read more</a>]]></description>
			<content:encoded><![CDATA[<p>Robert Clark wrote a <a href="http://www.telecomasia.net/article.php?id_article=12819" target="_blank">great opinion piece</a> in last month&#8217;s <a href="http://telecomasia.net" target="_blank">Telecom Asia</a> magazine, entitled &#8220;Mobile&#8217;s over-confidence problem&#8221;.  In it, he suggests that operators are currently doing okay &#8211; not great, but okay &#8211; leveraging the rise of mobile broadband, but are falling behind in the innovation game that will drive their future.</p>
<p>Clark&#8217;s argument is that the mobile and mobile Internet players &#8211; Google, Yahoo!, Microsoft, Nokia and particularly Apple &#8211; are the ones driving innovation in the industry, so any confidence derived by mobile network operators from their current position is dangerously optimistic.  As an example, Clark cites that any satisfaction operators derive from growth in mobile data use needs to be tempered by the knowledge that this growth largely results from devices like the iPhone, plus the applications and content they consume.   From which, ultimately, the operator receives nothing other than ever-commoditised data revenues. Ultimately, Clark sees this as a cultural problem:</p>
<blockquote><p>&#8220;Carrier leaders need to recognize that the industry culture has evolved to deliver scale and reliability. Even among young and small cellcos, it isn&#8217;t geared to innovation.&#8221;</p></blockquote>
<p>One of the challenges generally faced by &#8220;innovation units&#8221; within mobile operators &#8211; those teams chartered with driving application and services growth &#8211; is getting beyond corporate risk aversion. In the Internet world, companies can try, test, and measure new services and features easily, quickly and cheaply &#8211; Google&#8217;s &#8220;Lab&#8221; products are great examples of this.  In the mobile world, service offerings and VAS business cases face reviews by multiple committees, take months to deploy and often get launched as overly-sanitised versions of a once-original idea.  In a way, any service &#8220;innovation&#8221; gets watered down by internal processes.  Which is fine, if you are launching or upgrading multi-billion dollar network infrastructure.  But not if you just want to see if an idea works.</p>
<p>This month we&#8217;ve launched a new section on our web site: <a href="http://locatrix.com/labs">Locatrix Labs</a>.  In it, we&#8217;re profiling in real-time projects and works-in-progress from the Locatrix engineering team, ably led by Andrew Eross and Johnson Page.  Of course the innovations featured all leverage or extend <a href="http://locatrix.com/solutions/xlf">Locatrix/XLF</a>, our VAS applications framework, which is exactly the point: we can provide mobile solution product managers a &#8220;safe&#8221; &#8211; in terms of both cost/capital expenditure and deployment risk- means to define, test-launch and measure new service ideas, and indeed mashups between services: perhaps <a href="http://locatrix.com/solutions/uandme">Uandme</a> supported by <a href="http://locatrix.com/solutions/mobile-marketing">mobile advertising</a> (we know one operator already is already considering this), or our entertainment/engagement application <a href="http://locatrix.com/labs/nine">Nine </a>with <a href="http://locatrix.com/solutions/social-networking">branded Facebook marketing</a>.</p>
<p>By showcasing the Labs solutions we hope to provide our customers and partners a view of what cellco service innovation could look like, in an environment which allows them to (as Clark suggests):</p>
<blockquote><p>&#8220;&#8230;marshall their strengths in network reach and enabling systems, and be the best channel partner for the broadband mobile internet.&#8221;</p></blockquote>
<p>Which is precisely where they need to innovate!</p>
<p>Please check out <a href="http://locatrix.com/labs">Locatrix Labs</a> and <a href="http://locatrix.com/about/contact">let us know what you think</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://locatrix.com/blog/mobile-innovation-an-operators-roadmap/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

