It’s no secret that I’m a big fan of my Samsung Galaxy S2, mostly because the specifications are enough to make any geek weak at the knees. It’s not just geeks that are obsessed with the phone either as Samsung has moved an impressive 10 million of them in the 5 months that its been available. Samsung has made something of a name for itself in being the phone manufacturer to have if you’re looking for an Android handset, especially when you consider Google used their original Galaxy S as the basis for their flagship phone the Nexus S. Rumours have been circulating for a while that Samsung would once again be the manufacturer of choice, a surprising rumour considering they had just sunk a few billion into acquiring Motorola.
Yesterday however saw the announcement of Google’s new flagship phone the Galaxy Nexus and sure enough it’s Samsung hardware that’s under the hood.
The stand out feature of the Galaxy Nexus is the gigantic screen, coming in at an incredible 4.65 inches and a resolution of 1280 x 720 (the industry standard for 720p). That gives you a PPI of 315 which is slightly below the iPhone 4/4S’ retina screen which comes in at 326 PPI which is amazing when you consider it’s well over an inch bigger. As far as I can tell it’s the highest resolution on a smart phone in the market currently and there’s only a handful of handsets that boast a similar sized screen. Whether this monster of a screen will be a draw card though is up for debate as not all of us are blessed with the giant hands to take full advantage of it.
Under the hood it’s a bit of a strange beast, especially when compared to its predecessors. It uses a Texas Instruments OMAP 4460 processor (dual core, 1.2GHz) instead of the usual ARM A9 or Samsung’s own Exynos SOC coupled with a whopping 1GB of RAM. The accompanying hardware includes a 5MP camera capable of 1080p video, all the usual connectivity options with the addition of NFC and wireless N and, strangely enough, a barometer. The Galaxy Nexus does not feature expandable storage like most of its predecessors did, instead coming in 16GB and 32GB variants. All up it makes for a phone that’s definitely a step up from the Galaxy S2 but not in every regard with some features on par or below that of the S2.
Looking at the design of the Galaxy Nexus I couldn’t help but notice that it had sort of regressed back to the previous design style, being more like the Galaxy S rather than the S2. As it turns out this is quite deliberate as Samsung designed the Galaxy Nexus in such a way as to avoid more lawsuits from Apple. It’s rather unfortunate as the design of the Galaxy S2 is really quite nice and I’m not particularly partial to the rounded look at all. Still I can understand why they want to avoid more problems with Apple, it’s a costly exercise and neither of them are going to come out the other side smelling of roses.
Hand in hand with the Galaxy Nexus announcement Google has also debuted Ice Cream Sandwich, the latest version of the Android OS. There’s a myriad of improvements that I won’t go through here (follow the link for a full run down) but notable features are the ability to unlock your phone by it recognizing your face, integrated screen capture (yes, that hasn’t been a default feature for this long), a NFC sharing app called Android Beam and a better interface for seeing how much data you’re using that includes the ability to kill data hogging apps. Like the Galaxy Nexus itself Ice Cream Sandwich is more of an evolutionary step rather than being revolutionary but it looks like a worthy compliment to Google’s new flagship phone.
The Galaxy Nexus shows that Samsung is very capable of delivering impressive smart phones over and over again. The hardware, for the most part, is quite incredible bringing features to the table that haven’t yet been seen before. Ice Cream Sandwich looks to be a good upgrade to the Android operating system and coupled with the Galaxy Nexus the pair will make one very desirable smart phone. Will I be getting one of them? Probably not as my S2 is more than enough to last me until next year when I’ll be looking to upgrade again, but I can’t say I’m not tempted 😉
It was just under 2 years ago when I wrote my first (and only) post on smartphone virtualization approaching it with the enthusiasm that I do with most cool new technologies. At the time I guessed that VMware would eventually look to integrate this idea with some of their other products, in essence turning user’s phones into dumb terminals so that IT administrators could have more control over them. However the exact usefulness was still not clear as at the time most smartphones were only just capable of running a single instance, let alone another one with all the virtualization trimmings that’d inevitably slow it down. Android was also somewhat of a small time player back then as well having only 5% of the market (similar to Windows Phone 7 at the same stage in its life, funnily enough) making this a curiosity more than anything else.
Of course a lot has changed in the time between that post and now. Then market leader, RIM, is now struggling with single digit market share when it used to make up almost half the market. Android has succeeded in becoming the most popular platform surpassing Apple who maintained the crown for many years prior. Smartphones have also become wildly more powerful as well, with many of them touting dual cores, oodles of RAM and screen resolutions that would make my teenage self green with envy. With this all in mind then the idea of running some kind of virtualized environment on a smartphone doesn’t seem all that ludicrous any more.
Increasingly IT departments are dealing with users who want to integrate their mobile devices with their work space in lieu of using a separate, work specific device. Much of this pressure came initially from the iPhone with higher ups wondering why they couldn’t use their devices to access work related data. For us admin types the reasons were obvious: it’s an unapproved, untested device which by rights has no business being on the network. However the pressure to capitulate to their demands was usually quite high and work arounds were sought. Over the years these have taken many various forms, but the best answer would appear to lie within the world of smartphone virtualization.
VMware have been hard at work creating full blown virtualization systems for Android that allow a user to have a single device that contains both their personal handset as well as a secure, work approved environment. In essence they have an application that allows them to switch between the two of them, allowing the user to have whatever handset they want whilst still allowing IT administrators to create a standard, secure work environment. Android is currently the only platform that seems to support this wholly thanks to its open source status, although there are rumours of it coming to the iOS line of devices as well.
It doesn’t stop there either. I predicted that VMware would eventually integrate their smartphone virtualization technology into their View product, mostly so that the phones would just end up being dumb terminals. This hasn’t happened exactly, but VMware did go ahead and imbue their View product with the ability to present full blown workstations to tablet and smartphones through a secure virtual machine running on said devices. This means that you could potentially have your entire workforce running off smartphones with docking stations, enabling users to take their work environment with them wherever they want to go. It’s shockingly close to Microsoft’s Three Screens idea and with Google announcing that Android apps are now portable to Google TV devices you’d be forgiven for thinking that they outright copied the idea.
For most regular users though these kinds of developments don’t mean a whole lot, but it is signalling the beginning of the convergence of many disparate experiences into a single unified one. Whilst I’m not going to say that anyone one platform will eventually kill off the other (each one of the three screens has a distinct purpose) we will see a convergence in the capabilities of each platform, enabling users to do all the same tasks no matter what platform they are using. Microsoft and VMware are approaching this idea from two very different directions with the former unifying the development platform and the latter abstracting it away so it will be interesting to see which approach wins out or if they too eventually converge.
I’m pretty fiscally conservative when it comes to my own cash, agonizing over purchases for sometimes weeks at a time before I take the plunge. It’s enough to outright kill some purchases entirely like the Motorola Xoom that I was convinced was worth at least having around just for the “tablet experience” but couldn’t seem to pass my financial filter. There are however times when my inner geek becomes so impressed with something that it overwhelms any sort of fiscal responsibility and I’ll find myself in possession of my object of desire well before I realize that I’ve taken my credit card out of my wallet. The Samsung Galaxy S2 is a brilliant example of this as I had been looking for a new phone for a while (and the Windows Phone 7 handsets available weren’t wowing me) and a quick trip to the specification sheet had me deep in geek lust, and 3 days later I had one in my hands.
The Galaxy S2 is really another world away from any other handset that I’ve had the pleasure of using. It’s quite a wide unit with the main screen measuring an impressive 4.3″ (10.92cm) across the diagonal but it’s also incredibly slim, being only 8.49mm thick. It’s also incredibly light weighing in at a tiny 116g which you’d think would make it feel cheap when compared to other similar handsets (the iPhone 4 is much more meatier) but the construction of the handset is very solid despite it being entirely plastic. The front screen is Gorilla glass which is incredibly resistant to scratches. I haven’t had a single scratch on it despite dropping it a couple times and putting it in my pocket with my keys by accident, something that would’ve ruined a lesser phone. To say that the first impressions of just holding the handset are impressive is putting it lightly, it’s simply an incredible device to hold.
In fact coming directly from an iPhone to the Galaxy S2 I can see why Samsung is in hot water with Apple over this particular device. I’ve covered the TouchWiz interface being strikingly similar to iOS in my Android review but the handset itself is also very Applesque, sporting the same single physical button on the front right in the same location that Apple has. Although its hard to accuse them of outright copying Apple since you can only get so creative with large touchscreen devices, especially when some of the required buttons are dictated by the underlying OS.
Under the hood of this featherweight device lies immense processing power, a multitude of connectivity options and enough sensors to make privacy nuts go wild with lawsuits. To give you an idea of just how jam packed the Galaxy S2 is here’s a breakdown of the specifications:
As you can see it actually stands up quite well when compared to my Sony. The video and picture quality is very comparable, especially in well lit situations. However it does fall down in low light and any time there’s motion due to the smaller CMOS sensor and lack of image stabilization. The LED flash on it is also incredibly harsh and will likely wash out any low light photo you attempt to take with it, but it does make for a decent little flash light. It won’t outright replace my little pocket cam any time soon but it’s definitely a good stand in when I don’t have (or don’t want to carry) it with me.
The everyday usability of the Galaxy S2 is also quite good for someone like me who has large hands (…ladies 😉 and used to struggle somewhat with the smaller screens on other handsets. However one gripe I do have with the handset is the lack of physical buttons for the options and back buttons for Android. The Galaxy S2 opts instead for 2 capacitive buttons either side of a the physical home button which does give the device a much sleeker look but can also mean accidental button touches should you brush against them. Samsung has also opted to put the power button on the side of the handset instead of the traditional placement on top near the headset port, which takes a little getting used to but is quite usable.
Where the stock Galaxy S2 falls down however is in its battery life. With moderate usage the battery wouldn’t make it through a second day requiring me to keep it plugged in most days whilst I was work lest it die on me overnight when I went home. This could have been the deal breaker for this phone as whilst I’m not the forgetful type I do like to be confident that I can make it through the day without having to watch the battery meter like a hawk. Thankfully the guys over at XDA Developers came to the rescue again with their custom ROM for the Galaxy S2 called VillainROM. After going through the process of doing the upgrade my battery now lasts about twice as long as it used to, only needing charging once or twice a week. I’ve yet to run Advanced Task Killer to attempt to squeeze even more battery life out of my handset, but it’s good enough for the time being.
It should come at no surprise then that this has been a wildly popular handset with both the tech and non-tech crowd a like. In the 3 months since its release the Galaxy S2 has sold a whopping 6 million units and just anecdotally it seems nearly every single one of my friends who was looking for a new phone has got one as well as almost half of my workmates. I used to laugh at anyone who touted any smartphone as an iPhone killer but with the Galaxy S2 not even being available in the USA yet and already garnering such a massive reception it might be the very first single phone that will be able to come close to touching Apple’s numbers. Of course I don’t believe for a second that any single Android handset will be able to take down the iPhone, not for a while at least.
The Samsung Galaxy S2 has set the bar as to what smart phones should be capable of and it will be the gold standard with which all are compared to for a long time coming. The combination of elegant design, incredible power and features galore make the Galaxy S2 stand out from the crowd in a big way, so much so that buying any other handset seems illogical. For many it has the potential to replace several other devices with its top notch multimedia components, further improving the overall value that you can derive from this handset. Overall the Samsung Galaxy S2 is a wonderfully impressive device and if you’re in the market for a new smart phone I really can’t recommend it enough.
For the past year I was somewhat of an anomaly amongst my tech friends because I choose to get an iPhone 3GS instead of one of the Android handsets. The choice was simple at the time, I had an app that I wanted to develop for it and needed something to test on, but still I copped it sweet whenever I said something positive about the platform since I’d usually be the only one with an Apple product in the area. When it came time again to buy a new phone, as I get to do every year for next to nothing, I resisted for quite a while, until one of my friends put me onto the Samsung Galaxy S2¹. The tech specs simply overwhelmed my usual fiscal conservativeness and no less than a week later was I in possession of one and so began my experience with the Android platform.
The default UI that comes with all of Samsung’s Android handsets, called TouchWiz, feels uncannily similar to that of iOS. In fact it’s so familiar that Apple is suing Samsung because of it, but if you look at many other Android devices you’ll see that they share similar characteristics that Apple is claiming Samsung ripped off from them. For me personally though the Android UI wins out simply because of how customizable it is allowing me to craft an experience that’s tailored to my use. Widgets, basically small front ends to your running applications, are a big part of this enabling me to put things like a weather ticker on my front page. The active wallpapers are also pretty interesting too, if only to liven up the otherwise completely static UI.
What impresses me most about the Android platform is the breadth and depth of the applications and tweaks available for the system. My first few days with Android were spent just getting myself back up and running like I was on my iPhone, finding all the essential applications (Facebook, Twitter, Shazam, Battle.net Authenticator, etc) and comparing the experience to the iPhone. For the most part the experience on Android is almost identical, especially with applications that have large user bases, but some of them were decidedly sub-par. Now most would say that this is due to the fragmentation of the Android platform but the problems I saw didn’t stem from those kinds of issues, just a lack of effort on their part to polish the experience. This more often happened for applications that weren’t “Android born” as many of the native apps were leaps and bounds ahead of them in terms of quality.
The depth of integration that applications and tweaks can have with the Android platform is really where the platform shines. Skype, for example, can usurp your outgoing calls and route them through their network which could be a major boon if you’re lucky enough to have a generous data plan. It doesn’t stop with application integration either, there are numerous developers dedicated to making the Android platform itself better through custom kernels and ROMs. The extra functionality that I have unlocked with my phone by installing CF-Root kernel, one that allows me root access, are just phenomenal. I’ve yet to find myself wanting for any kind of functionality and rarely have I found myself needing to pay for it something, unless it was for convenience’s sake.
Android is definitely a technophile’s dream with the near limitless possibilities of an open platform laid out before you. However had you not bothered to do all the faffing about that I did you still wouldn’t be getting a sub-par experience, at least on handsets sporting the TouchWiz interface. Sure you might have to miss out on some of the useful apps (like Titanium Backup) but realistically many of the root enabled apps aren’t aimed at your everyday user. You still get all the benefits of the deep integration with the Android platform where a good 90% of the value will be for most users anyway.
Despite all of this gushing over Google’s mobile love child I still find it hard to recommend it as the platform for everyone. Sure for anyone with a slight technical bent it’s the platform to go for, especially if you’re comfortable modding your hardware, and sure it’s still quite usable for the majority who aren’t. However Apple’s platform does automate a lot of the rudimentary stuff for you (like backing up your handset when you sync it) which Android, as a platform, doesn’t currently do. Additionally thanks to the limited hardware platform you’re far less likely to encounter some unknown issue on iOS than you are on Android which, if you’re the IT support for the family like me, can make your life a whole lot easier.
Android really impressed me straight from the get go and continued to do so as I spent more time getting to know it and digging under the hood to unlock even more value from it. The ability to interact, modify or outright replace parts of the underlying Android platform is what makes it great and is the reason why it’s the number 1 smart phone platform to date. As a long time smart phone user I feel that Android is by far the best platform for both technophiles and regular users alike, giving you the usability you’ve come to expect from iOS with the tweakability that used to be reserved for only for Windows Mobile devices.
Now I just need to try out a Windows Phone 7 device and I’ll have done the mobile platform trifecta.
¹I’m reviewing the handset separately as since Android is available on hundreds of handsets it wouldn’t be fair to lump them together as I did with the iPhone. Plus the Galaxy S2 deserves its own review anyway and you’ll find out why hopefully this week 😉
You know I was pretty hyped about getting a WP7 handset after having a short play with one in the store. The slick interface and overall usability of it was so high that I thought it was worth a shot and I had really nothing to lose since my work would be paying for it. The NoDo update was on the horizon however so I decided that I’d hold back until it made its way into production so that I wouldn’t have to deal with the same frustrations that day 0 customers had. Most notably this would be the inclusion of copy and paste, but there were also a few other fixes that I thought would be good to have and worth the wait.
The problem is however that unlike regular Windows patching there’s a gate keeper between me and Microsoft’s patches for their new mobile platform. You see the patches have to pass muster with the carriers first before they can be distributed to the handsets although Microsoft had said in the past that they were working with them to make the process as quick as possible. Unfortunately for us Australian customers looking for a WP7 handset you really only have one carrier to go with: Telstra. Now this wouldn’t be so much of a bad option normally since Telstra had to start playing straight after their retail and wholesale arms were broken apart but it seems that they’re not up to the job of testing WP7 updates:
Universal availability of the copy-and-paste update to Windows Phone 7, codenamed NoDo, is almost here, according to Microsoft’s latest schedule update. The final unpatched phone available in the US market, the HTC Surround sold by AT&T should start to receive its updates within the next ten business days. The network’s other two handsets, the Samsung Focus and LG Quantum, have been receiving updates since last week.
European carrier Deutsche Telekom (which includes T-Mobile UK) has at last finished its testing, as has Australian carrier Optus. Updates from phones on these networks should also appear within the next ten business days or so. This leaves only two carriers still delaying the updates due to “testing”: Telefonica, in Spain, and Telstra, in Australia.
This was the one area where I was expecting Microsoft to shine through since their bread and butter products have depended so heavily on their patch services for well over a decade. Sure the vast majority of the blame should be leveled at the carriers since they’re the ones causing the delays, but Microsoft isn’t innocent of incurring delays either. Of course the original iPhone and Android handsets weren’t immune to problems like this either but I had expected Microsoft’s late coming to the party to be at least coupled with a strong patch and feature release scheme so they could play catch up quickly.
It might seem like an extraordinarily small gripe considering the rest of the platform looks solid but when minor feature releases like this take so long to get through the pipeline it makes me wonder just how long I’ll have to wait for the next update, codenamed Mango, to drop. Amongst other things Mango will bring full HTML5 support to WP7 something which it currently lacks in its browser. Whilst the IE9 implementation of HTML5 does leave some things to be desired (my newest app idea uses HTML5 bits, and IE9 mangles it) it is a lot better than not having it at all, especially when so many mobile versions of sites rely on HTML5 functionality. With speculation now brewing that this update might slip to next year that’s starting to put WP7 at a serious disadvantage, unless some enterprising browser developer ports to WP7 ala Opera et al.
I’m still planning to nab myself one of these handsets if only for the few times I’ll want to try my hand at developing an application for it but with such delays piling up on each other I could very well see myself changing to Android or back to iOS until they’re finished playing the catch up game. I’m sure as time goes on they’ll develop a much better relationship with the carriers and hopefully they’ll be able to leverage that to remove some of the roadblocks to getting patches and updates out to us consumers. Until then however WP7 users are going to be at the whim of the carriers, even more so than they are normally.
The world of mobile gaming is a curious one. It’s roots date back well over decade but it’s only really come into its own in the past few years as smartphones became capable enough and there were platforms available to support it. The industry blossomed on the backs of the small and independent developers who took advantage of the low barriers to entry to be able to release their games on the platform and is now a multi-billion dollar industry. As a traditional gamer I was a bit sceptical that it would amount to anything more than just another time waster platform, my opinion only changing after buying Infinity Blade which I thoroughly enjoyed. Still I’m a firm believer that the mobile platform, whilst definitely a successful industry, is not killing other platforms as you just can’t recreate the same experience on a tablet or handheld as you can with a PC or a console.
Of course the large game developers and publishers are concerned about how what the future of their business will look like. With mobile gaming carving out a good chunk of the games industry in such a small amount of time (about 6.4% of all games industry revenue) and social networking games grabbing about the same it really shouldn’t come as a surprise that they might be worried about it. Recently Mike Capps, president of Epic who create the Unreal engine, went on record saying that the flood of 99 cent games was killing them:
“We have not been this uncertain about what’s coming next in the games industry since Epic’s been around for 20 years. We’re at such an inflection point. Will there be physical distribution in 10 years or even five? Will anyone care about the next console generation? What’s going on in PC? Can you make money on PC if it’s not a connected game? What’s going on in mobile?
“If there’s anything that’s killing us [in the traditional games business] it’s dollar apps,” he lamented. “How do you sell someone a $60 game that’s really worth it … They’re used to 99 cents. As I said, it’s an uncertain time in the industry. But it’s an exciting time for whoever picks the right path and wins.”
If you take into consideration the vast majority of people who play games on their phones don’t play games on other platforms¹ then it makes sense that you can’t sell them a $60 game because the platform just isn’t suited to that kind of title. Sure people may spend a good chunk of time playing games on their mobiles (rivalling the amount of time spent on more traditional titles) but it’s in no way comparable. Most of the time spent on mobile games is done in fits and bursts as the platform is aptly tuned to, rather than the long continuous sessions that PC and console gamers are more accustomed to. In essence if you’re a traditional game developer or publisher looking to push your wares onto the mobile market you’re not going to be building the same kind of products, nor are you going to be charging the same price.
Additionally the mobile gaming industry is in no way killing any of the other platforms. Consoles are by far the kings of the industry bringing in over 40% of the total revenue with PCs still making up a good 20% (and is even growing despite the heavy competition). Sure mobile games have brought some disruption to the industry and have given pause to many developers and publishers who are trying to gauge where the industry is heading. Frankly though if you think that there’s no future left in the classic $60 titles then you deserve to go out of business, since the industry figures just don’t support that view.
I do agree with Capps’ claim that we’re at an inflection point where the games industry is facing quite a few fundamental changes. Just like the music and film industries before them though they will need to adapt to these market changes or face dying a slow death as they attempt to shoe horn their business models into the new world. I do believe that the games industry is far better poised to adapt and innovate with these market disruptions than their more traditional media outlets were and that was proven by just how fast mobile gaming caught on as a mainstream phenomenon. Still mobile gaming is a long, long way from killing off the traditional gaming sector and realistically it has a lot of growing up to do before it would ever have a chance at doing so.
¹I tried my darnedest to find some solid numbers on this and couldn’t find anything substantial. I stand by the sentiment though as from my personal viewpoint the vast majority of people who are mobile gamers are solely dedicated to that platform and don’t play games anything else.
So I’m sold on the tablet idea. After resisting it since Apple started popularizing it with the iPad I’ve finally started to find myself thinking about numerous use cases where a tablet would be far more appropriate than my current solutions. Most recently it was after turning off my main PC and sitting down to watch some TV shows, realizing that I had forgotten to set up some required downloads before doing so. Sure I could do them using the diNovo Mini keyboard but it’s not really designed for more than logging in and typing in the occasional web address. Thinking that I’d either now have to power my PC or laptop on I lamented that I didn’t have a tablet that I could RDP into the box with and set up the downloads whilst lazing on the couch. Thankfully it looks like my tablet of choice, a wifi only Xoom, can be shipped to Australia via Amazon so I’ll be ordering one of them very soon.
Initially I thought I’d go for one of the top of the line models with all the bells and whistles, most notably a 3G/4G connection. That was mostly just for geek cred since whenever I’m buying gadgets I like to get the best that’s on offer at the time (as long as the price isn’t completely ludicrous). After a while though I started to have a think about my particular use patterns and I struggled to find a time where I’d want to use a tablet and be bereft of a WiFi connection, either through an access point or tethered to my phone. There’s also the consideration of price with all non-cellular tablets is usually quite a bit cheaper, on the order of $200 with the Xoom. It then got me thinking, what exactly is the use case for a tablet with a cellular connection?
The scenarios I picture go something along these lines. You’re out and about, somewhere that has mobile phone reception, but you don’t have your phone on you (or one not capable of tethering) and you’re no where near a WiFi access point. Now the possibility of having mobile phone reception but no WiFi is a pretty common event, especially here in Australia, but the other side to that potential situation is you either can’t tether to your mobile phone because its not capable or you don’t have it on you. Couple that with the fact that you’re going to have to pay for yet another data plan just for your new tablet then you’ve really lost me as to why you’d bother with a tablet that has cellular connectivity.
If your reason for getting cellular connectivity is that you want to use it when you don’t have access to a WiFi hard point then I could only recommend it if you have a phone that can’t tether to other devices (although I’d struggle to find one today, heck even my RAZR was able to do it). However, if I may make a sweeping statement, I’d assume that since you’ve bought a tablet you already have a smart phone which is quite capable of tethering, even if the carrier charges you a little more for it (which is uncommon and usually cheaper than a separate data plan). The only real reason to have it is for when you have your tablet but not your phone, a situation I’d be hard pressed to find myself in and not be within range of an access point.
In fact most of the uses I can come up with for a tablet device actually require them to be on some kind of wireless network as they make a fitting interface device to my larger PCs with all the functions that could be done on cellular networks aptly covered off by a smartphone. Sure they might be more usable for quite a lot of activities but they’re quite a lot more cumbersome than something that can fit into my pocket and rarely do I find myself needing functionality above that of the phone but below that of a fully fledged PC. This is why I was initially skeptical of the tablet movement as the use cases were already aptly covered by current generation devices. It seems there’s quite a market for transitional devices however.
Still since nearly every manufacturer is making both cellular and wireless only tablets there’s got to be something to it, even if I can’t figure it out. There’s a lot to be said about the convenience factor and I’m sure a lot of people are willing to pay the extra just to make sure they can always use their device wherever they are but I, for one, can’t seem to get a grip on it. So I’ll put it out to the wisdom of the crowd: what are your use cases for a cellular enabled tablet?
Whilst the only current smartphone platform I’ve had any decent experience with is Apple’s iPhone I’m still not completely tied to it. Sure the platform is great and I’ll always be keeping an iOS device around for as long as I keep developing for the platform but my next handset purchase is more than likely not going to be another Apple device. The case is strong for a Windows Phone 7 handset thanks to its great tool set and general esoteric-ness (I don’t yet know anyone who’s bought one) but that same air of mystery is a double edged sword. Sure most of my general applications will be available on it, like Twitter and Facebook, but past that there’s not a whole lot of interest in the platform.
It’s not surprising really considering that slice of the mobile market pie that Microsoft commands is only a mere 5.5% according to the IDC, which includes all handsets that come under the Windows umbrella. The nearest rival to them is RIM (creator of the Blackberry handset series) who nearly triple their share at a whopping 14.9% and even they don’t seem to command a 3rd party developer army comparable to that of Android or Google. Still with them sealing the deal on a partnership with Nokia recently the IDC has reported that Microsoft’s WP7 platform will begin to surge ahead, overtaking iOS and being second only to Android.
The intial reaction to this was of course, utter disbelief:
In the close to six months that WP7 has been available, it has failed to set sales on fire. In fact, Microsoft hasn’t provided any metrics on how many WP7 handsets have been sold. Also, the 5.5% market share that Microsoft has now represents both WP7 and the old Windows Mobile 5.x and 6.x systems, which are still being sold on enterprise handhelds.
Further, Microsoft has stumbled badly with the first two system updates for its smartphone platform. First by delaying it for nearly two months, and second by bungling the actual delivery of the updates. Things are not going so smoothly for Microsoft. Heck, WP7 champion Joe Belfiore actually wrote a public apology to its WP7 customers about the whole update debacle.
Zeman makes some good points about the WP7 ecosystem and the troubles Microsoft has faced in dragging their Windows Mobile platform into the modern age. The sales figures aren’t that impressive when you compare them to iOS and Android, heck they’re not even that impressive compared to single handsets on either platform. Still this ignores the fact that WP7 is still a nascent platform and it will be a while before it reaches the maturity level that everyone’s expecting of it. If we’re fair and compare the initial WP7 sales to the initial release of Android you’ll actually find them quite comparable with the G1 selling some 600,000 handsets in the first couple months and WP7 cracking 1.5 million in its first 6 weeks. It took quite a while for Android and even the iPhone to hit the fever pitch that they have today so the current market share of WP7 devices shouldn’t really come as a surprise.
I can’t provide an excuse for their botched update schedule however. Apple seems to be the only major competitor that’s nailed this completely with Android and WP7 both suffering from the same carrier induced delays and fragmentation problems. It’s actually one of the reasons why I haven’t already lashed out for a WP7 handset since the main carrier of them here in Australia, Telstra, is still testing the pre-update update and has no schedule for the release of the coveted Nodo update. Since there doesn’t seem to be any way to route around the carrier and install the patch manually (although I’ll admit I haven’t done a ton of research on this) it means I’m wholly dependent on someone other than Microsoft to get my handset updated. With Telstra’s track record that doesn’t exactly inspire much confidence in the platform.
Both Android and iOS faced similar problems in their infancy and I’m sure WP7 will be able to overcome them in the future. Whether it will become the second most popular platform though remains to be seen as whilst the Nokia relationship means they have a strong possibility of gaining some serious traction it’s not a sure bet that every current Symbian customer will convert over to WP7. With Microsoft being particularly coy about their sales figures its hard to get a good reading of how their new mobile platform is trending but it will definitely be interesting to see how their market share changes as Nokia begins releasing their WP7 handsets.
The date is fast approaching April and that means the Fringe Benefits Tax year is about to roll over. For most people this is a non-event unless you’re salary sacrificing a car but for contractors like me it means I can write off another phone and laptop device on tax, effectively getting them for half the market price. Whilst it’s not as good as it used to be (you were also able to depreciate them, making said devices basically free) there hasn’t been a year yet when I haven’t taken advantage of at least getting a new phone, and last year was the first when I purchased my Macbook Pro. So of course I’ve spent the last couple weeks looking through the available selection of phones and tablets with which to gorge myself upon and the more I look the more I get the feeling I won’t be able to leave my iPhone behind like I did with my other smart phones.
The tablet choice is pretty easy since I’m not particularly fond of the iPad (I don’t need another iDevice) and getting something like the Motorola Xoom would cover off my need for an Android device to code against. To have all current platforms covered then the smart phone choice (HA! See what I did there?) would be a Windows Phone 7 handset. Taking a look around I found a few pretty good deals on various handsets with contracts comparable to what I’m on now with tons of extra value. My handset of choice is the HTC Mozart which appears to be the cream of the current crop of WP7 handsets, anything else is just too far off on the horizon to be worth considering.
Of course whenever I’m contemplating a new phone I’ll always compare it to what I currently have to see if it fixes the things that bug me and whether or not it will be worth it. Whilst my 3GS is less than a year old it’s nipping on the feet of being 2 generations behind the current trend so any recent handset should beat it hands down. A quick look at the similarly priced handsets shows this to be true all of them bristling with bigger CPUs, more RAM and better dedicated graphics. Unfortunately however there’s one thing that all the other handsets I’ve been looking at don’t cover.
That unfortunate beast is the Apple App Store.
Despite the insane growth that Android has shown over the past year Apple is still the platform of choice for many early adopters and developers. It’s extremely rare for a company to attempt to launch a mobile application on anything but Apple first, simply because the user base tends much more towards that early adopter mindset of trying things out. Sure there are many examples of popular apps that made their debut on the Android markets (although none that I’m aware of for WP7) but when you compare them to the number of success Apple can count using its platform there’s really no contest. Couple that with the fact that despite Android’s runaway popularity the App store is still by far more profitable for developers looking to sell their wares and you’d really have to be crazy not to launch on their platform.
For me this presents an interesting conundrum. Whilst I was never going to sell my 3GS since it will make a good test bed for at least another year or two I do use it quite extensively to test out potential competitor’s applications. Since most of them launch on iPhone first this hasn’t been a big deal but with me planning to move to WP7 (or possibly Android) for my main handset I can’t help but feel that I’ll probably want to keep it on hand so that I can keep a close eye on the market. Sure I could just make a note to try an application later but many up and coming products are based around using them for a particular purpose, not booting them up occasionally to see the new features. Granted this is probably limited to social applications but any new product is almost guaranteed to have some kind of social bent baked in (heaven knows I tried to avoid it for the longest time with Lobaco).
The market could change and with the growth that Android is experiencing I may be singing a completely different tune a year from now. Still until the Android store starts pumping out billions of dollars to its developers I can’t see a future where any serious developer isn’t focused primarily on Apple first with Android planned down the line. For now I think I’ll stick with my plan of a WP7 phone and an Android tablet, keeping the gaggle of devices close at my side at all times so that I can test any app regardless of its platform. It’s the same line of thinking that lead me to buy every major console, although the Wii has only ever been used a couple times.
There’s an analogy in there somewhere 😉
I’ve had quite a few phones in my time but only 2 of them have ever been Nokias. The first was the tiny 8210 I bought purely because everyone else was getting a phone so of course I needed one as well. The second was an ill-fated N95 which, despite being an absolutely gorgeous media phone, failed to work on my network of choice thanks to it being a regional model that the seller neglected to inform me about. Still I always had a bit of a soft spot for Nokia devices because they got the job done and they were familiar to anyone who had used them before, saving many phone calls when my parents upgraded their handsets. I’ve even wondered loudly why developers ignore Nokia’s flagship mobile platform despite it’s absolutely ridiculous install base that dwarfs all of its competitors, acknowledging that it’s mostly due to their lack of innovation on the platform.
Then on the weekend a good friend of mine tells me that Nokia had teamed up with Microsoft to replace Symbian with Windows Phone 7. I had heard about Nokia’s CEO releasing a memo signalling drastic changes ahead for the company but I really didn’t expect that to result in something this drastic:
Nokia CEO Stephen Elop announced a long-rumored partnership with Microsoft this morning that would make Windows Phone 7 Nokia’s primary mobile platform.
The announcement means the end is near for Nokia’s aging Symbian platform, which many (myself included) have criticized as being too archaic to compete with modern platforms like the iPhone OS or Android. And Nokia’s homegrown next-generation OS, MeeGo, will no longer be the mythical savior for the Finnish company, as it’s now being positioned more as an experiment.
We’ve argued for some time that a move to Windows Phone 7 would make the most sense for Nokia, and after Elop’s dramatic “burning platform” memo last weekend, it was all but certain that the company would link up with Microsoft.
It’s a bold move for both Nokia and Microsoft as separated they’re not much of a threat to the two other giants in the mobile industry. However upon combining Nokia is ensuring that Windows Phone 7 reaches many more people than it can currently, delivering handsets at price ranges that other manufacturers just won’t touch. This will have a positive feedback effect of making the platform more attractive to developers which in turn drives more users to come to the platform when their applications of choice are ported or emulated. Even their concept phones are looking pretty schmick:
The partnership runs much deeper than just another vendor hopping onto the WP7 bandwagon however. Nokia has had a lot more experience than Microsoft in the mobile space and going by what is said in an open letter that the CEOs of both companies wrote together it looks like Microsoft is hoping to use that experience to further refine the WP7 line. There’s also a deep integration in terms of Microsoft services (Bing for search and adCenter for ads) and interestingly enough Bing Maps won’t be powering Nokia’s WP7 devices, it will still be OVI Maps. I’m interested to see where this integration heads because Bing Maps is actually a pretty good product and I was never a fan of the maps on Nokia devices (mostly because of the subscription fee required). They’ll also be porting all their content streams and application store across to the Microsoft Marketplace which is expected considering the level of integration they’re going for.
Of course the question has been raised as to why they didn’t go for one of the alternatives, namely their MeeGo platform or Google Android. MeeGo, for all its open source goodness, hasn’t really experienced the same amount of traction that Android has and has firmly been in the realms of “curious experiment” for the past year, even if Nokia is only admitting to it today. Android on the other hand would’ve made a lot of sense, however it appears that Nokia wanted to be an influencer of their new platform of choice rather than just another manufacturer. They’d never get this level of integration from Google unless they put in all the work and then realistically that does nothing to help the Nokia brand, it would all be for Google. Thus WP7 is really the only choice with these considerations in mind and I’m sure Microsoft was more than happy to welcome Nokia into the fray.
For a developer like me this just adds fuel to the WP7 fire that’s been burning in my head for the past couple months. Although it didn’t take me long to become semi-competent with iPhone SDK the lure of easy WP7 development has been pretty hard to ignore over the past couple months, especially when I have to dive back into Visual Studio to make API changes. Nokia’s partnership with Microsoft means that there’s all the more chance that WP7 will be a viable platform for the long term and as such any time spent developing on it is time well spent. Still if I was being truly honest with myself I’d just suck it up and do Android anyway but after wrangling with Objective-C for so long I feel like I deserve a little foray back into the world of C# and Visual Studio goodness and this announcement justifies that even more.