Wednesday, April 25. 2007

What is Nokia Thinking!

There’s a battle line drawn for local mobile search, with carriers on one side and Web properties on the other side. Sure, we’ve seen a few carrier-managed and distributed POI apps; sure, we’ve seen Web property efforts to make local search available with manual address inputs; but without freely available lat/long, no one has really fired a shot yet… except Nokia. In a neither here nor there purgatory position, some suggest they are confused over which camp they live in, evident by their distancing dance from the stodgy telecom world, while simultaneously trend-following some sort of hip mobile ‘2.0 something’. This suggests that even the best in their business are struggling with identity as Telecom and Internet forces collide on the ‘commputing’ battlefield. But, with so many application areas to tackle in commputing, why are so many (including Nokia) fixated on mobile local search? With 2 billion sets of connected eyeballs out there, that equates to a lot of ad cash. Lots of folks want that cash, which has historically gone to those who owned yellow & white pages print (yep, that would be the Telecom companies). Add to this a Telecom-world acceptance that ad-subsidized services as the way forward for mobile data consumer services in general, and someone (ah hem, the carriers) just got quite concerned that the Web guys are good at what they do. Mix in a handset provider bystander perspective to these dynamics in motion, and well, we now have a three way battle. This is going to get uglier…

Posted by Jonathan Spinney in LBS at 11:13 | Comments (0) | Trackbacks (0) |

Comments

Display comments as (Linear | Threaded)

No comments

Add Comment

Name
Email
Homepage
In reply to	[ Top level ]
Comment	Enclosing asterisks marks text as bold (*word*), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. E-Mail addresses will not be displayed and will only be used for E-Mail notifications To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information?   Subscribe to this entry