Posts tagged "android"
Arguably, 2010 was the year of the iPad. It became the executive’s new computer and the parent’s new babysitter. For my business, it’s been the primary device of interest for developing new applications, with most of the apps we build for customers now being iPad applications.
My take coming into 2011 was that it had the potential to be the year of the tablet. CES showed that promise with a number of Android-powered devices set to hit stores, with the Motorola XOOM, LG G-Slate, and Toshiba Folio 100 representing the leading candidates. These tablets really only are possible because of Google’s unveiling of the tablet-optimized Android 3.0 aka Honeycomb. And last week, it was finally showcased to the public. Generally, I’m excited about the update. As a whole, however, I’m concerned about the success of Android tablets in the consumer market and what this means for developing android tablet applications:
1. Costs are too high.
The iPad isn’t cheap but with initial prices for devices like the Motorola XOOM coming in at $800+, comparatively the iPad looks like a steal.
2. Too many options.
With a minimum of 3-4 options to choose from, and many, many more flooding the market, consumers aren’t going to know the right Android tablet to purchase. That’s especially important because they really won’t understand what they are getting comparative to an iPad.
3. No clear winners.
A corollary to the second point. Even with a number of more compelling Android tablets set to launch in Q1 and early Q2, it’s going to take some time to get numbers on what kind of distribution they collectively reach. More importantly, we’ll not know if there is clear winner and a de facto Android alternative to the iPad till mid-2011 at the earliest.
4. Fragmentation following Android onto the tablet.
Motorola XOOM – 10.1”
LG G-Slate – 8.9”
Samsung Galaxy Tab – 7”
The display sizes alone for potential leading Android tablets reveal that developing across these devices is not a trivial task. Then consider the more significant resolution and hardware internals differences.
5. iPad 2
It’s very likely the iPad 2 will launch somewhere between March and April. It will largely be a revision with it being expected to be sleeker, including a front-facing camera, and a faster processor. Still, a revision on a top selling device, which is priced more competitively than alternatives, could be trouble for these fledgling Android tablets.
What It Means
The primary buyers of the initial versions of Android tablets are going to be early technology adopters. Thus, I do not recommend most organizations proceeding with building consumer-focused Android tablet applications for the first part of 2011. Some of the exceptions to this guidance include game studios and large publishers. But even for those groups, they need to proceed with caution and focus on the perceived device winners (my early pick, as with others, is the Motorola XOOM).
Where’s the Opportunity
If I were a manufacturer, I’d likely not engage in the crowded consumer tablet arena. Instead, I’d focus on developing Android devices that can be used in the enterprise market (i.e., behind firewalls) and in field operations. That’s also where the opportunity is for Android developers, although it’s difficult to break into these markets without having established relationships.
Similarly, organizations may want to develop direct partnerships with Android tablet providers. These types of relationships could provide better pricing and open up additional customizations to the hardware itself.
Although I am concerned about rumors that the Motorola XOOM’s Wi-Fi will be disabled without purchasing a data plan, it’s the Android tablet I’m currently planning to purchase. That could change if the rumors hold true (and there’s no way to cancel the data plan). In any case, I will report back with my Android 3.0 experiences and with what we are working on for these tablets.
No, it’s not a predictions post. It would be too late for that anyway, right (this year, they got started in September!)? Instead, I want to focus on some key numbers to pay attention to throughout 2011, as well as some not so key ones. Please, do yourself a favor…pay special attention to the ones that don’t matter and any time you see an article about them, don’t waste your time reading it.
1. Two U.S. carriers for the iPhone.
It’s important news for iOS developers, regardless of location. Conservatively, iOS app sales could increase by 5-7% over the next year based on how quickly Verizon is likely to ramp up sales.
2. The number of Windows Phone 7 devices that get activated.
I’m not sure there are any reliable data points on this one right now. I’ve mentioned before that I don’t know anyone with a WP7 (other than developers) and that’s still the case. It remains to be seen if WP7 can become an alternative to iOS, Android, and RIM…and if it gets enough traction to entice developers to build for it.
3. Android 3.0, Honeycomb
Android tablets—but possibly not one that you currently own—are finally going to have an operating system designed specifically for them. The update looks promising, as seen in Google’s sneak peek video.
4. Sales for “iPad killers”
In my opinion, the Samsung Galaxy Tab is still the only other option to the iPad but the Motorola XOOM appears promising. Neither are truly iPad killers but with the tablet craziness at CES this year, the numbers will inform us of the true iPad
5. Benchmarks for In App Purchase conversion rates.
Both through my discussions and other industry data points such as Urban Airship’s 2010 developer survey, it’s obvious developers are hot on In App Purchase and the freemium model. Interest for In App Purchase as a way to monetize an app has swung from 8% to 31% from 2010 to 2011. What’s needed, however, are benchmarks that provide industry standards for In App Purchase conversion rates or developers are still just guessing that this model is the best for their applications.
6. The percentage of developers building for one more than one platform.
Developers try to follow the money trail. Should there be large percentage shifts in developers, especially iOS developers, who also begin building for other platforms, that’s a key indiciator that other platforms are picking up momentum.
My take on this one: even with Android 3.0, fragmentation still presents serious problems on Android (especially due to carrier control). WP7 also would have to ship a ton of devices to make it enticing for developers. Overall, even if the numbers show building across platforms is picking up interest, I don’t see it being a breakout year for Android or WP7 consumer applications.
1. Android leading the U.S. smartphone market share.
That was known all along because Google’s strategy is about advertising, meaning it needs volume. The surprise was how fast it achieved that volume…but not that it was achieved. Remember that market share leader does not equate to most profitable or best opportunity for mobile app developers.
2. The number of apps in Apple’s iOS App Store.
Short version: there’s a lot of ’em.
Slightly longer version: What’s the difference to consumers between 300,000 or 500,000 apps? Critical mass has been reached.
3. iOS 3.x
It’s time to retire supporting iOS 3.x, especially with iOS 4.3 on its way. Apple will do it soon enough and many developers have already made this decision.
4. The number of pundits on each side of the mobile web versus mobile native debate.
This debate should have been over in 2009 but it got revved up again in 2010. There is no single winner. We need both and both are here to stay.
5. Total value of mobile app market.
There’s been several waves of the mobile app phenomena at this point. I see the next being focused on business-to-business, enterprise, and generally more “internal” tablet applications. If mobile is not a priority by now for any organization, the ever changing total value of the mobile app market guesstimated by analysts is not going to suddenly make it one.
I’ve been a big proponent of Mozilla’s Firefox and unlike many others, never made the jump to Chrome. Aside from some very cool recent innovations on the desktop side (e.g., Firefox Panorama), Firefox Mobile for Android has just moved from alpha to beta.
Having used the new beta on my Nexus One (see my brief video below), it’s exceptionally more stable than the previous alpha builds. Although there are still some issues with over-responsive navigation controls, it’s getting closer to being ready for prime time use. What really excites me about the new beta though, is that there are hints that Firefox’s vision of mobile browsing just might offer the best experience available.
That conclusion comes from trying nearly every standard or third-party browser across various mobile devices and platforms. For example, on iOS, Safari’s severely crippled with the maximum pages that can be opened, no download support, and most importantly, not allowing the content of the page to be the focus. That’s especially true on the iPad, where the URL bar and navigation controls are always present. It’s why I often will use third-party browsers like iCab Mobile or Grazing, which offer these other features.
What’s different about Firefox Mobile for Android? Aside from the myriad of reasons Mozilla engineer Matt Brubeck details, he and his colleagues have created a mobile browsing experience that most successfully overcomes the major challenge when designing for a mobile device: limited screen real estate. This challenge is really twofold. The first aspect was alluded to above, which is to the keep the content front and center. The second is less obvious and can even result from smartly approach the first: not burying navigation controls.
(See it in action on a quick video overview I put together.)
I initially saw Mozilla’s navigation concept when I demoed what was then called “Fennec” on a simulator well over a year ago. Reviewing my notes from that time, I wasn’t convinced of their paradigm, which consists of swiping right or left to access tabs and page back/forward. I liked the maximized screen real estate but it seemed the implementation of the navigation was too slow and did not provide for an easy enough way to get back and forth between web pages. I can safely write that they’ve now delivered on their original concept.
While this version of Firefox is initially only available on Android and the Nokia N900, I’d really be interested to see this run on the upcoming Samsung Galaxy Tab. Further, with Apple’s loosening of App Store restrictions, let’s get Firefox onto iOS already!
Kudos to the Mozilla team. As I concluded in my video, Firefox Mobile is a most welcome addition to any Android device.
As a speaker for Digital East, I was interviewed by Tech Journal South about mobile and native mobile apps specifically.:
“They’re looking at this year and asking how will it lead me into next year,” he says. Some firms are willing to throw some money at mobile this year, but don’t really expect much to start happening until 2011.
“Mobile is such a moving target this year,” he explains. “Tablet devices have been touted for some time as the ‘Next Big Thing,’ but didn’t really materialize until Apple introduced the iPad.”
Android device makers are very active and is surpassing Apple in the number of devices using the Google operating system and shipping daily.
So, he says, “People are just trying to keep up with what’s happening. They’re not sure if things will change drastically again this year. They want to be leaders, but they don’t want to over or under invest in something they don’t completely understand.”
Yarmosh says he sees a lot of indications that tablet computing and apps are becoming important this year. “I have my iPad with me in every meeting and that’s the only thing they’ll want to talk about.”
Jason Hiner on Android’s “dirty little secret.” Nuff said…it’s also why I bought a Nexus One directly from Google:
Just as Google is overwhelming the iPhone with over 20 Android handsets to Apple’s one device, so the army of Android phones that can be carrier-modified is overwhelming the one Apple phone on a single carrier that allows it to stand apart and not play the old carrier-dominated game that resulted in strong handsets weakened by the design, software, and pricing ploys of the telecoms.