I own two colleges and a bar.

I’m not really sure what all the excitement over MyTown is about. It’s a social app for the iPhone that employs GPS as a means of allowing you to play a real estate game like Monopoly using local establishments as the places you trade.  Local businesses, that is, from the white pages.

When I first read about it, it sounded great.  When I read that it was developed by ex-Diablo engineers, it was a must-download.  While there was some meager novelty in “owning” the local community college, the shimmer quickly faded, because nothing at all interesting occurred as a result.

Sadly, 48 hours later, I think I’m going to remove it.  It’s boring, and it plays just like one of those Zynga social games where you have to check in as often as possible in order to “level up”.  I just don’t have time for that.

What the world will notice about iPhone apps after Adobe ships CS5

Offering Adobe CS5 as an alternative development tool for the iPhone is a stroke of bittersweet genius. It lowers barriers to entry for aspiring iPhone developers and creates a go-to-market strategy for creatives who don’t have the programming chops to do it today. To be overt, Objective C is the main reason more developers DON’T create iPhone apps, and the main reason iPhone app development is neither rapid nor user-friendly. So there are some real plusses to the heat Adobe is giving Apple here.

More access to friendly development tools = more iPhone apps = a more mature and varied iPhone marketplace.  Everybody wins, right?  TechCrunch even headlined their post about this, “the year Flash’s 2 million developers come to the iPhone.”

Maybe not.  Sorry TechCrunch.

When Adobe announced that it will include an iPhone “packager”, that is a program that will package Adobe Flash programs as iPhone apps, my initial reaction was, “Great, now I can do that time entry app I’ve been envisioning for my company’s web-based trouble ticketing system.”

But I quickly realized that this packager is only going to produce iPhone-runnable Flash apps, and the full set of iPhone APIs will likely be out of reach to Flash developers.  The telephony APIs and other niceties XCode jocks get to use will probably still be off limits, to say nothing of distribution of the apps.  It will be very easy for Apple to spot a Flash app on its way through the App Store submission process, and disapprove it.  In fact, the rejection of the packaged Flash apps could be automated such that there’s not even any oversight–and on similar grounds Apple used to reject the Commodore 64 emulator last year.

Not to mention that fact that other apps that could benefit from Flash’s presence (like Safari, to say the least) still won’t be able to run custom-made Flash client programs.

So maybe Apple will come around–but in the mean time, I don’t think this announcement is nearly as significant as it sounds.

Apple: Decide if the iPhone is a platform, and do it quick please

If Apple insists on barring developers who overlap the “built-in functionality” of the iPhone, how is a developer to know what types of applications are a safe bet–in the long run? Since Apple recently banished Google Voice from the app store (which is an epic fail on Apple’s part, btw), one has to wonder, since all apps borrow some of Apple’s API functionality, just what they consider built-in and not.

The article, Apple Makes the Case for Web Apps concludes that developers will be more inclined to  create web-based apps geared at the iPhone.  While Apple’s recent actions may give developers pause to consider the web approach, I disagree that many will abandon their native app inclinations because of all that they lose in doing so.  For one, you can’t create home screen shortcuts to web apps (that I know of).  But the best reason not to develop web apps for the iPhone is their lack of support for front-end controls on the phone itself.  That is, in a web app, you don’t have nearly the power to access the GPS location, the GUI controls, the iPod library,  and so on. The new 3.0 iPhone browser is better at hooking into the phone’s local hardware, but is still quite hobbled compare to native apps, so geolocation and photos won’t have the pinache they would on a native app. Those are the content items that have made iPhone apps so much better than previous-generation mobile apps, and with the web approach, they’re more or less off limits.

How is it that YellowPages.com can offer a directory lookup app on the app store when it obviously overlaps Apple’s built-in Contacts and Maps functionality?  Yet instead of picking on YellowPages.com, Apple is seen picking on Google, arguably their biggest and most powerful ally.  Add to that the insult of Apple’s marketing of the iPhone and iPod Touch to developers as a platform for great apps, and it should make us all feel a bit used.

In the heady days of the computer revolution, Microsoft was forced to recognize that Windows (even MS-DOS) was a platform. Rather than stifling upstart competition by barring certain developers from the Windows ecosystem, Microsoft at least realized that it was developer embrace of the platform that would cause it to live or die in the long run.  The result was that, through the early 2000′s, Windows was the go-to platform for the whole world, and everybody from Sun to IBM lost lengthy, futile, billion dollar battles trying to undo Microsoft’s early decision.

Apple is nearly past that point in their new platform’s life cycle.  If it’s an app platform–let it be.  Palm and Blackberry are still waiting in the wings, and Windows Mobile will be the centerpiece of Microsoft’s revenue strategy in the next ten years.  And, like it or not, whatever else Microsoft did that was crummy and evil, they never told a developer he couldn’t distribute an app.

The Intrigue of an Appstore for Windows and OS X

Let’s face it.  If you can support selling 5 GB downloads (which Apple does in the form of movies) through your e-commerce solution, iTunes, then there’s certainly no intrinsic barrier to doing so with applications, or drivers, or other forms of digital content.  If we fail to think of applications as content, we fail in our understanding of content.   Yet here we are thinking it’s a bold new idea to license and sell application software online–fully confining the novelty of such a thing to the mobile space.   Heh, we’re smart.

An old friend, Fleecy Moss, who was among the architects of the independent takeover of Amiga in the early 2000′s, once gave a talk at a tradeshow in the nineties–and his espousal of the content designation to software was, at the time, a revolutionary concept.  As with many ideas that bubbled up from the ill-fated Amiga wellspring, this concept proved true, and was ahead of its time.  It would be another ten years before the idea was accepted by the greater community.

The app store paradigm has brought this idea to the forefront of the way we think about distributing content.  Yet there’s something holding up the adoption of online app stores to distribute software, and I can’t quite thumb it.  Shareware authors have been distributing license credentials through e-commerce sites for a decade already, yet Apple and Microsoft still don’t sell their developers’ software through their flagship web sites.

Perhaps even more silly is the fact that consumers, vis-a-vis bloggers, don’t already demand such a solution.  If I can buy and download a DRM’d episode of Lost, why can’t I download a credentialed, licensed copy of Squeeze, or Microsoft Office for Mac, or my favorite blogging application, Ecto?   Yet nobody complains.  Indeed, it seems that the idea of a desktop app store is some kind of new idea. Technologizer, the “smarter take on tech”, just ran a piece about it today.   Yet I was talking about it a year ago, and longer.

Nokia is not an American brand, pure and simple

(or: why Nokia gets trounced in the U.S.)

I have a healthy amount of respect for Nokia.  Before the iPhone they were the only devicemaker offering half of what Apple now offers with the 3GS.  Indeed, I toted a Nokia N95 for a while, and an N81 8GB for a while.  Both were excellent phones, but I’m convinced now that Apple’s iPhone, even as it arrives as a better all-around phone than Nokia’s current flagship (the obviously Blackberry-inspired N97), is more appealing to American consumers because it is made by an American company.

That’s right.  Nokia’s brand is obscurely perceived in North America, particularly the U.S., as an upscale European oddity not unlike Fiat or Porsche, to use an automotive analogy.  So while it may be the number one brand globally, Nokia has failed to make an impression on American consumers precisely for the reason that they’re a non-American company.

Apple owes a helping of its iPhone success to that fact.  The product is American; the company is American; the marketing is overwhelmingly American, with sitcom-style television commercials, extremely stable revision control (how many models of phone does Apple have on the market compared to Nokia?), and a least-common-denominator hardware engineering approach that appeals to the maximum number of simultaneous consumers instead of offering a specific style or feature set to five or six different niches.  Fewer buttons, more software.

The other American-friendly thing about the iPhone is the nature of its name.  Nokia is some Scandinavian meme as Sony is some Japanese one.  The difference is that Nokia’s name hasn’t been overcome with a mass-market product the way Sony’s cross-cultural name has been with the Playstation, and earlier, the Walkman. Same with Nintendo.  Who didn’t have a Nintendo Entertainment System in 1990?  And for that matter, who doesn’t have a Wii today? Far fewer carry a Nokia product than own a Wii in the United States.

But there’s more to it that the brand name. Say what you like about Nokia’s lack of good carrier support in the United States (Apple still has only one official carrier), or their botched execution of an application store model (Apple a lot to harm themselves on the appstore anyway), the real problem with Nokia’s phones isn’t the name on them.  It’s the way they look and feel.  While the majority of American consumers still haven’t obtained a smartphone, the daunting physique of a Nokia N81, for example, could give a buyer pause.  The lack of fluidity of form in Nokia’s products means that the user is exposed to as many features as possible, whether or not they want to use them, and perception is that there’s a long learning curve.

To the degree that the iPhone is simple-to-use, Apple has more or less beaten Nokia by exploiting that one shortcoming. Forget about the crummy app store, the weirdly-perceived brand name, and the GSM-only carrier support for a moment.  Nokia needs to embrace the “downrightly simple” mantra that had early adopters falling all over themselves trying to lay hands on an iPhone. Indeed, if it weren’t for AT&T’s customer retention strategy, Apple may’ve sold twice as many iPhones as they have.

But then, I believe most iPhone sales occured at Blackberry’s expense, not Nokia’s–and that, of itself, does not bode well for the European giant.