<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-6507272122237969080</atom:id><lastBuildDate>Thu, 21 Jan 2010 22:45:35 +0000</lastBuildDate><title>Ondeego Blog</title><description>Official Blog of Ondeego Inc, a Berkeley Mobile 2.0 startup.</description><link>http://ondeego.com/blogger/</link><managingEditor>noreply@blogger.com (Kenan Wang)</managingEditor><generator>Blogger</generator><openSearch:totalResults>16</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-1401904135691491625</guid><pubDate>Thu, 21 Jan 2010 22:39:00 +0000</pubDate><atom:updated>2010-01-21T14:45:35.367-08:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>android</category><category domain='http://www.blogger.com/atom/ns#'>procurement</category><category domain='http://www.blogger.com/atom/ns#'>mobile enterprise</category><title>Three Ways the Nexus One Will Change Enterprise Mobility</title><description>This month Google began selling the Nexus One.  While a new Android phone with a beautiful OLED screen and 1 ghz+ chipset is certainly exciting, the Nexus One will bring about some changes in how we deal with smartphones in the enterprise.&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;1. The Way We Buy Phones Will Change&lt;br /&gt;&lt;/span&gt;Traditionally, mobile phones have been sold through carrier-branded stores (in the United States), and sold into enterprises by either a) OEM sales teams (from RIM or Apple, for example), or b) came with you carrier contract. Google's decision to sell the Nexus One is a bold new decision.  &lt;br /&gt;Carriers are getting further decoupled from value chain, and are acting more as a utility provider than a channel/customer-owner.  Expect telecom carriers as a whole to become more like ISPs over the next 5 years, and less like the phone companies they are today.&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;2. Google and Microsoft Compete for the Enterprise&lt;br /&gt;&lt;/span&gt;Windows Mobile has done reasonably well in the enterprise.  At last tally, there's something like 10 million Windows Mobile Phones in the US, mostly in the enterprise.  Windows Mobile has made its way in the enterprise by natively integrating with Microsoft Exchange and other Microsoft products (ActiveDirectory, Office, System Center, etc) that are omnipresent.&lt;br /&gt;Between Android and Google's substantial affront to Microsoft's Exchange business with Google Apps, expect Google to move beyond the consumer market and into the enterprise, challenging Microsoft on their home turf.  While predicting who will win is fully beyond me, when great companies compete, even better products emerge.  Google will be challenged to deliver more whole products, while Microsoft will be challenged around usability and competing with Google's incredibly low prices.  &lt;br /&gt;&lt;span style="font-weight:bold;"&gt;3. IT Consumerizes Even Further&lt;br /&gt;&lt;/span&gt;The Consumerization of IT is one of our favorite causes here at Ondeego, and the Nexus One further moves the enterprise in that direction.  Back in 2005, Gartner said that the Consumerization of IT will be the &lt;a href="http://www.gartner.com/press_releases/asset_138285_11.html"&gt;largest trend of the next decade&lt;/a&gt;.  &lt;br /&gt;Now, end users have incredibly cheap access to great technology.  They take this technology and bring it into the enterprise - like BlackBerries, salesforce.com, and now iPhones - and then this great new tool rapidly becomes a management nightmare.  The IT tools of the future will be end-user accessible and IT manageable.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-1401904135691491625?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2010/01/three-ways-nexus-one-will-change.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-4526163041228727204</guid><pubDate>Wed, 21 Oct 2009 05:14:00 +0000</pubDate><atom:updated>2010-01-15T10:23:59.097-08:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>gartner</category><category domain='http://www.blogger.com/atom/ns#'>appcentral</category><category domain='http://www.blogger.com/atom/ns#'>CIO</category><category domain='http://www.blogger.com/atom/ns#'>mobile enterprise</category><title>Gartner Names Mobile Applications a 'Strategic Technology for 2010'</title><description>&lt;link rel="File-List" href="file:///C:%5CUsers%5CLEADPR%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CUsers%5CLEADPR%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CLEADPR%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Cambria; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073741899 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} span.apple-style-span 	{mso-style-name:apple-style-span; 	mso-style-unhide:no;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} &lt;/style&gt; &lt;![endif]--&gt;  &lt;p class="MsoNormal"  style="font-family:trebuchet ms;"&gt;&lt;span style="font-size:100%;"&gt;&lt;span class="apple-style-span"&gt;&lt;span style="line-height: 115%;font-size:10pt;color:black;"  &gt;Yesterday, Gartner named Mobile Applications one of the &lt;a href="http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&amp;amp;newsId=20091020006104&amp;amp;newsLang=en"&gt;'Top Ten Strategic Technologies'&lt;/a&gt; for 2010. Other technologies named for their disruptive and strategic implications include cloud computing, client computing (virtualization), and social computing.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal"  style="font-family:trebuchet ms;"&gt;&lt;span style="font-size:100%;"&gt;&lt;span class="apple-style-span"&gt;&lt;span style="line-height: 115%;font-size:10pt;color:black;"  &gt;We at Ondeego have thought mobile applications are strategic technologies for quite a while.&lt;span style=""&gt;  &lt;/span&gt;Everyone with a BlackBerry, iPhone, or other smartphone now understands the benefits delivered by mobile email.&lt;span style=""&gt;  &lt;/span&gt;Now, finally, other mobile enterprise applications are getting the respect they deserve.  Particularly when combined with other innovations, like cloud services, social computing, and advanced analytics, mobile applications can be truly disruptive, lowering costs, and driving competitive advantage.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;span style=";font-family:trebuchet ms;font-size:100%;"  &gt;&lt;span class="apple-style-span"&gt;&lt;span style="line-height: 115%;font-size:10pt;color:black;"  &gt;What Gartner doesn't mention: With mobile enterprise applications, it is important to remember that a complete strategy is needed - not just a single tactical mobile application.&lt;span style=""&gt;  &lt;/span&gt;These applications have other management questions - what happens when someone loses a phone?&lt;span style=""&gt;  &lt;/span&gt;What happens when an employee leaves a company or transfers workgroups?&lt;span style=""&gt;  &lt;/span&gt;Most importantly, how do you provision these applications onto (potentially) hundreds or thousands of isolated devices?&lt;span style=""&gt;  &lt;/span&gt;&lt;span style=""&gt;  &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=""&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-4526163041228727204?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/10/gartner-names-mobile-applications.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-3908748952403717406</guid><pubDate>Mon, 19 Oct 2009 22:49:00 +0000</pubDate><atom:updated>2010-01-15T10:27:14.670-08:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>appcentral</category><category domain='http://www.blogger.com/atom/ns#'>awards</category><category domain='http://www.blogger.com/atom/ns#'>investors</category><title>Ondeego Selected to Present at MobiTechFest Americas!</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://ondeego.com/blogger/uploaded_images/MTF_2009_Finalist-748760.gif"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 180px; height: 100px;" src="http://ondeego.com/blogger/uploaded_images/MTF_2009_Finalist-748758.gif" alt="" border="0" /&gt;&lt;/a&gt;&lt;meta equiv="Content-Type" content="text/html; charset=utf-8"&gt;&lt;meta name="ProgId" content="Word.Document"&gt;&lt;meta name="Generator" content="Microsoft Word 12"&gt;&lt;meta name="Originator" content="Microsoft Word 12"&gt;&lt;link rel="File-List" href="file:///C:%5CUsers%5CLEADPR%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"&gt;&lt;link rel="themeData" href="file:///C:%5CUsers%5CLEADPR%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"&gt;&lt;link rel="colorSchemeMapping" href="file:///C:%5CUsers%5CLEADPR%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:worddocument&gt;   &lt;w:view&gt;Normal&lt;/w:View&gt;   &lt;w:zoom&gt;0&lt;/w:Zoom&gt;   &lt;w:trackmoves/&gt;   &lt;w:trackformatting/&gt;   &lt;w:punctuationkerning/&gt;   &lt;w:validateagainstschemas/&gt;   &lt;w:saveifxmlinvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;   &lt;w:ignoremixedcontent&gt;false&lt;/w:IgnoreMixedContent&gt;   &lt;w:alwaysshowplaceholdertext&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;   &lt;w:donotpromoteqf/&gt;   &lt;w:lidthemeother&gt;EN-US&lt;/w:LidThemeOther&gt;   &lt;w:lidthemeasian&gt;X-NONE&lt;/w:LidThemeAsian&gt;   &lt;w:lidthemecomplexscript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;   &lt;w:compatibility&gt;    &lt;w:breakwrappedtables/&gt;    &lt;w:snaptogridincell/&gt;    &lt;w:wraptextwithpunct/&gt;    &lt;w:useasianbreakrules/&gt;    &lt;w:dontgrowautofit/&gt;    &lt;w:splitpgbreakandparamark/&gt;    &lt;w:dontvertaligncellwithsp/&gt;    &lt;w:dontbreakconstrainedforcedtables/&gt;    &lt;w:dontvertalignintxbx/&gt;    &lt;w:word11kerningpairs/&gt;    &lt;w:cachedcolbalance/&gt;   &lt;/w:Compatibility&gt;   &lt;w:browserlevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;   &lt;m:mathpr&gt;    &lt;m:mathfont val="Cambria Math"&gt;    &lt;m:brkbin val="before"&gt;    &lt;m:brkbinsub val="&amp;#45;-"&gt;    &lt;m:smallfrac val="off"&gt;    &lt;m:dispdef/&gt;    &lt;m:lmargin val="0"&gt;    &lt;m:rmargin val="0"&gt;    &lt;m:defjc val="centerGroup"&gt;    &lt;m:wrapindent val="1440"&gt;    &lt;m:intlim val="subSup"&gt;    &lt;m:narylim val="undOvr"&gt;   &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;  &lt;w:latentstyles deflockedstate="false" defunhidewhenused="true" defsemihidden="true" defqformat="false" defpriority="99" latentstylecount="267"&gt;   &lt;w:lsdexception locked="false" priority="0" semihidden="false" unhidewhenused="false" qformat="true" name="Normal"&gt;   &lt;w:lsdexception locked="false" priority="9" semihidden="false" unhidewhenused="false" qformat="true" name="heading 1"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 2"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 3"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 4"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 5"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 6"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 7"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 8"&gt;   &lt;w:lsdexception locked="false" priority="9" qformat="true" name="heading 9"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 1"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 2"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 3"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 4"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 5"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 6"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 7"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 8"&gt;   &lt;w:lsdexception locked="false" priority="39" name="toc 9"&gt;   &lt;w:lsdexception locked="false" priority="35" qformat="true" name="caption"&gt;   &lt;w:lsdexception locked="false" priority="10" semihidden="false" unhidewhenused="false" qformat="true" name="Title"&gt;   &lt;w:lsdexception locked="false" priority="1" name="Default Paragraph Font"&gt;   &lt;w:lsdexception locked="false" priority="11" semihidden="false" unhidewhenused="false" qformat="true" name="Subtitle"&gt;   &lt;w:lsdexception locked="false" priority="22" semihidden="false" unhidewhenused="false" qformat="true" name="Strong"&gt;   &lt;w:lsdexception locked="false" priority="20" semihidden="false" unhidewhenused="false" qformat="true" name="Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="59" semihidden="false" unhidewhenused="false" name="Table Grid"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Placeholder Text"&gt;   &lt;w:lsdexception locked="false" priority="1" semihidden="false" unhidewhenused="false" qformat="true" name="No Spacing"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" unhidewhenused="false" name="Revision"&gt;   &lt;w:lsdexception locked="false" priority="34" semihidden="false" unhidewhenused="false" qformat="true" name="List Paragraph"&gt;   &lt;w:lsdexception locked="false" priority="29" semihidden="false" unhidewhenused="false" qformat="true" name="Quote"&gt;   &lt;w:lsdexception locked="false" priority="30" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Quote"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 1"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 2"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 3"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 4"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 5"&gt;   &lt;w:lsdexception locked="false" priority="60" semihidden="false" unhidewhenused="false" name="Light Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="61" semihidden="false" unhidewhenused="false" name="Light List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="62" semihidden="false" unhidewhenused="false" name="Light Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="63" semihidden="false" unhidewhenused="false" name="Medium Shading 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="64" semihidden="false" unhidewhenused="false" name="Medium Shading 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="65" semihidden="false" unhidewhenused="false" name="Medium List 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="66" semihidden="false" unhidewhenused="false" name="Medium List 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="67" semihidden="false" unhidewhenused="false" name="Medium Grid 1 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="68" semihidden="false" unhidewhenused="false" name="Medium Grid 2 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="69" semihidden="false" unhidewhenused="false" name="Medium Grid 3 Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="70" semihidden="false" unhidewhenused="false" name="Dark List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="71" semihidden="false" unhidewhenused="false" name="Colorful Shading Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="72" semihidden="false" unhidewhenused="false" name="Colorful List Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="73" semihidden="false" unhidewhenused="false" name="Colorful Grid Accent 6"&gt;   &lt;w:lsdexception locked="false" priority="19" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="21" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Emphasis"&gt;   &lt;w:lsdexception locked="false" priority="31" semihidden="false" unhidewhenused="false" qformat="true" name="Subtle Reference"&gt;   &lt;w:lsdexception locked="false" priority="32" semihidden="false" unhidewhenused="false" qformat="true" name="Intense Reference"&gt;   &lt;w:lsdexception locked="false" priority="33" semihidden="false" unhidewhenused="false" qformat="true" name="Book Title"&gt;   &lt;w:lsdexception locked="false" priority="37" name="Bibliography"&gt;   &lt;w:lsdexception locked="false" priority="39" qformat="true" name="TOC Heading"&gt;  &lt;/w:LatentStyles&gt; &lt;/xml&gt;&lt;![endif]--&gt;&lt;style&gt; &lt;!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} .MsoPapDefault 	{mso-style-type:export-only; 	margin-bottom:10.0pt; 	line-height:115%;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --&gt; &lt;/style&gt;&lt;!--[if gte mso 10]&gt; &lt;style&gt;  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} &lt;/style&gt; &lt;![endif]--&gt;  &lt;p class="MsoNormal" style="line-height: normal;"&gt;&lt;span style=" Times New Roman&amp;quot;,&amp;quot;serif&amp;quot;; font-family:&amp;quot;;font-size:12pt;color:black;"&gt;Ondeego is among the 16 companies that have been chosen to present to investors and industry executives at Investorfest Media's MobiTechFest 2009 conference at the Sun Microsystems Conference Center in Santa Clara, CA on October 27.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="line-height: normal;"&gt;&lt;span style=" Times New Roman&amp;quot;,&amp;quot;serif&amp;quot;; font-family:&amp;quot;;font-size:12pt;color:black;"&gt;More than 120 of the mobility industry's top investors, innovators and executives will attend the conference. The event focuses on bringing together professionals from related disciplines to showcase the most promising innovations from the mobile and WiFi communications industry to a group of leading investors, including partners from Storm Ventures, Norwest Venture Partners, and other notable venture firms.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;span style=" line-height: 115%; Times New Roman&amp;quot;,&amp;quot;serif&amp;quot;; font-family:&amp;quot;;font-size:12pt;color:black;"&gt;"We are very impressed with both the number and quality of submissions we received for MobiTechFest Americas. This is a showcase of the latest technology being developed in the mobility industry, and the event is a must-attend for these innovative companies and the top investors in the field," said Investorfest Media founder Gopan Madathil. "We are pleased to select Ondeego from a list of more than 50 companies that submitted to present at this exciting conference."&lt;br /&gt;&lt;br /&gt;For more information, see the &lt;a href="http://www.businesswire.com/portal/site/home/permalink/?ndmViewId=news_view&amp;amp;newsId=20091019006364&amp;amp;newsLang=en"&gt;&lt;span style="color:blue;"&gt;press release&lt;/span&gt;&lt;/a&gt;.&lt;/span&gt;&lt;span style=" line-height: 115%; Times New Roman&amp;quot;,&amp;quot;serif&amp;quot;;font-family:&amp;quot;;font-size:12pt;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-3908748952403717406?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/10/ondeego-selected-to-present-at.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-192292407337246762</guid><pubDate>Tue, 18 Aug 2009 19:16:00 +0000</pubDate><atom:updated>2009-08-18T13:03:21.862-07:00</atom:updated><title>Ondeego at Mobilize09!</title><description>Ondeego will be at &lt;a href="http://events.gigaom.com/mobilize/09/"&gt;Mobilize09&lt;/a&gt;'s LaunchPad Event on September 10th.  We will be launching our new product, AppCentral.  (AppCentral is not on the website yet.  It is in stealth until it launches.)&lt;br /&gt;&lt;br /&gt;Please come out and support us, and please, vote for Ondeego!&lt;br /&gt;&lt;br /&gt;&lt;a href='http://events.gigaom.com/mobilize/09/?a=b_speaker'&gt;&lt;br /&gt; &lt;img src='http://wp.gigaom.com/assets/buttons/mobilize/speaker.gif' alt='See me speak at Mobilize 09 &amp;mdash; San Francisco, September 10' border='0' width='125' height='125' /&gt;&lt;br /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-192292407337246762?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/08/ondeego-at-mobilize09.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-1051065083667287120</guid><pubDate>Thu, 02 Jul 2009 18:48:00 +0000</pubDate><atom:updated>2009-07-02T11:55:28.239-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>mobile customer service</category><category domain='http://www.blogger.com/atom/ns#'>mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>E2C applications</category><category domain='http://www.blogger.com/atom/ns#'>next generation mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>branded mobile applications</category><title>Branded E2C Portals: the Next Phase of Branded Mobile Applications</title><description>&lt;p class="MsoNormal"&gt;Branded mobile applications can be much more than simple games or brand building exercises.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;They can truly be services, driving loyalty, customer service, and revenue.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Because you’re reading this, you probably know that branded mobile applications have exploded as an interactive marketing tool in the last 18 months.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;While this can be primarily attributed to the iPhone and the success brands have had in the App Store (see &lt;a href="http://www.kraftfoods.com/kf/iFood.aspx"&gt;Kraft’s iFood Assistant&lt;/a&gt; and &lt;a href="http://www.textually.org/textually/archives/2009/03/023158.htm"&gt;Zippo’s Zippo Lighter&lt;/a&gt;), other factors, such as the rise of smartphones, the growing prominence of pull marketing, and increasing consumer awareness of mobile internet services have all played a big part in branded apps’ growth.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;However, these entertainment-only mobile applications are only the tip of the iceberg in mobile applications for brands – smartphones are ubiquitous, always carried, internet connected computers, and they can be used for a lot more than just games.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Branded mobile applications can move beyond simple brand-building exercises in the newest of new media into customer experience facilitators, offering services of true utility to the consumer.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;This new breed of mobile applications includes more functionality than the previous generation of branded mobile apps.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;The new breed of mobile apps will be applications that help consumers use products and services.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;For instance, applications from pharmaceutical companies that drive compliance, applications from retailers that function as enhanced loyalty cards, and applications from airlines and travel companies that provide mobile customer service portals.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;These new services will take advantage of the unique features of mobile: personalization, ubiquity, and context-awareness.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Personalization &lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Bill Drummy, CEO of Heartbeat Digital says &lt;a href="http://heartbeatdigital.com/"&gt;here &lt;/a&gt;(it's all Flash but go to "Who We Are") that “there is something inherently more intimate about a digital relationship than any other media.” I agree, and I would add that mobile experiences are inherently more intimate than other digital experiences.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;Mobile is a uniquely personal medium – only one person uses each mobile phone.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;As such, mobile experiences can be uniquely personalized to the user, offering them quick access to the services that interest them the most.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Ubiquity&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;The mobile phone is a modern essential.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;Research firm StudyLogic&lt;span style="mso-spacerun:yes"&gt; &lt;/span&gt;&lt;a href="http://www.prweb.com/releases/2008/09/prweb1330304.htm"&gt;found &lt;/a&gt;84% of professionals check their smartphone before going to sleep and immediately upon waking up.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;The device is so essential, 87% of professionals reported bringing it into the bedroom.&lt;span style="mso-spacerun:yes"&gt;   &lt;/span&gt;(Sadly, the study was lacking statistics about how professionals’ significant others felt about this.)&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;35% of smartphone users even picked their mobile phone over their spouse, if forced to choose.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;The mobile device is a perfect way to connect consumers with frequently used services like health care information. &lt;span style="mso-spacerun:yes"&gt; &lt;/span&gt;People carry their phones places that laptops or web services can never go – like directly into a store or during air travel lay-overs.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Context Aware&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Today’s mobile phone is a device that can understand context.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;Unlike Flash sites or some of the desktop experiences marketers use, the mobile application can understand if your consumer is standing in a store, on vacation, or at home.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;Using this information, different messages can be delivered depending on the location of the user.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;For example, consumers passing by a store can receive promotions personalized to their shopping habits, or travelers in an airport can receive customer care directions specific to where they are.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;While so much marketing is context independent, location-based services can achieve a level of understanding intention on par with paid search.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;b style="mso-bidi-font-weight:normal"&gt;Conclusion&lt;o:p&gt;&lt;/o:p&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Branded mobile applications are a new way for brands to directly communicate with consumers.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;Rather than just games or search functions, they offer a new channel to give narrowly targeted services to consumers.&lt;span style="mso-spacerun:yes"&gt;  &lt;/span&gt;Brands should embrace this channel for more than just trivial apps – the right mobile application can drive sales, market share, and customer satisfaction.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-1051065083667287120?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/07/branded-e2c-portals-next-phase-of.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-7615812595228186087</guid><pubDate>Mon, 15 Jun 2009 18:18:00 +0000</pubDate><atom:updated>2009-06-15T11:59:32.657-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>handset fragmentation</category><category domain='http://www.blogger.com/atom/ns#'>mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>carriers</category><category domain='http://www.blogger.com/atom/ns#'>porting</category><category domain='http://www.blogger.com/atom/ns#'>transcoding</category><category domain='http://www.blogger.com/atom/ns#'>developers</category><category domain='http://www.blogger.com/atom/ns#'>app developers</category><category domain='http://www.blogger.com/atom/ns#'>hardware diversity</category><category domain='http://www.blogger.com/atom/ns#'>fragmentation</category><category domain='http://www.blogger.com/atom/ns#'>mobility barrier</category><category domain='http://www.blogger.com/atom/ns#'>handset makers</category><category domain='http://www.blogger.com/atom/ns#'>mobile platform</category><title>Fragmentation Stifles Innovation in Mobile and It's Here to Stay</title><description>Kenan Wang&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;There's a concept that we at Ondeego call the Mobility Barrier. The Mobility Barrier is our name for all the issues that prevent companies or individual developers from creating mobile applications. It is the reason that innovation in mobile hasn't hit the point of inflection, where growth becomes exponential. Right now innovation in mobile has largely been linear (with the notable exception of the iPhone). Up until a couple years ago a select group of people from the carriers or the handset manufacturers provided almost all the innovation (primarily in the form of new devices and features) in the mobile space up. "Apple has fundamentally changed the industry from a focus on hardware to a focus on software and content," says Ken Dulaney, an analyst at consultancy Gartner (IT). In response the major players in the mobile industry - the carriers, platform vendors, and handset manufacturers - are showing a willingness to work with outside groups particularly ISVs (check out the 100 Million Club http://www.visionmobile.com/research.php#The-100-million-club) to drive innovation through software and content.  However, the Mobile Barrier still prevents the everyday developer from contributing much to the mobile space outside of the iPhone app store.  What will change things is when the economics change so that the everyday developer can contribute to innovation too.&lt;br /&gt;&lt;br /&gt;One lesson that Mobile can learn from the recent Web movement is that innovation is largely a product of economics.  When making websites became easy and cheap enough to make, so that businesses and everyday people could contribute- that's when the web took off.&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;The potential of HTML to create graphically attractive web-sites and the ease with which these sites could be accessed through the new generations of web-browsers opened the Web to whole new groups. Until now, the Web had served two main communities - the scientific community (accessing on-line documentation) and a wider 'netizens' (net citizens) community (accessing e-mail and news-group facilities). Now commercial web-sites began their proliferation, followed at a short distance by local school/club/family sites. These developments were accelerated by the appearance of ever-more powerful (and cheap) personal computers (which increased both the number of netizens and the potential market for businesses) and by the increase in capacity of the communications infrastructure. The Web now exploded.&lt;br /&gt;&lt;br /&gt;Griffiths, R. T. "Internet for Historians, History of the Internet: The Development of the Internet."&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;What we see is that the Mobility Barrier is preventing the supply of mobile apps from meeting the latent demand for mobile apps - there is a gap in innovation. In a study by IBM, “89 percent said they would like a higher level of personalization through the ability to pick and mix applications, services and other characteristics of the handset such as form factors and designs. Moreover, 81 percent would switch to a provider that offered greater choice for customization.”&lt;br /&gt;&lt;a href="http://www.telecommagazine.com/international/article.asp?HH_ID=AR_4564"&gt;http://www.telecommagazine.com/international/article.asp?HH_ID=AR_4564&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Furthermore, a detailed look at the behavior of app phone users and non-app phone users shows promising signs of the potential for mobile innovation. &lt;a href="http://www.gravitytank.com/apps/#"&gt;http://www.gravitytank.com/apps/#&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There are three main layers to the Mobility Barrier. One layer is technical issues. The second layer is business issues. The third layer is the lack of understanding of the mobile space. All of these layers are interconnected and affect each other; however, it's possible to take one area as the focus of our discussion to drive our analysis of the problem. Today we will talk about the technical issues blocking mobile innovation, particularly fragmentation.&lt;br /&gt;&lt;br /&gt;Damith C. Rajapakse, from the National University of Singapore, School of Computing, has a &lt;a href="http://www.comp.nus.edu.sg/%7Edamithch/df/device-fragmentation.htm"&gt;superb article discussing Device Fragmentation&lt;/a&gt;.  Rajapakse describes fragmentation as "the inability to 'write once and run anywhere'." He breaks down the reasons for fragmentation as&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;-"Hardware diversity, such as differences in screen parameters (size, color depth, orientation, aspect ratio), memory size (heap, persistent), processing power, input mode (keyboard, touch screen, etc.), presence of additional hardware (camera, voice recorder), and connectivity options (bluetooth, IR, GPRS, etc.).&lt;br /&gt;&lt;br /&gt;Software diversity:&lt;br /&gt;-Platform diversity, such as differences in platform/OS (Symbian, Nokia OS, RIM OS, Apple OS X, PalmOS, Mobile Linux, Android, BREW,etc.), API standards (MIDP 1.0, MIDP 2.0, etc.), optional APIs, proprietary APIs, variations in access to hardware (e.g., fullscreen support, access to local storage),  and differences in multimedia support (e.g., codecs), maximum binary size allowed, etc.&lt;br /&gt;&lt;br /&gt;-Implementation diversity, such as quirks of implementing standards (different interpretations of the standards, bugs, etc.). Incideentally, fragmentation resulting from implementation bugs/quirks is one of the most tiresome type of fragmentations, according to practitioners.&lt;br /&gt;&lt;br /&gt;-Feature variations, such as light version vs full version&lt;br /&gt;&lt;br /&gt;User-preference diversity, in aspects such as in language, style, etc., or accessibility requirements&lt;br /&gt;&lt;br /&gt;Environmental diversity, such as diversity in the deployment infrastructure (e.g., branding by carrier, compatibility requirements of the carrier backend APIs, gateway characteristics, opened ports, restrictions on access to outside the network etc.), locale, local standards."&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Each of these separate issues don't just add to the problem, they multiply it. We as application developers have thousands and thousands of possible variations (Rajapakse calls them Operating Contexts or OCs) to worry about. The problem is big.&lt;br /&gt;&lt;br /&gt;Rajapakse further classifies these issues into two types of diversity:&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;"Essential diversity: This is the diversity that differentiates a product/service in some useful manner. This kind of diversity is intentional and often unavoidable. For example, users will continue to differ in their preferred size for a device, and the device manufacturers will continue to differentiate the devices in terms of size.&lt;br /&gt;&lt;br /&gt;Accidental diversity: This is the diversity that - does not serve any useful purpose, is often introduced unintentionally, and is often avoidable. For example, diversity due to API implementation bugs/quirks is unintentional, avoidable, and does not serve any useful purpose"&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;He states that essential diversity is here to stay and will only get worse as the additional features and capabilities are added to different devices. This seems like a fairly reasonable assumption. Because each person treats and uses their mobile device so differently no hardware or feature standardization, like what has happened with PCs, is likely. Two factors contributing to increased essential diversity are:&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;" Desktop-class mobile applications: As devices become more capable, there is more potential for feature-rich, mission-critical (and consequently larger, and more complex) applications to move to the mobile platform. This is likely to exacerbate the fragmentation problem. Specifically, it will increase the effort required to fit one application to multiple OCs.&lt;br /&gt;&lt;br /&gt;Growing number of new device models: Even released applications will continues to fragment, as more and more new OCs need to be supported. This fragmentation may be hard to predict, or plan for. It also becomes necessary to identify OCs no longer cost-effective to support."&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Accidental diversity can be addressed, he says. Better standards would go a long way to help. However he accurately points out that the major mobile players - Carriers, Device Manufacturers, and Platform vendors play a critical role.&lt;br /&gt;&lt;br /&gt;I believe even accidental diversity has little chance of getting better in the near future. Some efforts exist toward promoting standards and consolidating the number of platforms. Things like the Open Handset Alliance, or &lt;a href="http://www.informationweek.com/news/software/open_source/showArticle.jhtml?articleID=217701621"&gt;efforts by Sun &lt;/a&gt;may help in the long run. However, with such a proliferation of platforms in the market, more platforms entering every day, and no pressing need for the major players to reduce fragmentation, fragmentation will only get worse in the near future, and will be slow to get better.&lt;br /&gt;&lt;a href="http://disruptivewireless.blogspot.com/2008/03/handset-os-fragmentation-is-here-to.html"&gt;http://disruptivewireless.blogspot.com/2008/03/handset-os-fragmentation-is-here-to.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Rajapakse also discusses at length the various ways of dealing with fragmentation. &lt;a href="http://www.comp.nus.edu.sg/%7Edamithch/df/dfApproches.htm"&gt;http://www.comp.nus.edu.sg/~damithch/df/dfApproches.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;We use what Rajapakse calls the All-In-One, Self Adapt approach to dealing with fragmentation.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-7615812595228186087?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/fragmentation-stifles-innovation-in.html</link><author>noreply@blogger.com (Oren Salomon)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-6845725353541368715</guid><pubDate>Wed, 10 Jun 2009 21:40:00 +0000</pubDate><atom:updated>2009-06-15T17:39:25.301-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>compliance</category><category domain='http://www.blogger.com/atom/ns#'>branded mobile applications</category><category domain='http://www.blogger.com/atom/ns#'>prescriptions</category><category domain='http://www.blogger.com/atom/ns#'>healthcare</category><category domain='http://www.blogger.com/atom/ns#'>non-compliance</category><category domain='http://www.blogger.com/atom/ns#'>applications</category><title>Compliance Through Mobile Applications</title><description>Compliance Through Mobile Applications&lt;br /&gt;&lt;br /&gt;Oren Salomon&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Compliance – What it is and Why it Matters&lt;/span&gt;&lt;br /&gt;  Patient compliance (also known as adherence or persistence) with doctors’ prescriptions is essential to treating medical conditions.  Many patients choose to ignore doctors’ orders for any number of reasons, but the result are the same: lost sales to pharma companies and increased healthcare costs for healthcare providers as the entire system has to absorb the consequences of letting medical conditions spiral out of control. This cost can be forwarded onto consumers in the form of worsening their quality of life, possibly even through death in extreme cases. In financial terms, hospital stays are expensive and avoiding them through compliance is a much more economical solution. Bacteria can mutate and evolve into a bigger problem for those who do not fully comply with anti-biotic prescriptions.&lt;br /&gt;&lt;br /&gt;According to a &lt;a href="http://sites.mckesson.com/mprs/images/page/pc_mckesson_reprint_7-21.pdf"&gt;McKesson report&lt;/a&gt;, the leading cause of non-compliance is simply forgetting to take one’s medication. Nearly 80% of respondents of a study of those who did not fully comply with doctors orders cited this as a reason for non-compliance, followed by running out of medication (19%), too costly (9%), perceived lack of need (9%), side effects (7%), and the very rare no improvement seen (3%). All of these are causes that need to be addressed as non-compliance is one of the most costly problems facing the pharmaceutical and healthcare industries today.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Compliance Hurting the Healthy of the Industry: Costs to Pharma and Healthcare&lt;/span&gt;&lt;br /&gt;  The primary cost to pharmaceutical companies is the lost revenue from unfilled prescriptions. Conservative estimates indicate that only 60% of prescriptions actually get filled and while 100% compliance is an unrealistic goal, some of the &lt;a href="http://www.redorbit.com/news/health/804637/patient_noncompliance_estimated_to_cost_the_pharma_industry_us70_billion/index.html"&gt;$70 billion in revenue lost annually from non-compliance&lt;/a&gt; could reasonably be captured if pharmaceutical companies find a way to merely increase compliance rates. Essentially this means for every percent rise in compliance, the pharmaceutical industry as a whole stands to gain nearly $2 billion in sales. Rather than targeting new potential customers, which is very costly and involves pushing doctors to write more prescriptions (and leads to charges of “disease mongering”), pharmaceutical companies can raise revenues in a more cost effective manner by converting more existing prescriptions into sales.  As will be discussed in the next section, this can be achieved by better managing relationships with existing patients using new mobile technologies.&lt;br /&gt;&lt;br /&gt;Non-compliance is not only an issue in the lost revenue from the marketplace for drugs, but can also tamper with research and clinical trials. One of the key problems with non-compliance is that patients and especially paid test subject patients do not always freely admit when they are not complying with doctors’ instructions with regards to prescriptions. This creates problems in research models as some test patients will effectively place themselves in a placebo category by not taking the medication given to them without telling those running the trial. This can conflate variables in research and also lead test results for drugs to represent less effectiveness than actually achieved. Controlling for non-compliance is difficult when testing for it is expensive and researchers like doctors rely on honesty from their patients for effective treatment. Doctors and researchers are simply too busy to conduct a lie detector test on their patients to guarantee compliance. There must be a better means that doesn’t waste doctors’ time, researchers’ time, or patients’ time. Convenient and effective ways to increase compliance can be achieved through mobile technologies.&lt;br /&gt;&lt;br /&gt;Lastly there is the myriad of costs for the healthcare industry as a whole. Medical problems do not simply go away and if allowed to fester the patient’s condition can deteriorate and treatments for worsening conditions become progressively more expensive. Often times, if the condition leads to extensive hospital stays, the medical bill can spiral into six or seven figures, a medical debt many patients cannot afford, leaving taxpayers and the healthcare industry as a whole the burden of paying for their mistakes. Fulfilling prescriptions immediately and taking medication as prescribed  is an effective form of preventative healthcare that can keep healthcare costs down for our society. &lt;a href="http://bits.blogs.nytimes.com/2009/05/28/electronic-patient-records-will-force-consolidation-in-health-care/"&gt;Healthcare costs for our nation&lt;/a&gt; are spiraling out of control and growing faster than any significant section of our national GDP. More so than Social Security, Healthcare costs represent the biggest budget challenge for the federal government. New mobile technologies promise to raise compliance and therefore hopefully mitigate the challenges that growing healthcare costs present to our society.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Pharma’s New Swiss Army Knife: Mobile tools to combat non-compliance&lt;/span&gt;&lt;br /&gt;  A popular mobile tool for raising compliance to date has been SMS, commonly referred to as text messages. An SMS reminder sent to the patient when they need to take their medication or refill their prescription can be an effective tool, but there are significant limitations. First and foremost, there is the 160 character limitation of any SMS message. Second, text messages, like email, can be considered invasive and even intrusive. Creating an opt-in feature can help keep this from being viewed as annoying, but the SMS is a 1 way communication tool that cannot easily adjust for the customer’s individual pill schedule or refill schedule. There is no room for the creation of rich content explaining the benefits, side-effects , and implementation instructions of the medication.  Additionally, depending on carrier infrastructure, SMS messages can be delivered late or not at all – resulting in non-compliance. Generally, SMS messages serve best for campaigns that send an undifferentiated non-personalized  message to a wide reaching audience. Serving an individual patient through SMS is therefore generally ineffective when compared other, more sophisticated tools.&lt;br /&gt;&lt;br /&gt;Branded mobile applications behave much like programs on a computer in their high functionality, but reside on an individuals’ most personal electronic device, their cell phone. Much more secure from both hackers and other physical users, cell phones are a personal item that are generally not shared and therefore provide a digital safe haven for storing this kind of personal medical information. Because they are always opt-in (the user has to willfully choose to download an application to a cell phone), being perceived as invasive is almost never an issue for mobile applications. The power of mobile applications to increase compliance lie in  their ability as a powerful communication tool, not only to remind the user to both take and refill their medication when appropriate. Mobile applications can feature as much content as most websites and display them in similarly easily accessible and navigable formats. The patient can become educated on the benefits, side effects, and implementation instructions (particularly useful for inhalers) on their own time, sparing doctors and pharmacist’s time and efforts. Unlike pamphlets with this information that are quickly discarded, mobile applications (until deleted) follow the patient everywhere they go. Additionally as a digital format, mobile applications offer the ability to animate instructions, which can often be more helpful than static illustrations.&lt;br /&gt;&lt;br /&gt;In sum, mobile applications offer many improvements over existing approaches to combating non-compliance without suffering many drawbacks. While mobile applications require an upfront start up cost, their maintenance is often low cost and does not require many human hours. A mobile application, much like a website, works overtime and is available to the consumer 24-7 for confidential disclosure of information. A mobile application, unlike an SMS can be outfitted to include full disclosure (fair balance) on side effects and drawbacks of medication and therefore comply with legal regulations much easier and still leave plenty of room to express benefits. Therefore mobile applications represent pharmaceutical companies’ best tool yet to combat non-compliance.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-6845725353541368715?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/compliance-through-mobile-applications.html</link><author>noreply@blogger.com (Oren Salomon)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-5370703640632287832</guid><pubDate>Tue, 09 Jun 2009 22:37:00 +0000</pubDate><atom:updated>2009-06-09T15:41:39.669-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>doctors</category><category domain='http://www.blogger.com/atom/ns#'>branded mobile applications</category><category domain='http://www.blogger.com/atom/ns#'>smartphones</category><category domain='http://www.blogger.com/atom/ns#'>pharma</category><category domain='http://www.blogger.com/atom/ns#'>healthcare</category><title>64% of Doctors in the US have Smartphones</title><description>&lt;p class="MsoNormal"&gt;&lt;a href="http://www.ama-assn.org/amednews/2009/05/25/bil20525.htm"&gt;64% of Doctors in the US have Smartphones: A Beachhead for Pharma Mobile Applications&lt;/a&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Oren Salomon&lt;/p&gt;  &lt;p class="MsoNormal"&gt;This article points out some very useful statistics and trends, namely that 64% of doctors in the US use smartphones. Compared with the &lt;a href="http://www.connectitnews.com/canada/story.cfm?item=6837"&gt;27% adoption rate of the general population&lt;/a&gt;, doctors are early adopters.&lt;span style=""&gt;  &lt;/span&gt;This makes sense – HCPs were some of the first adopters of mobile technology like pagers.&lt;span style=""&gt;  &lt;/span&gt;They are the quintessential mobile professionals.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Popular uses of smartphones for doctors have been searchable digital versions of medical reference books, which often number in the thousands of pages. Dosage calculators are also popular. Though the smartphone can perform many tasks of a desktop, it is available wherever busy doctors go, while desktops stay in the office. The only limiting factor of a smartphone for doctors seems to be screen size. Within a few years, it is conceivable that doctors will manage their practices primarily through their smartphones rather than their computers. &lt;/p&gt;  &lt;p class="MsoNormal"&gt;Today, national initiatives are pushing for implementing digital healthcare services. If patient info and the like becomes available through secure online resources, then the smartphone becomes an attractive platform for health applications because of its mobile convenience. The appeal of bringing health applications to the “point of care” explains why the smartphone has been the most quickly adopted technology ever by doctors. &lt;/p&gt;  &lt;p class="MsoNormal"&gt;This all means that mobile applications can be a beachhead for pharma marketers. As doctors become more accustomed to downloading mobile applications to their smartphones, the opportunities to get a larger share of the doctors’ time increase. This is because doctors’ while constantly busy, will find themselves idle with nothing to do at various times of the day, perhaps on a train or the 2 minutes between appointments with a moment to spare. Though your sales rep could never reach them at this moment, the doctor might choose to open up the mobile application on their smartphone and learn a little more about your product offering.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-5370703640632287832?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/64-of-doctors-in-us-have-smartphones_09.html</link><author>noreply@blogger.com (Oren Salomon)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-2089420616549547281</guid><pubDate>Mon, 08 Jun 2009 17:54:00 +0000</pubDate><atom:updated>2009-06-10T16:30:11.364-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>app stores</category><category domain='http://www.blogger.com/atom/ns#'>carriers</category><category domain='http://www.blogger.com/atom/ns#'>developer ecosystem</category><category domain='http://www.blogger.com/atom/ns#'>developers</category><category domain='http://www.blogger.com/atom/ns#'>app developers</category><category domain='http://www.blogger.com/atom/ns#'>ARPU</category><category domain='http://www.blogger.com/atom/ns#'>handset makers</category><title>4 Keys to a Great Developer Ecosystem</title><description>&lt;p class="MsoNormal" style="margin: 0in 6pt 12pt; line-height: 18pt;"&gt;&lt;span style=";font-family:&amp;quot;;font-size:10;color:black;"   &gt;The Pre's biggest disadvantage is its app store, the App Catalog. At launch, it has only about a dozen apps, compared with over 40,000 for the iPhone, and thousands each for the G1 and the modern BlackBerry models. Even worse, the Pre App Catalog isn't finished. It's immature, it's labeled a beta, and Palm has yet to release the tools for making Pre apps available to more than a small group of developers.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;-&lt;span style=""&gt;              &lt;/span&gt;&lt;a href="http://online.wsj.com/article/SB124407239691783093.html"&gt;Walt Mossberg, Wall Street Journal, June 4, 2008&lt;/a&gt; &lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt;&lt;span style=""&gt;With the rise of new app stores, attracting developers to a platform or app store is important to drive revenue and stay relevant.&lt;span style=""&gt;  &lt;/span&gt;Today’s consumers know that “there’s an app for that,” and they want that app on their phones.&lt;span style=""&gt;  &lt;/span&gt;If today’s carriers or handset manufacturers can’t offer those cool and useful apps, consumers will switch to another platform, carrier, or app store to get them.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt;&lt;span style=""&gt;Today’s carrier or handset manufacturer is now serving more masters than ever before – in addition to their stockholders and consumers, they must now attract developers to their offering.&lt;span style=""&gt;  &lt;/span&gt;App stores and great developer programs are a way for carriers to be more than “dumb pipes,” and maintain relevance in the rapidly growing mobile content ecosystem.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt;&lt;span style=""&gt;The good news is developers will flock to these new platforms and create applications.&lt;span style=""&gt;  &lt;/span&gt;They will sell them in app stores, which will drive app store revenue, and drive consumers to these platforms.&lt;span style=""&gt;  &lt;/span&gt;A good vibrant developer program can increase revenue, drive new consumers to devices, and add new services to devices without effort on the part of the manufacturer/carrier.&lt;span style=""&gt;  &lt;/span&gt;(For example, see the iPhone.)&lt;/span&gt;&lt;span style=";font-family:&amp;quot;;" &gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;The bad news is that developer programs can go off the rails – see Palm’s struggles with their Pre development community.&lt;span style=""&gt;   &lt;/span&gt;As you can see from the Palm testimony, when developers get mad, they use the internet to show their disapproval – like &lt;/span&gt;&lt;a href="http://www.danrumney.co.uk/2009/05/21/predevcamp-palms-missed-opportunity/"&gt;here &lt;/a&gt;&lt;span style=""&gt;, &lt;/span&gt;&lt;a href="http://blog.gallucci.net/2009/05/palm-doesnt-get-it.html"&gt;here&lt;/a&gt;&lt;span style=""&gt; and &lt;/span&gt;&lt;a href="http://whurley.com/2009/05/21/exit-whurley-stage-left/"&gt;here&lt;/a&gt;&lt;span style=""&gt; – and thoughts spread virally amongst developers really, really easily.&lt;span style=""&gt;  &lt;/span&gt;(A lot of developers are bloggers, active forum contributors, and avid social media users.&lt;span style=""&gt;  &lt;/span&gt;Some of them are even SEO/SEM experts.&lt;span style=""&gt;  &lt;/span&gt;It is one thing to be hated on the internet, but it’s quite another to be hated by the people who can get to the top of Google page.) Palm’s poor launch is a wake-up call to take a look at what makes developer programs succeed or fail.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;&lt;br&gt;Today’s app developers are not traditional ISVs (independent software vendors) – they are college kids in dorm rooms, experienced programmers coding after hours, and small shops run out of garages – think the early days of the internet.&lt;span style=""&gt;  &lt;/span&gt;While larger ISVs are important and part of a vibrant ecosystem , their needs are different than those of small developers.&lt;span style=""&gt;  &lt;/span&gt;Because of this difference in motivation, it makes sense to give ISVs a separate track, with a business development manager contact.&lt;span style=""&gt;  &lt;/span&gt;Smaller developers, by contrast, need a contact who understands them – someone who is a developer and understands the technical and logistical problems associated with creating applications for your platform.&lt;span style=""&gt;  &lt;/span&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;&lt;span style=""&gt; &lt;/span&gt;&lt;br&gt;The keys to attracting small developers to a particular platform are simple yet often missed: give them tools, share revenue with them, communicate with them, and be transparent with your rules.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b&gt;&lt;span style=""&gt;&lt;br&gt;Give Them Tools&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;Today’s mobile application developers are looking for the most effective way to create and bring to market their mobile service.&lt;span style=""&gt;  &lt;/span&gt;Because it is impossible (or at least very difficult) to predict what will be a runaway success in an app store combined with fragmentation issues, creating an app is a substantial upfront cost to a developer not just in cash outlays but in time costs as well.&lt;span style=""&gt;   &lt;/span&gt;One way you can lower the barrier-to-entry for new developers to your platform is to give them great, easy-to-use tools and lower their time costs so they can spend more time developing and less time learning how to use your tools.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;&lt;br&gt;Apple’s iPhone SDK is a great example of this – they created tools that made it easy for developers to create visually attractive applications.&lt;span style=""&gt;  &lt;/span&gt;Fragmentation is still a huge problem and appears to be getting worse.&lt;span style=""&gt;  &lt;/span&gt;If you operate a mobile application store on multiple handset platforms, you must give developers tools to allow them to tackle the fragmentation issues.&lt;span style=""&gt;  &lt;/span&gt;By contrast, Palm refuses to distribute their SDK publicly, and has about a dozen apps.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b&gt;&lt;span style=""&gt;&lt;br&gt;Sharing is Caring&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;Sharing revenue with developers is very important to attracting them to your platform.&lt;span style=""&gt;  &lt;/span&gt;While the &lt;/span&gt;&lt;a href="http://www.washingtonpost.com/wp-dyn/content/article/2008/08/11/AR2008081100440.html"&gt;standard is becomin&lt;/a&gt;&lt;span style=""&gt;g 30% with Apple App Store, other stores are picking different revenue splits.&lt;span style=""&gt;  &lt;/span&gt;Windows Mobile went with the same split, while BlackBerry opted to give their developers a little more with an 80/20 split.&lt;span style=""&gt;  &lt;/span&gt;T-Mobile has taken a different tack with their announced app store – it will cover all T-Mobile handsets and have a &lt;/span&gt;&lt;a href="http://www.pcmag.com/article2/0,2817,2330338,00.asp"&gt;revenue share based on bandwidth use&lt;/a&gt;&lt;span style=""&gt;.&lt;span style=""&gt;  &lt;/span&gt;Now that there are carrier app stores and independent app stores, it is very possible that a consumer will have more than one app store on his or her phone – even one from a carrier, one from a handset OEM, and an independent one.&lt;span style=""&gt;  &lt;/span&gt;With that in mind, developers will sell their applications in the stores with the largest reach and the most generous revenue share.&lt;span style=""&gt;  &lt;/span&gt;Some app stores, like China Mobile, &lt;/span&gt;&lt;a href="http://www.intomobile.com/2009/06/08/china-mobiles-appstore-will-ask-50-cut-of-all-sales.html"&gt;have announced&lt;/a&gt;&lt;span style=""&gt; revenue splits as high as 50-50 between developers and the carrier.&lt;span style=""&gt;  &lt;/span&gt;If your app store is not the only option, developers will seek other venues to distribute their apps.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b&gt;&lt;span style=""&gt;&lt;br&gt;Have a Dialog with Your Developers&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;Communicating with people who are developing software for your platform at their own expense is important.&lt;span style=""&gt;  &lt;/span&gt;Forums, wikis, and blogs are the best ways to do this – developers, by their nature, will first Google a problem they encounter.&lt;span style=""&gt;  &lt;/span&gt;Have a developer relations staffer monitor these forums, and answer questions.&lt;span style=""&gt;  &lt;/span&gt;BlackBerry has done a great job of this – all of the developers I know comment on how responsive their developer relations staff is on forums.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;&lt;br&gt;Not communicating with your developers is a grave mistake.&lt;span style=""&gt;  &lt;/span&gt;Complaints in the blogosphere are rampant about trying to get &lt;/span&gt;&lt;a href="http://www.crunchgear.com/2008/11/16/googles-the-latest-hit-by-the-arbitrary-iphone-ban-hammer/"&gt;answers to questions&lt;/a&gt;&lt;span style=""&gt; from Apple.&lt;span style=""&gt;  &lt;/span&gt;Then, there is the mother of all PR/Developer Relations disasters, Palm’s actions with their PreDevCamp group.&lt;span style=""&gt;  &lt;/span&gt;It seems that the organizers of these events signed an NDA with Palm, tweeted to their community that they signed such an agreement, and were then informed that they violated the NDA by tweeting about it.&lt;span style=""&gt;  &lt;/span&gt;Developers will use social media to communicate with each other about your product – join the conversation or let it happen.&lt;span style=""&gt;  &lt;/span&gt;Trying to muzzle it will lead to a disaster – such as one of the organizers of your dev community writing an article in Businessweek airing their grievances and &lt;/span&gt;&lt;a href="http://www.businessweek.com/technology/content/jun2009/tc2009062_915044.htm"&gt;predicting your failure&lt;/a&gt;&lt;span style=""&gt;.&lt;span style=""&gt;  &lt;/span&gt;Hell hath no fury like a developer scorned.&lt;/span&gt;&lt;span style=";font-family:&amp;quot;;" &gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b&gt;&lt;span style=""&gt;&lt;br&gt;Transparency&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;Developers, particularly small developers, will follow the rules of your app store.&lt;span style=""&gt;  &lt;/span&gt;However,&lt;span style=""&gt;  &lt;/span&gt;if you have rules regarding submissions, it is important that they be applied evenly across the community and across applications.&lt;span style=""&gt;  &lt;/span&gt;When you don’t do this, you have the PR storm that Apple had around approvals – the &lt;/span&gt;&lt;a href="http://www.crunchgear.com/2009/04/24/a-secret-look-into-the-iphone-app-review-process-its-run-by-eight-year-olds/"&gt;process itself&lt;/a&gt;&lt;span style=""&gt;, approving the &lt;/span&gt;&lt;a href="http://www.techcrunch.com/2009/04/22/feel-like-shaking-a-baby-to-death-theres-an-app-for-that/"&gt;baby shaking application&lt;/a&gt;&lt;span style=""&gt;, and the Trent Reznor/NIN &lt;/span&gt;&lt;a href="http://www.techcrunch.com/2009/05/03/trent-reznor-responds-to-apple-you-want-obscene-ill-show-you-obscene/"&gt;debacle&lt;/a&gt;&lt;span style=""&gt;.&lt;span style=""&gt;   &lt;/span&gt;Whether you decide to approve everything or follow content standards, you must consistently follow this policy.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;b&gt;&lt;span style=""&gt;&lt;br&gt;Conclusion&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;Today’s consumers expect mobile apps on their devices. (See the Walt Mossberg quote at the top of the article.)&lt;span style=""&gt;  &lt;/span&gt;A thriving developer ecosystem is a great thing for a platform and an app store, and will drive revenue if properly managed.&lt;span style=""&gt;  &lt;/span&gt;Transparency, dialog, sharing revenue, and provision of tools are keys to growing a developer community.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;&lt;o:p&gt; &lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;(Disclosure: Ondeego is a BlackBerry Partner.)&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;&lt;o:p&gt; &lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style="margin-bottom: 0.0001pt; line-height: normal;"&gt;&lt;span style=""&gt;Questions? Comments? Want to discuss developer relations strategies? Reach Matt at Matt (at) ondeego (dot) com, or leave a comment.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-2089420616549547281?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/4-keys-to-great-developer-ecosystem.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-5335735093351844738</guid><pubDate>Wed, 03 Jun 2009 21:00:00 +0000</pubDate><atom:updated>2009-06-03T14:30:51.128-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>carriers</category><category domain='http://www.blogger.com/atom/ns#'>developers</category><category domain='http://www.blogger.com/atom/ns#'>CellAuthor</category><title>Ken Singer Talks About Ondeego on Mobile Presence</title><description>Last week, Ondeego CEO Ken Singer was interviewed for the Mobile Presence podcast.  Ken talks about how carriers and handset makers can empower developers and drive revenue in their app stores.&lt;div&gt;&lt;a href="http://www2.webmasterradio.fm/mobile-presence/2009/mobile-platforms-for-developers-and-brands/"&gt;Ken Singer on Mobile Presence&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-5335735093351844738?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/ken-singer-talks-about-ondeego-on.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-4670159579678375995</guid><pubDate>Wed, 03 Jun 2009 16:10:00 +0000</pubDate><atom:updated>2009-06-03T09:15:26.631-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>branded mobile applications</category><category domain='http://www.blogger.com/atom/ns#'>brands</category><title>Great Article on Mobile App Strategy</title><description>I saw this article on mobile application strategy in Mobile Marketer today, and it's great.  &lt;div&gt;&lt;a href="http://www.mobilemarketer.com/cms/news/advertising/3387.html"&gt;Applications Integral Part of Mobile Marketing Strategy&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;A mobile application is a tactic in mobile marketing strategy.  An app by itself will not solve all of your problems, nor will people magically discover it.  However, a mobile app is one of the deepest, stickiest way a brand can connect with consumers.  The Weather Channel example in the article is particularly interesting. It shows that for services that consumers engage with regularly - weekly or more often - a mobile app is generally a better play than a WAP site.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-4670159579678375995?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/great-article-on-mobile-app-strategy.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-3319916805666547405</guid><pubDate>Tue, 02 Jun 2009 19:34:00 +0000</pubDate><atom:updated>2009-06-03T12:17:41.563-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>twitter</category><category domain='http://www.blogger.com/atom/ns#'>ondeego</category><title>Follow Us on Twitter!</title><description>Now, you can follow Ondeego on twitter: &lt;a href="http://www.twitter.com/ondeego"&gt;http://www.twitter.com/ondeego&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-3319916805666547405?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/follow-us-on-twitter.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-8926539681909195497</guid><pubDate>Tue, 02 Jun 2009 00:00:00 +0000</pubDate><atom:updated>2009-06-01T20:22:51.021-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>carriers</category><category domain='http://www.blogger.com/atom/ns#'>cars</category><category domain='http://www.blogger.com/atom/ns#'>ARPU</category><title>Wireless in Cars versus Mobile Phones in Cars</title><description>&lt;span style="font-size: medium;"&gt; I saw this on FierceWireless Today: &lt;br /&gt;&lt;a href="http://www.fiercewireless.com/press-releases/gartner-says-wireless-connectivity-be-main-focus-vehicle-manufacturers-2012"&gt;&lt;span style="font-size: medium;"&gt;Gartner Says Wireless Connectivity to be Main Focus for Vehicle Manufacturers by 2012&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is intriguing - wireless in cars.  It should give carriers new subscribers, which is good.  The ARPU will be pretty low - but does ARPU still matter when you're talking about devices that aren't phones?  For reference, the Amazon Kindle II's ARPU for Sprint is something like $2/user.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;div&gt;&lt;div&gt;&lt;span style="font-size: medium;"&gt;However, I wonder: does it make more sense to put a wireless app, the infrastructure, the SIM, etc, into a car, or does it make more sense to use everything the mobile phone the passenger already has to do the same thing?  Maybe through bluetooth (or some other way) the car could communicate with the passenger's phone, and piggyback on the existing infrastructure and handset ownership.&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;span style="font-size: medium;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-size: medium;"&gt;Either way, a subscription fee for wireless in your car when you already have a wireless device in your pocket seems like a pretty hard sell.&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;span style="font-size: medium;"&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-8926539681909195497?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/wireless-in-cars-versus-mobile-phones.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-8323474320591856413</guid><pubDate>Mon, 01 Jun 2009 22:25:00 +0000</pubDate><atom:updated>2009-06-01T15:28:38.687-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>mobile marketing</category><category domain='http://www.blogger.com/atom/ns#'>branded mobile applications</category><category domain='http://www.blogger.com/atom/ns#'>application stores</category><category domain='http://www.blogger.com/atom/ns#'>beyond the iphone</category><title>Branded Mobile Applications - In the Trenches, Beyond the iPhone - Extended Edition</title><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://ondeego.com/blogger/uploaded_images/dsoftm-748731.jpg"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 225px;" src="http://ondeego.com/blogger/uploaded_images/dsoftm-748729.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Parts of this post appear in the article “Branded Mobile Applications: In the Trenches, Beyond the iPhone,” in the Mobile Marketer Guide to Classic Advertising.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;This is the “extended version – blog cut.” &lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;The extended blog version pieces are in italics. &lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Additions by Matt Gratt – reach him at Matt (at) Ondeego (dot) com.&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;b&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;b&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Branded Mobile Applications: In the Trenches, Beyond the iPhone &lt;/span&gt;&lt;/span&gt;&lt;/b&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;By Ken Singer &lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Many said it couldn’t be done, but Apple’s iPhone proved that consumers will download and engage with a wide variety of branded mobile applications. The Zippo Lighter mobile application is a good example – it is the 13th most downloaded free iPhone app, with over 2.5 million downloads (Apple). Other applications offered for everything from ski condition reports to recipe finders to other branded mobile services for consumers have generated substantial brand utility, website visits, and even direct revenue.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;While brands making software services for mobile phones may seem strange, it reflects several current trends in marketing.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;No longer can brands “interrupt” consumers into attention, as Seth Godin and many others will tell you.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;The iPhone application needs to be of serious utility to consumers – often aiding them in enjoying the brand’s products.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;For instance, as a snowboarder, I love the North Face Snow Report app (and the many other ski report apps out there from different brands – REI, CLIF Bar, etc) – it enables me to find the ski resort with the best powder on a weekend pilgrimage to Lake Tahoe.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Rather than trying to interrupt me while I consume media, the brand is instead reaching out and giving me a service to help me enjoy their products.&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/i&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;However, only 17 million consumers use iPhones, compared to the more than 50 million BlackBerry users (Walt Mossberg, AllThingsD, April 10th, 2009.) There are also millions more smartphones on Windows Mobile and other proprietary operating systems. In the United States alone, there are more than 75 million smartphone users – the vast majority are NOT iPhone users.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/span&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Lots of others in the blogosphere (&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;linkto:&gt;&lt;/linkto:&gt;&lt;/span&gt;&lt;/i&gt;&lt;/span&gt;&lt;i&gt;&lt;a href="http://www.unstrung.com/blog.asp?blog_sectionid=626&amp;amp;doc_id=164642"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;http://www.unstrung.com/blog.asp?blog_sectionid=626&amp;amp;doc_id=164642&lt;/span&gt;&lt;/a&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&gt;) having pointed out that the iPhone is not dominant, particularly as you look across the world.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;In the United States, the BlackBerry Curve outsold the iPhone last quarter (&lt;/span&gt;&lt;/i&gt;&lt;a href="http://www.businessinsider.com/iphone-outsold-by-blackberry-curve-in-us-last-quarter-2009-5"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;http://www.businessinsider.com/iphone-outsold-by-blackberry-curve-in-us-last-quarter-2009-5&lt;/span&gt;&lt;/a&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;).&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;The iPhone is a great device – it has a great user interface and has really pushed the mobile landscape forward – but many mobile developers, particularly those in the Silicon Valley, fail to see the world beyond it. For instance, today Adverblog (&lt;/span&gt;&lt;/i&gt;&lt;a href="http://www.adverblog.com/archives/003879.htm"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;http://www.adverblog.com/archives/003879.htm&lt;/span&gt;&lt;/a&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;) points out that while 98% of Creative Directors own iPhones, less than 2% of the world’s phone-using population will even be able to download “an app for that.”&lt;/span&gt;&lt;/i&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;With the recent launch of BlackBerry App World, Windows Mobile Skymarket, the Android Market, and countless other application stores, an easy-to-use distribution channel now exists for these phones. Together, they give brands access to over 45 million consumers, more than any major network on TV. These app stores represent the future of mobile marketing and provide an extraordinary opportunity for consumer brands to make an early mark in this emerging medium.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;   &lt;/span&gt;&lt;/span&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Brands that got their apps in the store in the first 25 apps or so did phenomenally well – see Kraft’s iFood Assistant and Zippo’s Lighter app.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;These other stores are growing quickly, so the next big thing in mobile advertising will be apps for all smartphones, not just the iPhone.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;For consumer brands, the BlackBerry app store and others are untapped markets for reaching your consumer.&lt;/span&gt;&lt;/i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;b&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;b&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Best Practices in Multi-Platform Marketing &lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/b&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;i&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Making apps for other phones can be a little bit trickier than making apps for the iPhone.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;With the iPhone, there’s one platform and one distribution channel.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;There’s an SDK provided for you, and many agencies (and who knows how many vendors – apparently everyone who owns a Mac) have developed iPhone development capabilities and expertise.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;The iPhone app is the low-hanging fruit of mobile apps – you just have to hope it gets approved by Apple.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;With branded apps for other phones, there are a few more hoops to jump through – but the rewards can be exponentially larger, in terms of AdAge coverage, PR, and most importantly, downloads.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Your favorite friendly mobile applications vendor (like Ondeego) can help you navigate the trickier waters of other handsets.&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;i&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Before you begin developing your killer marketing app for the smartphones of the world, ask yourself who you are trying to reach. Your target demographic will determine your target handsets. Also, if you’re aiming at a wealthy, educated, professional demographic, then targeting BlackBerry and Windows Mobile smartphones make sense. If you’re aiming toward a younger, more urban demographic, less feature-rich handsets like RAZRs, KRZRs, and lower-end smartphones are more appropriate. &lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Once you know what handsets your target demographic is using, you can begin the task of selecting a distribution channel. The OEM app store for the devices you’re targeting is obvious, but you should add in the independent app stores (Handmark, Handango, GetJAR, etc.), and a Web-to-SMS portal from a microsite. There are also carrier application stores, but many of these require particularly arduous approvals and testing. Approval times should be accounted for as many app stores have non-transparent approval processes – they can range from days to months. &lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Apple’s somewhat schizophrenic approval policy has become a favorite topic of the blogosphere (&lt;/span&gt;&lt;/i&gt;&lt;/span&gt;&lt;a href="http://www.unstrung.com/blog.asp?blog_sectionid=626&amp;amp;doc_id=164642"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;http://www.unstrung.com/blog.asp?blog_sectionid=626&amp;amp;doc_id=164642&lt;/span&gt;&lt;/a&gt;&lt;i&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;).&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;MG Siegler from TechCrunch has made this a personal crusade (&lt;/span&gt;&lt;/span&gt;&lt;/i&gt;&lt;a href="http://www.techcrunch.com/2009/05/02/like-my-parents-in-1994-apple-find-nins-the-downward-spiral-objectionable/"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;http://www.techcrunch.com/2009/05/02/like-my-parents-in-1994-apple-find-nins-the-downward-spiral-objectionable/&lt;/span&gt;&lt;/a&gt;&lt;i&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;), and writes some great articles on it.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;   &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Other app stores approval processes range from no process what-so-ever to elaborate and Apple-like to unknown.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Always have a back-up plan – there’s lots of ways to distribute an application – and make sure you budget time for approval mishaps.&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;i&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;i&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Something we didn’t get to in the article is QA, or quality assurance testing of your mobile app.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;It is pivotally important that your vendor tests your application on all of the phones he or she claims it works on.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Real phones – not emulators.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Make sure they also test it on all carriers they say it will work on.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;At Ondeego, we use DeviceAnywhere – a great testing service that lets you use real phones over the internet - to make sure our applications work on all handset and carrier pairs that we claim.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;(Disclosure: DeviceAnywhere worked with Ondeego to provide free hours to the UC Berkeley students developing mobile applications in our class at UC Berkeley.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;They’re a partner of ours.)&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Marketing your application is also very important. To be effective, your mobile application should be part of a holistic strategy across multiple channels – not just an application. You’re launching a branded mobile service, and consumers have to find it to download it. Advertising on other mobile applications or websites can be effective, but blogger outreach and social media is the most cost-effective way to market your app. &lt;/span&gt;&lt;i&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;While there are many best ways to publicize your app, we’ve found the cheapest, most effective way is through blogger outreach.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;There’s a lot of device specific blogs and area specific blogs – ie you have a golf course finder for BlackBerry – you should reach out to BlackBerry bloggers and golf bloggers.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;The drawback here is that you have to have a good application that people will write about.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;(Then again, if you don’t, you may be barking up the wrong tree.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Just having a mobile app isn’t enough – it has to have real utility to the end user.)&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Alternatively, if you have money, you can use ad buys on other mobile sites and applications – the main advantage to these is it targets users that already use mobile services.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;As is somewhat obvious, these ad buys cost money, while blogger outreach is free. &lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/i&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;i&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;i&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Considering a multi-platform mobile app?&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Come see the experts at Ondeego.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;We’ve launched marketing apps for large brands that work on most handsets on the market.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Email &lt;/span&gt;&lt;a href="mailto:sales@ondeego.com"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;sales@ondeego.com&lt;/span&gt;&lt;/a&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; to set up your free consultation.&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/span&gt;&lt;/i&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="Default"&gt;&lt;span&gt;&lt;o:p&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt; &lt;/span&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Note: All statistics are current as of this writing.&lt;/span&gt;&lt;span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;They may change.&lt;/span&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-8323474320591856413?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/branded-mobile-applications-in-trenches.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-5534842382292472632</guid><pubDate>Mon, 01 Jun 2009 20:48:00 +0000</pubDate><atom:updated>2009-06-01T14:55:38.983-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>developers</category><category domain='http://www.blogger.com/atom/ns#'>marketing</category><category domain='http://www.blogger.com/atom/ns#'>analytics</category><category domain='http://www.blogger.com/atom/ns#'>brands</category><title>Flurry: Analytics for Mobile Apps</title><description>&lt;p class="MsoNormal"&gt;Flurry: Mobile Analytics Provider&lt;/p&gt;  &lt;p class="MsoNormal"&gt;I was recommended &lt;a href="http://www.flurry.com/"&gt;Flurry&lt;/a&gt; (http://www.flurry.com) by one of our friends at &lt;a href="http://www.trendmobility.com/"&gt;Trend Mobility&lt;/a&gt; (&lt;a href="http://www.trendmobility.com/"&gt;http://www.trendmobility.com&lt;/a&gt;).&lt;span style=""&gt;  &lt;/span&gt;Flurry is a really cool mobile analytics service that works across almost all platforms (just like Ondeego's applications).&lt;span style=""&gt;  &lt;/span&gt;With just one snippet of code, you get close to real-time analytics and insights about your app and how it gets used.&lt;span style=""&gt;  &lt;/span&gt;It's like Google Analytics for mobile – you even get pretty graphs in flash on your analytics page.&lt;span style=""&gt;  &lt;/span&gt;Cool product, responsive team – a good thing, all in all.&lt;span style=""&gt;  &lt;/span&gt;If you’re a mobile app developer looking for insights into consumer behavior, or a brand seeking to understand who actually uses your app, it might be the piece you need.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;(Disclosure: We use Flurry to track some of our applications. ) &lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-5534842382292472632?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/flurry-analytics-for-mobile-apps.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-6507272122237969080.post-8672838187315885609</guid><pubDate>Sun, 31 May 2009 20:46:00 +0000</pubDate><atom:updated>2009-06-01T16:28:20.283-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>welcome</category><title>Hello World</title><description>&lt;p class="MsoNormal"&gt;Welcome to the Ondeego blog.&lt;span style=""&gt;  &lt;/span&gt;From here forth, we will be using this blog to share our thoughts with the world.&lt;span style=""&gt;  &lt;/span&gt;You’ll see a lot of interesting topics covered, of value to all players in the mobile ecosystem and to all companies that could stand to get into the mobile world.&lt;span style=""&gt;  &lt;/span&gt;We’ll focus predominantly on mobile solutions for pharmaceutical companies and application development topics for carriers and handset manufacturers, but you should also see some mobile marketing and general Ondeego posts coming out.&lt;/p&gt;  &lt;p class="MsoNormal"&gt;Thanks for reading – we appreciate it!&lt;/p&gt;  &lt;p class="MsoNormal"&gt;If you want to see a particular topic covered, shoot me an email at matt (at) ondeego (dot) com, and we’ll try to write on it or point you to someone that does.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6507272122237969080-8672838187315885609?l=ondeego.com%2Fblogger' alt='' /&gt;&lt;/div&gt;</description><link>http://ondeego.com/blogger/2009/06/hello-world.html</link><author>noreply@blogger.com (Matthew Gratt)</author><thr:total xmlns:thr='http://purl.org/syndication/thread/1.0'>0</thr:total></item></channel></rss>