Saturday, 2 February 2013

Chromebook Failings

It's been well over a week, and I just ain't feelin' the lurve.

The Chromebook has some concepts down that I think will take great shape in the next 10 years for how operating systems work and for what we expect from them. For example, I have this dream that any laptop I find, or desktop, mobile, phablet, whatever, I should be able to log into it and I should feel like I'm in my computer. This is how I use Google+, Facebook and all else in the cloud, so why not even my OS? Chrome OS demonstrates admirably that this is possible and that this kind of future makes total sense.

But we are not there yet. I kindly received this as a holiday gift from Google, my oh so generous employer here in Dublin, and I do receive it gratefully. However, I use it painstakingly.

This thing is slow guys. You can't just work on a desktop that is blazing by at 100mph and then expect anything close from the Chromebook. This was my dream, and perhaps this is my mistake. I envisioned an early use case for me as one where I would work on my desk from the trusty MacBook Pro, and for meetings, taking work home, working from other hot-desks/spaces around the office, the Chromebook would suit nicely, being light, unplugged, and in the cloud. While this works, it's just annoying. The trackpad is slow to respond. Clicking feels weird. The mic and speaker crackle and suck (this is solved with a trusty pair of Urban Ears, so no hard feelings). In general, you get a deep sense of gratitude when you come back to a decent laptop. I thought I was just spoiled by my MacBook Pro, which admittedly is beyond decent, it's pro. But I'm much happier on my super old black MacBook... hell, I'm even happier on my girlfriend's Windows 7 laptop than I am on this Chromebook.

These are hardware issues, and what can you expect for $250, right? A lot, it turns out. Laptops are a lot cheaper than I think they get credit for. Throw in another $100 and you save a lot of grief that comes with the Chromebook. This laptop is priced cheap, but not cheap enough. It should be a $100 laptop; a sort of throwaway that you think about as an add-on when you buy a real one.

Not to say that all is bad. The future looks good, and I think that Google's idea here is right. Computers need less in them than they did before, so we need to start thinking about devices that work entirely in the cloud, with some reserved local features. What I love particularly about Chrome OS is how some apps, Hangouts for example, look and act like native applications, rather than something running in the browser. I think with Google working on new ideas for hosted apps and web apps, we'll start seeing traditionally web based services more like the main function of the computer. I think a lot of users probably do anyway. How many people boot up just to check Facebook? Why load all that crap in the background when all you want is a browser? The traditional operating system is a bad idea. The only problem is that the browser based OS is just not really good enough yet. It doesn't mean we shouldn't stop trying though, and I expect Chrome OS has a lot more to show us over the next few years, and hopefully beyond that.

A week ago I posted a picture with my Chromebook alongside my MacBook and my iPad, and said that I needed all four devices, including the Galaxy S3 I took the picture with. I can safely say that my Chromebook is demoted. It's here because it was a gift, and I'm grateful. It's part of my family of gadgets, and it will be used here and there. I could even give it a strong recommendation for some people, who I know need simpler computers in their lives. (I dare not forsake them to Window 8.) But for myself, I just don't think me and my Chromebook are going to be very close. I'm sticking with Apple for now.

Nintendo's Grim Future

I started writing this after finishing my exams in final year of uni, so it draws a lot from Management theory on strategy and innovation. It's weird how so many terms here don't get used in the real world, but I think this demonstrates more heavily how out of touch academics can be, rather than vice versa.


I have grown up with Nintendo franchises my whole life, and even as I have aged and matured over the past few years, I have never been tempted to invest in PlayStations or XBoxes in order to play crap like FIFA or COD. Give me Mario; give me Zelda; give me Smash Bros instead. So it was with a hopeful eye that I watched the release of the Wii U. But like many, I am disappointed.


First, the culture problem

The manufacture of a gaming console is fundamentally a platform strategy, but it is particularly more so for Sony and Microsoft than Nintendo. Platform strategies succeed when they scale quickly, and lock in users with network effects and dominant designs. In essence, this refers to things such as XBox Live - a network that the user accepts as standard and does not prefer to adopt a new one. In order for these strategies to become strong in the market, the platform has to achieve a great deal of scale in the market, and the greater the scale, the greater the foothold. PlayStation 2 owners will relate to the high switching costs of jumping to XBox, since the PS3 was backwards compatible with all those games you already own. But to scale to something the size of the PS2, a platform has to nurture an environment that attracts developers and users. The more users, the more developers (since their potential market is bigger), the more games, the more users...

But for Nintendo, their biggest and most significant developer has always been themselves.

This is the observed problem. This is a problem because it feeds from the Nintendo culture. While the Wii was able to radically disrupt the video game market, the cultural tendency to alienate other developers perpetually fragments the overall strategy. Nintendo will continually fail to satisfy the demands of its 'hardcore' gamers (I hate that term) if it does not find a better way to scale it's platforms, and attract powerful developers to make powerful games.

Culture can be a very challenging thing to change. When things go wrong, the first thing comanies do is fix the execution, then they try strategy and finally some might consider fundamentally turning the wheel on the very paradigm lens that the organisation views the world through. Nintendo did this remarkably when launching the Wii. But the Wii U is merely logical incrementalism, and not a true response to the critical gamers that will make decisions over the next two years.


Second, the environment

The market is far more social these days. Intenet gaming is a massive source of revenue for Microsoft, and the free subscription is a valuable competitive advantage for the Playstation Network. Moreover, Facebook, Twitter, Google+ and other social networking sites have grown dramatically in the last few years, and developed powerful social integration tools including games, voice calls, and video chat. Social interaction is at the core of gaming now, and it has moved from the three friends sitting next to you, to the 200+ friends you have all around the world.

Technology is not a spec game. While videogames used to be a power war, this method of differentiation is slowly being abandoned by all players, and this trend preceeds the Wii. The problem is that consumers now expect technology to improve, and if it does not, the new system forgoes an important threshold capability.


The Solution

It's time for Nintendo to focus. Since they started out in games, Nintendo have nailed both hardware and software, but those days are over. Software is now the companies home turf. The technology in hardware is best left to Apple, Samsung and Sony. They need to start developing for Android and iOS, and maybe consider Mac and PC.

They could do it. There's no reason Nintendo couldn't execute extremely high quality content on mobile devices. Their expertise in handheld gaming would allow for rich and powerful handheld games. Much bigger markets exist on these platforms than the one's Nintendo will have to build by launching another DS or Wii. Social integration is already built in too with links like Facebook Connect and Game Center.

Then there's the television. It's a tricky one for everyone to figure out, although Apple giving it a go (as the strong rumors suggest) might change things dramatically. Even if this doesn't happen however, we are on the eve of an emerging Android Game Console market that Nintendo may as well prepare for.

I believe Nintendo treads it's current path over the edge of a cliff, and it will be immensely difficult for it to stray from this and change it's culture. Everything happening in the industry today, including the dire Wii U, suggests that some time not too far off, innovative game design will lose an old and once wise leader.

Wednesday, 30 January 2013

Mobile love

Here's to a busy day and also my first post from my phone. I'm hopelessly multi-device dependant, but I am realising more and more that of all the new toys I've had the fortune to play with recently, it's this phone that I appreciate the most. I think I've stopped missing my iPhone.

Thursday, 27 December 2012

On Switching To Android

Christmas went by quickly. Looking back on the year, I often remark that I wish I'd taken more pictures, and captured more of the moments that made for a great 2012. I don't particularly make "new year resolutions" but I will resolve now and going forwards to take more pictures. In fact, I resolve to take one picture a day, every day. And to accomplish this task, I am armed with the Samsung Galaxy S3.

The first in the series is a panorama of our front room on Boxing Day
Friends in the know will recognize the significance of my move to Android. So far I have been a walking talking iAd, and in many ways still am. I love Apple. I love their design, futuristic outlook, attention to detail and super-friendly UIs. But the time has come to go Google.

Why? Working there likely has a big part to play, but moreover, I'm finding recently that I want a little more from my phone. The camera was a big part of the decision (don't take my example above as proof of it's superiority, I'm still learning and practicing!) However, the customization, Google Now, and the general speed with which Google seems to be moving, compared to Apple, pretty much made me feel it was the right time to jump ship. It may not be there right now, but I've high hopes for Android in 2013.

The experience so far has been lackluster. I am struggling to adopt to the new world, but its a challenge I'm being rewarded for. Let me boil down a couple of my highlights so far. 1. The option to choose and buy my own battery cover (I'm in leather now, with Galaxy S3 etched in). 2. The option to custom fit my own launcher, minimizing animations and effects, and gearing my device for function. 3. Significantly better keyboard, also chosen by myself from the Play store. 4. Significantly better voice control, in the form of Google Now. It's still mostly a gimmick, but some functions have become part of my daily life, including checking stocks morning and night, checking what time's Stacey is at work (her rota changes, but I can see calendar entries as they come up), setting alarms and timers on the fly quickly and easily (I turn the boiler on and tell my phone "set alarm, 40 minutes, shower is ready", or I remember I have to make a phone call later, so I tell my phone "set alarm 715 tomorrow call home".


On the other hand, I should really tell you the many things that are pissing me off. There are tiny little details that Apple have paid attention to that I never even noticed until they disappeared on this device. Let's start with the one that is probably least relevant, but the most pertinent and frustrating - the lock screen. The lock screen is slow. I've never noticed how the iPhone lock screen is impressively present, but the Galaxy screen is slow. What I mean is, if I lock the phone and try and get back in, I'm not necessarily seeing the lock screen. I will probably see the screen I was just on, and have to wait a second or two to have the lock screen come up. In the long scheme of things, this is nothing, but it is bloody annoying. The time isn't on the button either. It's always worth giving the phone a couple of seconds in case it is showing you the time from the last time the display was on - this has happened many times. Forget the days of quick checking the time on the iPhone, and pocketing it back in a flash. This one takes time.

Next, the screen is too big! I can't believe I agree with this Apple ad now. I laughed at it when it went up on YouTube. I thought to myself "They are really desperate now, trying to sell on their thumb geometry." But it's a real issue. It's things like propping your phone up with your pinky to get to the home button, or having to conduct a carefully delicate maneuver to reach the top left corner, putting your phone is a dangerous palm balance.



I'll have to round up because this was a long post, and now I want to get dressed and head outside. I've got a picture to take and the weather in Dun Laoghaire is lovely (I didn't ask Google Now, I just looked out the window #oldschool). The roundup is pretty much a 'Watch This Space'. I'm not sure yet if I'm entirely comfortable on Android. While there are definitely gems keeping me interested, such as the prospect of rooting, developing apps for it, customizing, playing Ingress, etc., I'm still missing the simplicity and genius of the iPhone 5. I keep wondering, "Would it have been worth that extra 100 bucks?" The truth is, these are very different devices, believe it or not. The Apple vs. Samsung case while fighting over the hardware design, and some elements of the software, has made it seem like these two are homogenous, but they are not. One thing I have learnt from my time on Android, however, is that there are very few I would recommend it to. At least for the time being, it's definitely a place for the savvy, and the curious. If you want easy-to-use and "magical", just stick with Apple. Since Google Maps came out with an iOS app anyway, what's the problem?


Tuesday, 27 November 2012

Back to Black

After a year's hiatus, I've finally reinstated by black MacBook. I got this dear old thing back in Berkeley, when my Dell imploded just before a week of tests and coursework deadlines. It's nice to be back on my own computer (i.e. not a work computer), but it is weird having a poorer experience than I do at work. There is still some oddity with the backlight, which just decides to off itself every now and then, about once an hour, so there will be no movies had. Personally, I don't see myself lasting more than a few months before this old pal sees Ebay, but let's see if I can't make something of him yet.

Friday, 16 November 2012

Day 5: Shit work

Day 5 has been a tough one. I started out the morning crafting a new site template. Something a big different i.e. not simple and clean, but loud and outrageous. I decided to build a site for a fictional band, named aptly after my high-school attempt at a music career, Tru Story.


I'm not ready to upload this to the actual Internet yet, so you'll have to satisfy yourself with this drab screenshot. Even though its my work, I find it tasteless and clunky. I'm ashamed, but I'm not disheartened. Had I understood positioning in a more complete way, I'd have banged this out in an hour or so. But going back and correctly myself meant most of my day was spent trial-and-erroring multiple different combinations of absolutes, relatives and fixed. I didn't even spend 10 minutes honing the color scheme, so I've forgiven myself for that. I'm going to call this what it is and move on - a practice session. Perhaps not ready to be portfolio-ed, but something to work with. 

Thursday, 15 November 2012

HTML & CSS, Sorted!

It took the best part of the week, but I feel like I've finally got fundamental HTML and CSS cracked. I've just finished up on my first site (all about me, of course) and you can find it at mynameisel.com.

I'm going to go through the steps for you here, because really there isn't any reason we should all know a little bit about putting together a simple website. For me it was an obvious skill I needed - I work daily with online advertisers so having some web design knowledge should help there. It also means I can use my own creativity when it comes to promoting anything I'll need to in the future. So I decided to take 2 weeks off work to focus on me and learning something I wanted to learn. I did not expect to be done by now!

Day 1: On the first day I learnt all the basic HTML stuff. Pretty simple since I was a bit of a MySpaceaholic back in the day. I understand the core concepts, but needed some refreshing on how a website is really meant to be put together, as opposed to how a self-obsessed teenager might do on a broken social network. It led neatly into...

Day 2: Good, solid CSS. I loved this bit. I'm a bit of a minimalist (have you seen my site yet?!) and a perfectionist with stuff like this, so seeing the range of style to use was great fun. I've spent longer than I care to admit getting all the details right, but I've come to see how flexible CSS is, and how important it is to keep it in a separate file. This was a brand new concept to me (tell me about it... and I work at Google... I should know these things right?)

Day 3: Getting in hosted. This was way harder than I expected. A simple, practical and affordable web hosting solution is a big fat gap in the market if I've ever seen one. It took me two hours, a long walk, and a headache to figure out and decide what service provider to go with. All said and done, I put the site online using HostGator, for $8.95/month, plus $15 to register my domain. Their 24/7 chat customer service is pretty stellar, but their UI is total crap. I need to see if this can be done cheaper.

Day 4: Making it better. I spent time today nailing the "hover over" effect that's going on. Codecademy taught me how to change what happens to a certain div when you hover over it, but it took me a darn good while to figure out how to affect another div, and how to do it with correct positioning so that everything didn't shuffle around the page. Today is Day 4.

Next: Well now I need a new project. I've got some tidying up to do on the dashboards I have made for work, but since I am still on vacation, that can probably wait. In the meantime, I think I'll look for another site to start working on.

EDIT: Lot's of credit to Codecademy and the contributors on Stack Overflow btw. Couldn't have done it without them!