Tag Archives: Apple Computer

The Curious Paradox of Copying and Creativity

A couple of months ago I picked up this post on TechCrunch, which sort of accuses Apple of copying its iBooks application for the new iPad.

clonesI hate business copycats. Drives me crazy. As Palo Alto Software’s Business Plan Pro grew up, others copied our tag lines, our packaging, and the software. I hated that.

In the retail business you have some companies who live on copying packaging. They put imitation products inside imitation packages to fool people, so they get the wrong thing. I hate that. How do they live with themselves?

But it’s not illegal.

And it’s also the history of innovation. From VisiCalc to SuperCalc to Lotus 1-2-3 to Quattro Pro to Microsoft Excel, copying makes things better. From CP/M to DOS to Windows, copying makes things better. The original Macintosh operating system borrowed from an earlier mouse and window system developed by Xerox. The iPod was not the first MP3 player, nor is the iPad the first tablet computer. These were not new ideas, but they were improvements.

And all the cool new phones now are copying the iPhone.

Do we hate the people who copy ideas? We all do it. Kids learn their moves in sports by copying other kids. We learn to write better by copying writing we like. We learn to get along with people by copying people.

The entire history of human creativity is built on copying. What, if not copying, is the cause of those identifiable periods in music and art and writing, like the Baroque or Renaissance? What except copying makes Gothic cathedrals? Try to name a good movie that didn’t borrow from some earlier movie. Even Shakespeare was often redoing older classical themes.

And yet, when I look at all the stuff in the market that’s copying something else, it makes me mad. Do your own thing. Be original. Make it better. Don’t just copy my thing. Even if it’s barely legal, it’s still sleazy.

A lot of great art starts with copying, borrowing themes, ideas, and so on. But business, starting with one idea and adding to it, making it better, creating new things based on old things, that’s progress. Business copying, looking like somebody else just to steal some respect, is just bad business.

I’m glad cool new innovations based on existing stuff succeed. I hope all sleazy business copies fail.

(Images: galtiero boffi, Konstantin L/Shutterstock)

Business Strategy in Action, or Reaction, Both, or Neither

Apple vs. Kindle vs. publishers, oh my. Do you know the background? It’s all over the web. And I posted here this week about how Apple and Amazon.com and Macmillan are wrapped up in an ebook battle. And it gets better. As I write this, Wednesday evening, the news is that Amazon gave in and put Macmillan back into the mix, but at higher prices. But I just checked the site and my favorite Macmillan book, Thomas Friedman’s Hot, Flat, and Crowded, is listed there as available through third parties only. So go figure.

I’m fascinated with all of this. Really, business strategy in action. Consider these questions, and ask yourself: if you were Steve Jobs, or Jeff Bezos, what would you do?

  1. Does Apple Computer block the Kindle app on its new iPad? The iPad runs iPhone apps, and the Kindle iPhone app works great. But does that mean iPad users can buy Kindle books for their iPad for $9.95, while Apple’s iPad iBooks cost $14.99?
  2. Apple can block the Kindle app, of course. But what will users say about that? Apple users tend to take Apple as some public resource. They’re incensed when Apple acts in its own business interest instead of the public good. Would cutting off the competition be worth the dark side mask?

  3. Is Amazon.com seriously going to cut off its nose to spite its face? They took all Macmillan books off of Amazon.com because of a pricing and revenue share argument related to the iPad. But doesn’t that hurt the Amazon.com business proposition? Don’t we all go there to find the world’s largest inventory? And now they say they’re giving in, putting Macmillan back, and at the higher prices it demanded. What does that do for the Kindle pricing ceiling at $9.99? What happens to the $5 differential on iPad between a Kindle book and an iPad book?
  4. Do publishers gain by fighting either format, or either channel? Now Macmillan books are playing second fiddle at Amazon.com. It’s hard to tell from here, but it’s been presented as Macmillan squaring off against Amazon.com for a larger share of the revenue. That’s a bold move. Would you do it? How would you feel if you were a Macmillan author?
  5. What about Sony, or Barnes and Noble? These other ebook readers that were seriously planning to compete… are they just blown away? What can they do?
  6. Does this mean ebooks are finally for real? I’ve liked ebooks for more than 10 years now, read them on an early Rocket ebook reader, on a PDA, on a Kindle, and on my iPhone, as well as on a number of laptops. Are they finally going to get to critical mass? That would be nice.
  7. Do smart buyers wait for all of this to sort out? Remember the Sony Betamax format vs. VHS? You don’t want to invest on the losing side here, right? I finally bought Blue-ray HD after HD DVD lost the battle.

I’m enjoying the spectacle. I’ve got the Kindle, I’ve got the iPhone with the Kindle app on it, and I’ll probably buy an Apple iPad for its entertainment value, form factor, and long batterly life. For ebooks the iPhone Kindle app is still my favorite, so I’ll probably use the Kindle app on the iPad too, when I get it — if Apple doesn’t block it, that is. I don’t see how the bells and whistles of the new iBook reader can be worth the extra $5. But, since it’s not shipping for a few months anyhow, I’m going to wait and watch.

And I’m especially watching the strategy play out. Several of these big players can make bold decisions that will cut off competition and annoy the hell out of buyers. Is that the way it’s going to go?

(Image credit: from Mashable’s recent post on the eBook War)

Apple Computer Role Reversal as Big Brother

What delicious irony. The champion of the little guy has become big brother.

Remember the groundbreaking first Macintosh television commercial, in 1984, with the young woman throwing a hammer into the giant video screen on an evil big brother, smashing it into bits? There’s a role reversal going on.

Apple Computer has taken the establishment role in the booming new iPhone application market. First the iPhone, then well-publicized stories of trivial iPhone apps making thousands of dollars daily, and then the application review process got swamped. And now there’s Apple Computer, the gatekeeper, protector of the establishment, standing between all those developers with stars in their eyes, on one had, and admission into the app store, on the other.

The original idea of review was a combination of protecting the software from crashing, and protecting the Apple store from embarrassment. Ever since the stories of iPhone application fortunes first broke — I fear it was with a fart app making $10,000 a day — the software developers are flocking to iPhone apps. Of course I have no special knowledge, but from the outside looking in, it would seem like the crush of applicants makes long waits, unfair rejections, and inconsistencies inevitable. I’m guessing Apple’s private-sector resources to manage the tidal wave are completely overwhelmed. Mobclix, which tracks iPhone applications with analytics, is reporting that there are more than 85,000 applications approved by Apple so far, and the wait has gone from days to weeks, and is rising.

On a Mobclix blog about the iPhone applications market, iPhone app developer Max Zamkow says:

iPhone developers live in constant fear of receiving an email from Apple with what can only be termed the ‘Death Sentence’: “We’ve reviewed your application and we have determined that this application…will not be appropriate for the App Store.”

He’s developed an app called FruitShoot Lite that lets unhappy iPhone developers (or anybody else) vent their anger by mock shooting at mock apples on their iPhones. But the default fruit target is a banana. And it passed the review.

It’s a couple of months ago now that Jason Calacanis, celebrity entrepreneur and blogger with a known taste for controversy, lashed out against Apple in The Case Against Apple–in Five Parts, in which he complained not just about the “draconian policies” of the iPhone app review, but also four other sins including “anti-competitive” practices with MP3 players, “monopolistic” dealings with telecommunications (a reference to AT&T’s lock on the US iPhone), “hypocrisy” of blocking competing browsers on the iPhone, and blocking Google voice on the iPhone.

TechCrunch highlighted a dumb-but-approved “upskirt” app last week, mocking the glaring inconsistencies:

Let me just get this straight: A hilarious satirical app made by the Someecards guys cannot get approved because it contains cards that, for example, mock Hitler. But an upskirt app is just fine? That is so ridiculous.

Yes, ironic indeed. On first glance, I look at the rising tide of complaints and I think they’re all delusional: Apple is a business, not a public service, and it owns the iTunes store, so it can do what it likes. Developers waiting weeks to get into the market, living in fear of rejection after all that work? It’s Apple’s clubhouse, so Apple can admit whoever it wants. However, as the whole thing starts to sink in, I have to add that Apple Computer has made this bed for itself, so it deserves to lie in it.

Not that I don’t like Apple. I’ve been a serious Mac user twice, first for about 10 years from the beginning in 1984 until the middle 90s, and again for the last two years. I like the Mac, love the iPhone, love Apple’s products in general. However, I’ve never quite accepted the odd phenomenon of Macintosh and Apple as crusade. The whole phenomenon of some connection between operating systems and good (Apple) or evil (Windows) has always seemed a bit creepy to me. After all, they’re just products for sale. Apple, IBM, Microsoft … they are all big companies.

Apple Computer, however, has actively catered to this odd canonization of brand throughout its history. It wasn’t for nothing that the Macintosh anti-big-brother image is part of our cultural heritage. It wasn’t for nothing that IBM became “big blue” and Microsoft “the dark side” … Apple spent a lot of thinking time, effort, and money on building that anti-establishment tinge to its brand. And it’s not totally crazy to suggest that Apple managed to change brand to aura, or halo.

Live by the anti-establishment brand, die by the anti-establishment brand. What we’re seeing, I think, with the rising protest of developers against Apple, is something akin to a jilted lover, or the famous Shakespeare epithet about a woman scorned. It seems like the backlash is whipped to a frenzy with Apple in a way that it might not be if it were some other big company, or, say, the US Patent and Trademark Office. Companies move slowly, government agencies move slowly, but not Apple Computer. The woman with the hammer in that 1984 commercial, crashing big brother and all. Say it isn’t so. Disillusion.

(Photo credit:wikipedia)

Reflections on Programming, and the Good Old Days

Somebody asked me recently how my background relates to programming computers, and software. That’s hard to explain, given that I majored in Literature as an undergrad, then got an MA in Journalism, then an MBA. None of that says programming.

In my case it was like falling in love. I first used word processing when I was still with United Press International (UPI) in Mexico City, back in the 1970s (it was an early Atex system). Then, when I got accepted to business school they gave me a teach-yourself-BASIC programming book, and told me to learn it before the school year started.

Flickr cc by Jana_aka_BADGRL
Flickr cc by Jana_aka_BADGRL

Programming, making the computer do things, was fascinating to me. It was like making real things, but with a touch of magic. Do the code, press run, and when it did what I wanted, filling the screen with my results, I loved it. I ended up with a part-time job helping fellow students with the computer in the business school basement, and building my own computer from parts (for you really old-time computer geeks, that was a CP/M computer and an S-100 bus).

What reminded me of these good old days was yesterday my daughter Megan sent me this: Someone At Apple Has A Sense Of Humor. The MobileCrunch report cites this piece of code deep in the iPhone, where you’d only find it by trying to hack around the main stuff:

00009 @interface UIViewController (UIViewControllerClassDumpWarning)

00010 – (void)attentionClassDumpUser:(id)fp8 yesItsUsAgain:(id)fp12 althoughSwizzlingAndOverridingPrivateMethodsIsFun:(id)fp16 itWasntMuchFunWhenYourAppStoppedWorking:(id)fp20 pleaseRefrainFromDoingSoInTheFutureOkayThanksBye:(id)fp24; 00011 @end

What that says there is “Although swizzling and overriding private methods is fun, it wasn’t much fun when your app stopped working. Please refrain from doing so in the future. Okay thanks bye.”

My actual programming was mainly in the 1980s, when “hacking” was a good thing, and those of us who worked with personal computers could feel like we were some kind of an in crowd at times. I did do some real code for Business Plan Pro’s first version, and, before that, I wrote code for the early Business Plan Toolkit using spreadsheet macros. Error messages could be kind of fun.

I’d like to brag about some of the more amusing error messages I left, but, sorry, I’d play with them during testing but I always chickened out and cleaned them up to look more professional (and, sadly, dull).

And that also reminds me, as well, of how programming was so often a one-person job back in the 1980s. I’d do it for myself, first, use it, and then productize later. That’s a lot different from the teams of programmers everybody uses today. But things, including the computer programs, were a lot simpler. Not as good, either — not by a long shot — but simpler.

But I searched Google for funny error messages, and a lot come up. You can click the link to see for yourself, or maybe just use this one, which seems like one of the best.

True Story: A Challenge

I was the planning consultant to Apple Computer’s Latin America group from 1982 until 1991 or 1992, the end of the relationship being a bit hard to define as I was called on steadily more by Apple Japan and less by Apple Latin America.

The challenge came in the spring of 1985. The annual business plan was done every spring, turned in to management in June and then discussed and revised and resubmitted and eventually accepted in July. In April of 1985 I had been the consultant for that process for four years running when Hector Saldana, manager of the group, said:

“Tim, yes I want you to do our annual plan for us again this year. But only on two conditions: first, I want you to stop working for other computer companies. Second, I want you to take up a desk in our office, come every day, and sit here and see us implement the plan.”

Happily, he also had some good news related to giving up other competing companies as clients: “And, if you agree to do this, I want to contract you for all of your hours for the next year, and at your regular billing rate.”

The condition of giving up competing clients was difficult for a one-person business. What if Apple had problems, or changed its policy regarding consultants? What if Hector got promoted or fired? Where would I be then, if I had given up other business relationships.

That’s not the real point of the story, although it does relate to planning as you go. That certainly wasn’t part of my business plan for my business, but it was a classic example of changed assumptions. We talked about it at home at length, and decided to go ahead with it. However, we also modified the plan we had going related to efforts to generate new leads and new business: we would focus that effort within Apple itself, different groups that didn’t talk much to each other, to reduce risk of having two many eggs in the single Apple Latin America basket. The plan was modified for cause, to accommodate changed assumptions.

The problem of implementation, however, forced me to consider the difference between the plan and the results of the plan.

There was some history. The previous year or two had been the time of “desktop publishing” for Apple Computer. Desktop publishing, which we now take for granted, started with the first Macintosh laser printer in 1985. It was a huge advantage for Apple in competition against other personal computer systems.

Our plan for fiscal 1985 had been to emphasize desktop publishing in most of our marketing efforts. And it didn’t happen. While we talked about desktop publishing in every meeting, the managers would go back to their desks, take phone calls, put out fires, and forget about it. They didn’t intend to, but they’d had so much emphasis on desktop publishing that it seemed boring, old hat. Multimedia was the thing.

So, faced with the implementation challenge, I created what became the strategy pyramid to manage strategic alignment. We ended up with a relatively simple database of business activities. Collaterals (meaning brochures and such), bundle deals (software included with the hardware at special bundled prices), advertising, trade shows, meetings and events, all were tied into a system that identified what strategy point they impacted, and what tactic.

So during that year, as business went on, we were able to view actual activities, spending and effort, divided by priority. We set more budget money for desktop publishing activities than any other. During the review meetings, we compared actual spending and activities (the beginning of what I talk about as metrics)  to planned spending and activities. And over time, with pie charts and bar charts to help, we were able to build strategic alignment. What was done was what the strategy dictated.

The plan-as-you-go implication was that this didn’t happen just because it was in the plan. It took management. There was a plan review schedule with the meetings on the calendar way in advance, and for every meeting I was able to produce data on progress towards planned goals. The managers discussed results. Plan vs. actual metrics became important.

When things didn’t go according to plan, the meetings would bring that to the surface. Managers would explain how the assumptions turned out wrong, or some unforeseen event — we had good results as well as bad results — and we would on occasion revise the plan.