Skip to main content

Platform Innovation


With the introduction of the iPhone 5, one new feature has more people abuzz than any other: the new adapter.  Instead of the traditional 30-pin dock connector that has become ubiquitous in everything from consumer electronics to luxury cars, Apple has opted to introduce a new, proprietary 8-bin connector dubbed "Lightning".  I think that I speak for most of us Apple product owners when I say that as soon as this was announced, you did a mental tally of all of the devices and cables that would eventually have to be replaced, and I wasn't too happy with the resulting number.

Yes, it will be a pain to replace all of my cables and devices that use the older connector, but we'll all complain about, get angry, and eventually over time, forget about it.  Like the CD drive.  Or floppy drive.  Or the replaceable battery.
My point here is not to get into a "who innovates more" argument, but rather highlight a type of innovation that is very much organic to Apple and its overall strategy: platform innovation.  Apple is more than willing to take the bold step of admitting (or what some may consider dictating) when a feature or product has seen better days, and simply eliminate that feature entirely.  

Let's start with the floppy disk.  With the original Mac, Apple bucked the industry and chose a newer, smaller format for it's floppy disk.  In this case, different was good, as it had a higher capacity and was much more durable that it's 5 1/4" counterpart.  It took a few years, but eventually, Macs and PCs alike both standardized on the 3 1/2" floppy as their standard drive.

Despite Apple's introduction of the 3 1/2" drive, it was also the format's assassin, as as they eliminated any floppy drive on the original iMac.  At the time, this seemed like a dangerous move, as a lot of software was still distributed via floppy disks, and almost all documents were saved on them if they needed to be moved to another workstation.  But over time, all other manufacturers followed suit, and now you'd be hard-pressed to find any PC or Mac with a floppy drive.

Next, consider OS X.  Initially, any older Mac application writen for System 8 or 9 would run in an emulator dubbed Rosetta.  This was great and even necessary, as initially there were few native applications built for OS X, and Apple needed to ensure compatibility.  But at some point - and I can't remember the specific release - Apple said no more emulation.  Many of us grumbled that we'd have to re-purchase the same software for the newer OS, but we all did, and I think that OS X is better for having eliminated this type of legacy support.

Apple also killed the removable battery - first in the iPhone, and later in the MacBook line.  This decision allowed for larger, more expensive batteries that would in theory give you more usage time.  I do believe that the verdict is still out on this one, as Apple's competitors use this as a weakness to this day, as few others have adopted this strategy.

This brings us to the new dock connector.  Of course, its too early to tell what will happen as a result of this.  My prediction - given past history - is nothing.  Once the 3rd party market starts cranking out $5 adaptors, this perceived pain will vanish, and we'll forget about any impact that this decision has made.  Apple will, once again, benefit from being able to determine if and when something is no longer useful, and force that decision upon its customers, for better, worse, or nothing at all.

This strategy can be applied to how we develop applications, too.  There will come a time when an old technology or feature or even method simply does not apply anymore.  The pain of removing the outdated component is always perceived to be high, but the relief of a better alternate approach over time will benefit everyone.  

Implementing a platform innovation is never easy, and often they are done in the wrong places.  But when they are done properly and in the right places, we all benefit in the long run. 

Comments

Buzz Killington said…
On a PC at least they went toward USB which is standard. Every other phone manufacturer uses micro-USB now except Apple.

They are giving all their customers a giant EFF U, but everyone eats it up. If they were switching to a standard connector, that would be one thing - but to another proprietary one?

You drew the parallel to software, but there is a reason that VBScript never took off and that's b/c it only works on IE. Javascript is universal, hence its appeal. Waiting for the same thing to happen with all of these "Apple only" things - hoping eventually people wake up to it!
Scott said…
Buzz,

Ironically, Apple pioneered USB as well. :)

They have reasons for the avoidance of micro-USB, namely that it won't deliver enough power for the iPad to charge. With their connector, they can not only deliver the required power, but also provide a faster charge time. They look at this as a benefit for the consumer and weigh that as more important than adhering to a standard that does not meet their needs. I would bet that the vast majority does not care about which standards Apple chooses to adhere to as much as they care about being able to charge their devices as quickly as possible.

VBScript is a good example, but that's out of what we can control. What I was referring to was something within the domain that we as developers can influence - be it an older system that should be upgraded, or some process that was implemented years ago that is no longer relevant.

We can't all make the same impact as Apple does with our choices, but within our organizations & communities, we can make things better.

- Scott -
30 Pin connector as well as Apex (aka Marvel) almost introduced at the same time to the world and Apple replaced 30 pin connector to "Lightening". How about Oracle :)
Scott said…
Balaji,

I think that software is a little more adaptable than hardware. :)

- Scott -

Popular posts from this blog

Spaced Out

A while back, I wrote about how to give the Universal Theme a face lift.  If you follow the steps in that post, the base font for an APEX application with the Universal Theme can easily be changed.

While that's all well and good, sometimes you only want to change the font for a report, not the entire page.  One of the applications that I'm building contains a number of IRs based mostly on log data.  Thus, having that data in a monospaced font would make it a whole lot easier to read.

You can search Google Fonts for monospaced fonts by selecting only that option on the right-side menubar.  You can also opt for the standard yet kinda boring Courier and achieve the same thing.

To implement this in your application, follow the steps in my other post, but stop shy of the final step.  Instead of pasting in the text that I specify, paste in the following to the Custom CSS field in Theme Roller, using the name of the font you selected for the font-family:

.a-IRR-table tr td { font-fam…

Thanks, ODC (Oracle Developer Community)!

I owe a lot of thanks to the ODC - which stands for Oracle Developer Community.  What is ODC?  You may remember it as OTN, or the Oracle Technology Network.  Same people, different name.  Why they changed it I can't say.  People just liked it better that way... (love that song)

In any case, what am I thankful for?  A lot.  To start, the tools that I use day in and day out: SQL Developer, ORDS, Oracle Data Modeler, SQLcl and - of course - APEX.  Without these tools, I'm likely on a completely different career path, perhaps even one that aligns more closely with my degree in television management.

While the tools are great, it's really the people that make up the community that make ODC stand out. From the folks who run ODC and the Oracle ACE program to the developers and product managers who are behind the awesome tools, the ODC community is one of, if not the greatest asset of being involved with Oracle's products.

If you have yet to get more involved with this communi…

Whose Deck is it Anyways?

This year at KScope, we're going to try something new.  And fun.  And funny to watch - we hope.  It's called "Whose Deck is it Anyways?", and will occur on Sunday at 8:30pm.  It's only 30 minutes, but it will likely be the best 30 minutes of the conference.  Or at least the most embarrassing.

Here's what we're going to do: the will be four 5-minute presentations - one on each of the following: BI, EPM, Database & APEX.

Sound interesting?  Probably not.  We get that, too.  So here's what we did.

Each 5-minute session will be presented by a non-expert.  For example, it's highly likely that I'll be presenting on BI or EPM.

To make it even better, each slide deck will be prepared by the corresponding expert.  So again, it's highly likely that my slide deck's creator will be either Stewart Bryson or Edward Roske.  If nothing else, this session will be a crash course in how not to make cohesive, easy to read slides.

Interested now?  Ya,…