Last week, Steve Ballmer joined Nokia CEO Stephen Elop in unveiling the Lumia 900, their newest phone at a press event in Las Vegas (ahead of CES). The device represents Nokia and Microsoft's best chance yet to break Google and Apple's hold on the U.S. smartphone market. The new phone will use AT&T's LTE wireless data network. Since this is Nokia and Microsoft's (last?) chance to disrupt the most lucrative phone market, I can't wait to get my hands on one of them and experience the new device. I also would like to hear about their developer plans.
u•biq•ui•tous, adjective: existing or being everywhere, especially at the same time; omnipresent. A blog to share thoughts and ideas about the evolution of the ubiquitous network. The topics covered in this blog range from device, network, data center, and enterprise software with a special interest in business models, partnerships, developer communities, and technology adoption. The opinions expressed in this blog are mine and not necessarily those of my past or present employers.
Showing posts with label android. Show all posts
Showing posts with label android. Show all posts
Friday, January 20, 2012
Saturday, December 17, 2011
Will BlackBerry survive 2012?
Good article here. The answer is no. According to research group Canalys, RIM's share of the smartphone market in the US fell to 9.2% in the third quarter from 24% in the same period last year. You don't recover from this kind of numbers, not unless you have a great plan in the works.
There might be room for another developer environment on top of iOS and Android, but it is not going to be RIM (Microsoft is not going to abandon a market that could grow into a trillion dollars). RIM totally missed the apps boat and doesn't have an attractive value proposition for users and developers. Why would you spend time and money porting your apps on a platform with a declining number of activated users?
There might be room for another developer environment on top of iOS and Android, but it is not going to be RIM (Microsoft is not going to abandon a market that could grow into a trillion dollars). RIM totally missed the apps boat and doesn't have an attractive value proposition for users and developers. Why would you spend time and money porting your apps on a platform with a declining number of activated users?
Labels:
android,
apple,
developers,
mobility,
rim
Monday, August 15, 2011
Google to Buy Motorola Mobility for $12.5 Billion
Looks like Larry Page didn't waste time since he moved to the CEO position. It is hard to believe that the acquisition was made for Motorola's hardware business. Google wouldn't risk alienating all the smart phone makers (Samsung, HTC) who are using the Android operating system. It seems to me that Google wanted to make sure that no patent lawsuit would stop Android's growth. I see a few dark clouds on the horizon for this acquisition:
- Looking at the problems AT&T is facing with the T-Mobile acquisition, I wouldn't be surprised to see the Feds looking at this transaction very closely and, despite approving other patent acquisitions, investigating the run for patents.
- Set top box, smart phone and tablet manufacturers may ask Google to reconsider the move or get guarantees from Google about the future of their relationships.
- Nearly 20,000 employees to integrate in a software, Silicon Valley culture-driven company. It will be a challenge for both sides to adjust to the new environment.
There is no doubt that there is a huge patent war going on between Google on one side and Apple and Microsoft on the other side. What will happen when they run out of patents to buy?
Wednesday, March 10, 2010
How many Java developers are there?

The author of the blog says that at the time of Java's open sourcing in 2007, there were 6 million Java developers and the number of Java developers had been rising at an average of 0.75 million per year during the previous two years. After Java was open sourced, that number shot up to 1 million per year.
Why the success?
From a technical point of view, "Write Once, Run Anywhere" and a solid set of APIs would do the trick.
From a business point of view, Free and a "transparent" Java Community Process would work, but a solid evangelist like Sun Microsystems is also needed.
As the back-end is moving to the cloud and the front-end is moving to mobile devices, Google and Apple are in control of the user experience. Java is still very relevant (through Android for the front-end).
Wednesday, January 27, 2010
Disruption at work: Apple's iPad

- Amazon. It's going to take a lot of work for the Kindle to get any significant traction unless there is a big change in design and business model.
- Carriers. AT&T gets a 3GSM model to increase its subscriber base in an environment where ARPU is declining. Verizon and Sprint must be worried and so should be other carriers worldwide.
- Print Media. It's going to be very interesting to watch how media companies such as newspapers are going to react to the new device. Why do you want to pay for print newspapers/magazines ever again? I'd better monitor newspapers sales and distribution from now on.
- Device manufacturers (Nokia, RIM, Samsung, LG). Apple is all over the house now, they have so many touch points with the consumer that the barriers to entry will be too high for you and you may become irrelevant quickly.
- Google. This is a double-edged sword. Apple was first to market but a lot of the device manufacturers may flock to Google to adopt Android. This looks very much like the open vs closed war that we saw before.
Wednesday, December 9, 2009
Context-aware technology
Early 2000, Location Based Services (LBS) already promised unimaginable smart services to serve coupon to shoppers walking by a store and other innovative applications. Handheld location was determined by triangulation based on signal strength from each base station. That architecture never delivered. Several reasons to this failure: hype cycle, precision was not good, wireless service providers controlled the information and wanted their own applications to use that data (not external applications). It is my opinion that the first incarnation of presence services went the same way for the exact same reasons.
Fast-forward nearly 10 years and we have a completely different environment. Apple (and its developers/partners), and Google are in total control of the user experience. Multiple applications are able to use location information to provide advanced services to the users. Yelp provides a unique example of combined use of location and camera with the Monocle feature (augmented reality).
The more source of data you can integrate (social media, CRM), the more phone features you can leverage (camera, accelerometer), the best experience you can provide and the more information about the user you get to track. Good and bad. Best way to enable this is to open up the phone platform (Android, iOS, RIM, Windows) to as many developers as possible. Java was a great example of a rapid and pervasive adoption.
Labels:
android,
app store,
developers,
google,
iphone,
mobility,
social networks
Monday, November 12, 2007
Google announces Android

As much as I like the people at RIM, they have no innovation on the application side that can resist what Apple and Google are doing to them right now. Ask people why they have a Blackberry today and the answer will be: push email. Messaging was a great differentiator 3 years ago, but for iPhones and Android-based phones, this is not even a table stake anymore.
Operating systems that can accommodate a rich and vibrant developer community will allow the creation of many small innovative applications that will drive revenue for carriers, handset manufacturers and developers. The more revenue they will generate with the platform, the more new developers will invest in this technology. Microsoft's response will be interesting, since they would be the only other serious contender in this battle.
Control of the user is achieved through control of the device, network and content. Google is becoming quite dominant here.
Subscribe to:
Posts (Atom)