Slashdot Mirror


The Forgotten Failure of Apple's PowerTalk

DECS writes "The series of articles Why Apple Will Change TV compared how Apple is poised for success in areas where Microsoft is currently failing. But circumstances are subject to change! Just over a decade ago, Apple began facing serious legacy problems with its platform, with many parallels to today's Microsoft. Examining Apple's dramatic fall provides a series of notable platform lessons that no company should ignore. A look back at the forgotten failure of Apple's PowerTalk: Apple vs. Microsoft in the Enterprise"

10 of 138 comments (clear)

  1. 3 valuable lessons? by pimpimpim · · Score: 5, Insightful
    The article mentions 3 valuable lessons:

    1. Don't try to sell a futuristic product that doesn't quite work yet; instead, talk about it while selling as existing product that can compete in the current market.

    2. Don't attempt to fire conceptual ideas at an imagined market; instead, craft finished products that solve real problems and can support a sustainable market.

    3. Ship a functional product and then constantly refine it; Real world use and years of ongoing refinement create enormous value for a product.

    Now, according to their lessons, google with all their betas must be a rightout disaster, shouldn't it?

    --
    molmod.com - computing tips from a molecular modeling
    1. Re:3 valuable lessons? by jfengel · · Score: 4, Interesting

      Actually, I'd say Google models this pretty well. Products with a real current functionality, like GMail and Google Maps, succeed despite pushing the technological envelope. Products which push the envelope too hard, like their office suite, fail to catch fire. They keep looking for the boundary between "functional" and "futuristic", but there's almost always a market for the things (especially at the $0 price they charge for it) they make when they work.

      Either way, Google is all about pushing the "constantly refine it" part. Web apps make for instantaneous, compatible upgrades.

    2. Re:3 valuable lessons? by Mr.+Underbridge · · Score: 4, Insightful

      Now, according to their lessons, google with all their betas must be a rightout disaster, shouldn't it?

      Significantly different market. Google has the cash, time, patience, and talent to instead throw 100 products at the wall and see what sticks. Because we're talking web services and not hardware, they can accept a 20% success rate, or lower, and that would be fantastic.

      That said, Google would do well to invest more energy in promoting the products that look on the verge of success, like mail. Already Yahoo has come out with a product that many think is now better than gmail (though I don't), in part because google's been dragging its feet with gmail, *and* it has stagnated for over a year.

  2. Yeah but which tuner? by Kadin2048 · · Score: 5, Insightful

    What kind of TV tuner would you have them install?

    Analog NTSC? Great, except that it'll stop working in a few years, and the quality is abysmal by modern standards.

    ATSC? You get high-def, but you need an antenna, and even then you only get the big networks, which is a big step down to people used to 100+ channels of cable.

    Clear QAM? It lets you use cable, so no antenna, but chances are you'll still only get the major networks, and it's arguably a greater pain in the ass than ATSC: many cable companies (Comcast, I'm looking at you) strip the metadata from their clear-QAM channels, making things like program guides really painful to use. And at the end of the day, you'll still be stuck with only the major broadcast networks, because those are the only ones that the cablecos are required to broadcast unencrypted. Everything else requires a proprietary converter box.

    The solution would be CableCard, but there are still a lot of areas where you either can't get one, or are treated like shit and get a degraded level of service if you do. (And you pay several extra bucks for the privilege of renting the card.)

    Given the state of the market right now, I wouldn't ship a computer with a TV tuner in it, either. If the FCC were to get its act together and really make CableCard the standard, and eliminate proprietary converter boxes, then I think you'd see an explosion in the types of set-top boxes and DVRs. I have no doubt Apple would be at the top of the list.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  3. Re:Apple vs. Microsoft by maztuhblastah · · Score: 4, Interesting

    MSFT enjoyed a 7% increase in revenue last quarter alone, while AAPL's growth has been in the iPod area. There are no similarities between AAPL and MSFT in that front.

    You probably didn't mean to phrase it that way, but you're totally right. Note the lack of Zune rumour sites, and general lack of enthusiasm over the Zune when compared to the iPod.

    Now, as for the marketshare aregument: you're also right. Apple's marketshare has fallen since 1994/5. It has also improved since 1997/8. Moving past statistics, one can look at the Wall Street perception of Apple. In 1996-7 Wall Street saw Apple in a death spiral. Their market share was swirling down the toilet, they were losing ground in the education and enterprise sectors, and Windows 95/98 was generating a much bigger buzz than anything Apple was producing. Then Apple turned around: they got Jobs back at the helm, released a product that created a media sensation (iMac -- for examples, look at Newsweek's and Time's coverage of it) and started inching away from the edge of a financial cliff. Following that with Mac OS X, and the iPod, Wall Streets prediction of Apple's future is pretty damn bright.

    You mention Microsoft. I say don't bother. They don't really compete. Apple makes personal computers and iPods. Microsoft makes an operating system and a game console (and soon another iPod "killer"). With the exception of the forthcoming Zune, there's not really much competition between the two. People cite Mac OS X as competing against Windows -- often referencing Vista -- but it's not really. Mac OS X only runs on Macs (officially.) Windows runs on commodity hardware. Apple makes Mac OS X to bundle with their hardware. Microsoft makes Windows because it's the cornerstone of their business. There's far less competition than people think.

  4. Same data, different conclusion by Anonymous Coward · · Score: 5, Interesting

    As an email gateway developer, I worked with Exchange since it's inception and I attempted to use AOCE. When I compare that experience with what's going on now, I reach a very different conclusion.

    Exchange started out life in the X.400 world. (If memory serves, Microsoft bought an X.400 product from someone else and GUIfied it.) This meant that even before the advent of the Internet Connector you could connect to Exchange using "standard" X.400 protocols. (I say "standard" because X.400 is so large and messy that pretty much everyone who implemented it was forced to deviate from the specifications in one way or another.) Not easy, but doable, and more to the point, doable from any platform able to deploy an OSI network stack. As Exchange shifted towards SMTP things improved to the point where Exchange was able to connect to existing facilities with little effort. (The article is wrong, BTW, in claiming that modem SMTP was around when Exchange first shipped. It was around but Microsoft chose to ignore it.)

    AOCE, OTOH, only provided vast, arcane, incomplete and poorly documented Mac-specific API. The underlying protocols weren't documented at all. We tried hard to figure how to interface with this mess, even sitting down to discuss our issues with Apple folks at one point, but eventually gave up. And I'm talking a group of people who developed successful gateways to X.400-1984, X.400-1988, cc:Mail, Microsoft Mail, Novell MHS, and GroupWise among others. Either we are fools who got incredibly lucky several times over, or AOCE was an unmitigated disaster. And I don't think we were lucky fools.

    But Apple learned their lesson. As the article points out, they now leverage open standards whenever possible. You can talk to a lot of Apple's new stuff over protocol. Sure, the APis are still there, and some of them are pretty nasty, but in a lot of cases you don't have to use them. Apple is also very active in various standards organizations (I wish they had had more success with Bonjour in the IETF, but that's a different matter).

    Microsoft, OTOH, has utterly failed to learn anything from their experience with Exchange. They still roll their own whenever possible. They don't document the protocols they use, only the APIs, and of course those are only available on Windoze. I used to see lots of Microsoft people at standards meetings but not so many any more.

    Of course things can change, but once things are headed in a particular direction they tend to stay on that course, even if it is a bad one. Everything I see about Microsoft says to me that they are on the wrong course and aren't doing anywhere near enough reinvention to correct it. The exact opposite appears to be the case with Apple.

    1. Re:Same data, different conclusion by lahi · · Score: 4, Interesting

      Interesting. If I recall correctly, AOCE/PowerTalk was presented at the 94 WWDC. A friend of mine attended, and shared what he had brought home with me. I saw the Demo video, and the docs. The API docs were huge - about two Inside Mac VI, I think. Incredible. The idea to empower _every_ application with e-mail capability was great in a way. As was many other ideas in AOCE/PowerTalk. But it was too complex and too inefficient.

      However, what really killed it, IMO, was that one of the premises it was built upon, was soon to be shown as false. Few people seem to remember it, but at that time, it was not at all clear that the Internet would take over the world completely. Networking yes, but it was widely believed that the Internet would be an interim solution, soon to be replaced by ISO OSI protocols like TP4. And of course X.400/X.500 etc etc. In addition, Apple still had a dedication to AppleTalk. And there were existing proprietary mailsystems like QuickMail.

      The idea was that PowerTalk users would have adapters that would enable a workstation to use legacy mail systems. In hindsight, this of course is a totally stupid idea, today we would put such gateway functionality at the mailserver. But with the following prevalence of plain SMTP/POP/IMAP mail, this capability would just constitute deadweight in the PowerTalk software.

      The idea of an in-basket on the desktop, and send-mail capabilities in all applications is in a way something that we still miss today. And if you think about it, it is in a way just a GUI rendition of old Unix ideas, with the ~7mbox (= in-basket), and :w !mail user from vi.

      In my opinion the user interface principles as they were strictly defined even up to AOCE are still unsurpassed, no interface has ever had the same completely natural feel. Windows, OS X, KDE, GNOME - nothing comes close to the interface as it was back in good old System 7.

      I sure wish there was an open source project to take the lessons learned back then, and make a new X11 based GUI that puts them to effective use, while trying to retain some fundamental simplicity.

      -Lasse

  5. tip-toeing by pubjames · · Score: 4, Insightful

    I have to say I have been very impressed by Apple's strategic manovering over the last five years or so. Whilst Sony and Microsoft has been clashing heads trying to use gaming machines as a trojan horse to become the digital hub of people's living rooms, Apple has quietly been putting together all the pieces it needs to do so in a much more sophisticated manner.

    Personally, I don't think Steve Jobs is very interested in conquering the enterprise desktop these days, he's got his eyes fixed on potentially a much bigger pie - becoming the digital media hub of people's homes.

  6. Really, this is a cyclical corporate problem. by RunzWithScissors · · Score: 4, Insightful

    Seriously, companies don't really learn from another company's trials and tribulations. At some point they all suffer from the same thing, which will cause them to experience "a downfall". This malady is:

    "But we're [insert company name here]!"

    I know it looks innocuous, but let's see that in action!

    1988, IBM was having big problems with management bloat, a stagnant product line, and a poor customer experience. But if you asked someone there 'Why would I buy from you when I could buy from Compaq or some other less expensive, more innovative competitor?' the response was invariably, "But we're IBM!"

    In 1998, SGI started shipping their coolest, most important product ever. The $15,000 Windows NT workstation. If you asked an executive at SGI 'Why would I pay $15000 for a Windows NT machine with a nice graphics card when I can build a whitebox with an Nvidia Riva TNT card for far less money?', the response was "But we're SGI!"

    Today, ask a SUN exec 'Why should I pay $X for a solaris workstation when I can buy assemble a box for $500 running Linux that will do the same thing?' What do they say? "But we're SUN!"

    It's been my experience that this becomes a problem at most sucessful companies, and if you pay attention, you'll see it's cyclical. The company adopts this mentality, loses customers, re-vamp's their product line, customer service, etc. Gains customers, becomes successful again, and ultimately repeats their mistakes and do the whole thing over again.

    Sad.

    -Runz

  7. Engineering vs Marketing by hhawk · · Score: 4, Funny

    The article states that Apple Enginners and Microsoft Markets.

    The authors understanding of what marketing is, is wrong. I think it would have been more correct to say that Microsoft Sells.

    The classical defination of marketing is to find out what a customer needs and then produce that for them.

    --
    http://www.hawknest.com/