New Year, New Direction

I want to thank WordPress for the very cool blog stats job they did for the 2011 summary.  Saved me a lot of work!

Which is especially good since I’ve been working hard on something new (I know, I know: what’s new in that, right?).  But bear with me!

Microsoft + Nokia Babies: Hate at a Distance, Love Up Close

original source: http://www.pop.com.br/

Apologies to QML fans but I’m going to to extend the interruption of that series by at least one more article.  Blame a cynical friend’s recent conversion to the Dark Side of mobile Microsoft. 

More Post-MeeGo Musing: Community Echoes

Ever since Intel’s MeeGo-cedes-to-Tizen announcement, I’ve been in a slightly unfocused state.  It’s familiar territory– when Maemo was set aside by Nokia for MeeGo, there was the same quandary: what now?  Better yet, what next?

After a little over two years of scant free time, I’m finally working normal hours.  So that liberates me for more community engagement, aka the stuff I really love.  It also frees me up to think.  But looking back on the past 5 years of support for open source projects with great promise but ultimate abandonment, I’m left to wonder what to target. 

A Qt QML Beginner’s Project: MotoRing, part 2 – Rewind and Reveal

Finally, here’s the much-demanded second part to this QML beginner-focused series.  Okay, one guy asked, but he sounded really interested.

I said at the end of the first article that I would progress to the next phase in this one.  But the request for a screenshot of the app at this point got me to thinking that it would be worth more to fledgling QML developers if I backed up and broke down the code.  So let’s do it.  There’s a lot to cover, so I’ll spread it across two or three articles.

A Qt QML Beginner’s Project: MotoRing, part 1 – GPS

I unloaded some Qt newbie frustration the other day detailing my first serious efforts to code for the Nokia N9.  Now I’d like to step back a bit and outline the actual project, and in subsequent posts walk other newcomers through my coding journey of pleasure and pain.

First a disclaimer: I’ve been programming for over 25 years.  That has included COBOL, Forth, Logo, DOS/VAX/Unix batch commands, Basic, LISP, Pascal, C, JavaScript and Visual Basic (both COM and .NET).  While I could work minor wonders with scripting and compiled linear languages, I found that I have been most productive in event-driven VB.Net.  Readers should know that I am not targeting an audience that’s totally new to programming, but rather, programmers who like me are experienced with other languages and platforms but new to Qt.

I really wasn’t very apprehensive about Qt, especially the mature 4.7.  Friends kept telling me how easy it was, and the Qt Creator environment did not look difficult at all at first glance. 

The Un-local Nokia

source: http://www-bgr-com

I’ve been pretty easy on my favorite former employer lately, even to the point of gushing over Nokia World 2011 and pouring out pure fanboy praise over a fantastic phone that will only see limited release.  But I don’t think I’d be performing my duty as a recently-renewed Developer Champion if I didn’t provide some much-needed critical feedback.  Lovingly, of course.

Nokia’s physical withdrawal from certain locales is not a new subject for me, but it’s reached a point where I’m more concerned than ever.  Of course most of my focus is on the United States, and more specifically, my home near Dallas, Texas.  In just a few years Nokia as a brand has become a complete non-factor here and just about the entire country.  I’m keenly observant of devices used by others and, outside of a small circle of open source enthusiasts, I’m seeing everything but Nokia phones in the hands of the general public.

None of that is news to most people.  And Nokia has made it very clear that it expects its fairly new Windows Phone strategy, coupled with impeccable and compelling industrial design, to get its high-end products back into regions (like the US) where product sales margins matter.

The continued problem as I see it, though, is that Nokia seems to expect that they can concentrate all efforts on a few key cities.  Its shrinking supply chain system has led to greater consolidation of localization activities at sites far removed from the end customers.  Now, for core needs this consolidation need not be an issue; a phone engine is a phone engine is a phone engine.  But as many companies are becoming increasingly aware, last-mile localization is an absolute must for finished goods.

This translates to customer Care activities as well.  Contract employees at remote call centers just cannot identify with many of the diverse clientele they are called upon to support.  It’s not just language barriers; cultural differences can be a real hindrance (not to mention cybersecurity risks).  But more than that, trade customers (i.e., AT&T, Telcel, Orange, et al) will not tolerate delays in problem resolution.  They will require local presence in key markets. 

My Derailed Journey Back to Nokia

This is a highly personal post so for those whose eyes roll or minds reel at the thought, click past this one and I promise more juicy tech stuff next.

As regular readers know, I lost a great job with an awesome company in January of 2009.  As of this past Monday I started a challenging new role with what seems like another awesome company so far.  In between, I worked at something that didn’t work out while keeping an eye on Nokia opportunities the whole time.   

Thoughts from Nokia World 2011

A few weeks ago, Nokia Connects held a media contest to award tickets, travel and accomodation for some lucky blogger to express why he or she was excited about Nokia World 2011.  I already had all that covered, but gave it a shot just in case my wife or a friend could use the prize.  Worth a try, right?

Granted, my entry began by addressing cynicism, some personal but largely general, which had to make it a long-shot.  I walked readers through my Nokia journey for this year, with the aim of providing an objective yet ultimately optimistic view of the company’s prospects.  

Me Tizen, You Join?

Mobile Linux characters have been acting out lately like they were in a bad adventure movie.

Maemo lopes slowly and reluctantly toward its fatal date with the sunset.  MeeGo blinks in the same sun and finds its full commitment gone.  And like a battle-tested Phoenix, Tizen emerges from the ashes of twice-burned, thrice-shy skepticism.

Such is life in the largely undeveloped desert ecosystems outside the expanding stockade walls of Appleworld, Microsoftia and the remaining fading few. 

Maemo, MeeGo, Mango and Me

Ever since the February 11 2011 Nokia event cheekily tagged as #NoWin and known colloquially as The Elopocalypse, I’ve struggled to cover Nokia’s present and abandoned strategies here with equal care.  Don’t be misled by my attempts of objectivity over Linux and Microsoft activities, though– it hasn’t been easy.  I’ve been moderating an internal conflict between a growing invasion of open source love versus a legacy of Microsoft development experience combined with strong curiosity.  Neither side has a clear advantage over the other for me and therein lies a conundrum.

I could have very easily avoided the whole controversy at the start.  When I assumed responsibility for Maemo internet tablet quality in the North American market, I could have taken the easy route and stuck to the basics.  That meant developing test plans, training auditors and inspectors, hosting Finnish and Mexican product teams, and making sure CES 2007 was supplied on time with 200 pristine N800s.  Nothing more.

But no.  I’m a device nut.  An admitted hardware geek.  As I’ve shared many times, laying eyes on the Nokia 770 tablet changed everything for me.  It put what I saw then as the future in my hands, literally and figuratively.  I could not just treat this product line as I did the various and sundry cell phones I also touched.  I took tablets personally.