I couldn’t help but wonder what the iPad hype machine is going to mean for OS X in the long wrong. Sure, OS X is the development environment for the iPhoneOS, but is there enough *there* with the mobile OS to make it the de facto environment of choice for folks like me?

As it is now, iPhone OS does a whole lot of things OS X does not–platform-wide UI support for multi-touch is just the beginning of the list. Still, it seems Apple has gone to great lengths not to cannibalize desktop PC sales, if not overtly saying so. No, iPad is not a desktop replacement, yet.  For starters, it synchronizes with iTunes, meaning that it doesn’t actually run iTunes, so its calendaring and music apps are still very mobile in nature. I also wonder if the lack of a user-facing camera was a design scheme to keep the iPad out of the desktop space, as opposed to a financial consideration to keep down manufacturing costs.

But the brushes app seems like an impressive utility with the potential to offset some productivity that’s normally reserved for the desktop.  And as I type this on a Macbook Pro, I realize that the iPad will never be suitable for video production, or for audio mixing. Even still, I can imagine great uses for multitouch in these kinds of apps.

Without the UI goodies, OS X shimmers less, and I believe it’s only a matter of time before touch-enabled desktop gear starts shipping from Cupertino.

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.

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.

  • Viagra online
  • Order cheap cialis
  • Buy viagra no prescription
  • Cialis online
  • Buy generic cialis
  • Order propecia no prescription
  • Cheap propecia online
  • Propecia online pharmacy
  • Order levitra online
  • Cheap price cialis
  • Online pharmacy levitra
  • Buy viagra online
  • Buy discount levitra
  • Cheap cialis online
  • Propecia hair loss