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.

It’s clear to me now that Microsoft, one of the “great American companies” I often refer to when talking to my kids about things I admire in business, has switched from advancement to entrenchment as its retention strategy for existing customers.  That is, rather than move their platforms forward and pull global businesses along with them, a more defensive strategy is emerging–one where Microsoft tries not to hemorrhage too much business to Google and even Apple by reminding companies how cheap it is NOT to migrate away from the Microsoft eco-system.

A fantastic example of this dynamic came to light today when it was announced that the next version of Microsoft Office for Mac will replace Redmond’s clunky Entourage e-mail app with an actual Mac OS X version of Outlook, the predominant e-mail application used in medium and large enterprises.  My company alone supports somewhere in the neighborhood of twelve-hundred Outlook nodes at about fifteen different firms.  So a Mac version of Outlook, as the t-shirt saying goes, is “kind of a big deal.”

But what’s an even bigger deal is that Outlook once ran natively on the Mac–on Mac OS 9 anyway–and shared a great deal in common with its Windows cousin.  And, suffice it to say, it was a better product than its redheaded stepchild, Entourage.  It makes me wonder why they ever canned Outlook on the Mac to begin with.

Now I’m beginning to understand that Microsoft is on an all-hands mission to get as many enterprises, large and small, as entrenched as possible before Google and other market players really step to the plate with something that competes with Microsoft, and in particular Outlook and Office.  (Anybody who suggests that Google Apps currently beats Microsoft Office is smoking some pretty harsh crack, sorry guys.)

Entrenchment is the key to damage control: keep the customer believing that it will cost them more in dollars and difficulty to move away from Microsoft, no matter how compelling the alternative, and they’ll stick with Microsoft.  This was how they (soundly) destroyed Lotus Notes, and Redmond’s incredible staying power may allow it to stave off Google Apps for quite a few years to come.

“Windows Marketplace for Mobile”.

OK, does this name strike anybody else as particularly dumb?  On the syllable count alone, the marketing folks at Microsoft should’ve shot this one down before it had a chance to get into the wild.  Now, it seems, it’s going to have to stick.

Compared to Apple’s “Appstore” (2 syllables) or Nokia’s “Ovi” (barely 2 syllables) or even Blackberry’s “App World” (seeing a pattern?), Microsoft’s elephant-sized name for it’s application store clocks in at a whopping 8 syllables. Imagine the water cooler discussions that will never happen as a result:

“Hey man, where’d you get that sweet pinball game?”

“Well, I got it from Windows Marketplace for Mobile!”

Riiiight.  Who seriously is going to call it that?  Microsoft’s history of self-defeating brand names hasn’t been on display this starkly since “Microsoft Windows Server Base Operating Systems Management Pack for Microsoft Operations Manager 2005“.  Srsly, who uses this wordy terminology?

With Apple having already coined the de facto term “Appstore”, why doesn’t Redmond take advantage of the growing strength of the Zune brand and call their wordy app store something like “Zune Store” or “Zune Place” or even just “Mobile World”?  Even HandMarket, a third-party app store for Windows Mobile, beats Microsoft to the punch in succinctness.

In an article posted today at eWeek, AT&T is excused from its traditional role as scapegoat in the Google Voice rejection fiasco.  And my previously posted sentiments about Apple building something that competes with Google Voice have finally been echoed on a mainstream outlet.

Well doy, Apple realizes that consumer-empowering voice technology is a competitive advantage.  We VoIP folks have been preaching that gospel for the last ten years.  Comrade Ken Camp wrote with visionary accuracy about the merits of VoIP in his book IP Telephony Demystified, one of the really early books on the subject.  I agreed with him when I wrote Switching to VoIP that VoIP is a leveler of the playing field, a true equalizer and a legitimately revolutionary technology item.

I’ve also viewed carriers like AT&T, at least for the last four or five years, as access providers, not “phone line providers” offering dialtone.  Apple, it seems, has arrived at the same conclusion.

First, it’s not the FCC’s domain but the Federal Trade Commission’s domain whether or not a business practice, like Apple’s (admittedly inconsistent) enforcement of it’s own developer agreements, is an unfair trade practice. And it may well be unfair; that doesn’t make it within the jurisdiction of the FCC, whose stock and trade isn’t social progress or anti-collusion.  Clearly, those are business matters whose definition of justice has little or nothing to do with voice as an application.  We have to be careful not to push the social progress agenda too hard–especially to the extend that we’re routinely punishing those who are earning a great profit, vis-a-vis Apple and the iPhone.

Second, let’s ask the real question: Since we know the decision to allow Google Voice is ultimately up to Apple, and not AT&T, what could Apple’s motivation for this rejection possibly be?  Are we ignoring the simple answer?  Enhancements to the iChat ecosystems, perhaps? The most obvious answer may not satisfy the conspiracy theorists.  But something as easy as Apple is getting ready to release their own Voice-killer makes the most since to me, to heck with AT&T’s bandwidth.

Finally, I’ve almost concluded that AT&T’s days as the exclusive distributor of iPhones in North America are numbered. Apple would have to score a pretty low IQ to permanently marry their network support to a single carrier, with the rise of new wide-area wireless networking standards and mass WiFi addiction marching on with no favoritism towards Bell.  This would seem to indicate, at least out here in the “sensible” midwest, that Apple is not beholden to AT&T, a company short on both sexy intellectual property and an applications-oriented revenue model, for a short-term political favor that screws its relationship with Google, a company who is enriched of both.

The answer to this mystery, I believe, is in Cupertino.

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.

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.

The retisance to provide an open, enthusiastic SIP solution on Apple’s part simply defies logic.  Everybody’s so excited about Skype on the iPhone–and so am I–but let’s face it, Skype is one in a series of many, MANY attempts to foist a proprietary telecom endpoint on the masses in the name of profit.  Sure, Skype on the iPhone will be fun, and even helpful-especially when the 3.0 firmware appears with push notification.  But you know what I really want?

To hook an iPhone up to a PBX.  Come on Apple.  The jig is up with AT&T; let’s see some SIP!

  • Viagra ordre
  • Cialis en ligne
  • Levitra en ligne
  • Propecia acheter
  • Viagra acheter
  • Acheter cialis
  • Ordre levitra
  • Ordre propecia
  • En ligne viagra
  • Vente cialis
  • Levitra bon marche
  • Propecia en ligne
  • Viagra online
  • Buy cialis
  • Order Levitra
  • Buy propecia
  • Buy viagra
  • Cheap cialis
  • Cheap Levitra
  • propecia online
  • Viagra prescription
  • Cialis online
  • Buy Levitra
  • Order propecia