rc3.org

Strong opinions, weakly held

Tag: Apple (page 4 of 7)

Apple kneecaps competitors and partners

I’ve been transfixed by Apple’s announcement yesterday that applications developed using translation or compatibility layers need not apply for inclusion on the App Store. My first thought was that this was an obvious stab at Adobe, and my second thought was that this was an attempt to insure that other companies don’t abstract away the iPhone OS.

I am reminded of Microsoft’s reaction to Java, specifically the early hype about Java. We all think of Java as a boring server-side language now, but the initial idea behind Java was that software developers could write applications in Java rather than writing them for Windows, and that those applications would work everywhere, thus defanging Microsoft’s desktop OS monopoly. Microsoft took various steps to prevent that from happening, but they lacked a tool like App Store that would enable them to just ban Java. Apple has that card to play, so they’re playing it.

Yesterday, John Gruber posted Why Apple Changed Section 3.3.1, and I think he nails the reasoning behind the move, but he declines to analyze whether this move is really good strategy for Apple. I would argue that it’s not.

Apple already has very wide latitude in deciding which apps will be approved for the store. If apps are low quality, they can be declined. And Apple can always issue more guidelines to application developers based on the content of the apps rather than on which tools were used to build them, requiring companies who create libraries to help produce iPhone applications to meet certain standards in terms of look, feel, and functionality in order to be included. It’s not necessary to cut everyone off.

Secondly, Gruber points out that most applications built using these kinds of intermediate layers suck. That’s the real reason why Java desktop applications were never incredibly successful. It had little to do with Microsoft’s anti-competitive moves and a lot to do with the fact that Java applications were slow, had their own user interface widgets which were different than those of the native platforms, and just looked ungainly. It wasn’t easy to write great applications in Java. That alone assured that Sun wasn’t going to abstract away Windows or the Mac OS.

Thirdly, this announcement is freaking out independent iPhone developers in a big way. Nearly all developers use third party libraries to save time when building applications, and every user of third party libraries now has to ask themselves whether these libraries fall into the new prohibited category. What happens if the iPhone application you’ve based a business on is found to depend on a library that is forbidden with iPhone OS 4? Do you start over or give up? A lot of developers are asking themselves that question today.

I have no idea whether there’s anything that will run afoul of the law in these license terms, but they should bother people, and Apple should suffer in the court of public opinion for them. This is a paranoid move and a defensive one. Apple’s mobile products are the most popular in their class right now, and they have the best community of developers of any platform vendor. Given their position of strength, they don’t need to act out of insecurity. And yet this is the second big defensive move they’ve made recently, the first being their offensive patent lawsuit against HTC last month.

Apple’s innovation impresses me, but their business practices are chilling. Customers need to let them know that they expect more from the company. Apple has shown in the past that it listens to this kind of feedback. Starting in 2003, Greenpeace put pressure on Apple over its environmental practices. Today Apple is regarded as one of the most environmentally responsible electronics makers in the world. I hold out hope that similar pressure over Apple’s ugly business practices can encourage the company to be more responsible on that front as well.

Apple hates cross-compilers

A lot of people have taken note of the following passage in the iPhone 4 developer agreement:

Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited.

It’s clear that Apple isn’t going to allow Flash to run on the iPhone, so Adobe came up with a creative alternative — a tool that lets you convert Flash into a native iPhone application. Packager for iPhone is to be included with Flash Professional CS5. Now Apple has made it known that applications created in this manner will not be approved for inclusion in the iPhone App Store.

Why would Apple make this rule? Perhaps there’s a technical reason, but my guess is this is pure cutthroat business. To create applications for the iPhone, you have to use Objective C. If you want to port the same application to Android, you have to rewrite it in Java. If Adobe and other tools vendors come up with applications that translate from ActionScript to Objective C and to Android’s flavor of Java, suddenly it’s much easier for developers to maintain their applications on multiple platforms. It looks like Apple wants to make sure that being multi-platform stays expensive, and that people just stick with building applications for today’s dominant platform — iPhone.

John Gruber’s iPad review

If you (like me) don’t own and haven’t used an iPad, you may enjoy John Gruber’s lengthy review.

I think this bit is exactly right:

Kindle has a better chance of long-term success as a software platform than a hardware one.

From day one I have wondered whether Amazon.com intended to make money on the Kindle or whether it was a proof-of-concept designed to spur the market for e-books. They’ve been aggressive about porting the Kindle reader to other platforms, and Amazon.com seems to be doing quite well selling digital music even though they don’t sell a music player. I imagine their margins are very good on e-books, regardless of whether or not the buyer purchased a Kindle.

The iPad commeth

People are going to start receiving their iPads tomorrow, and to mark the occasion we’re seeing one more spasm of iPad punditry. Tomorrow the hypothetical iPad dies and the real life iPad arrives, probably dashing the hopes of dozens of media companies who think that the iPad is their one way ticket to massive subscription revenue. (Danny O’Brien has a good post on that.)

Cory Doctorow took one more shot at the iPad today, making some good points in an argument that didn’t hold together particularly well. His strongest arguments are those meant to deter people from building native iPhone applications. And I do think that if you care about ubiquity and openness, you should avoid the iPhone platform and stick with building Web applications. Everything seems to indicate that they’ll run beautifully on the iPad, just as they run beautifully on your Netbook, or your Mac, or your Windows PC.

The piece I really wanted to link to, though, is Greg Knauss writing about the iPad future. Or, more generally, a future that involves simpler devices that require less expertise and maintenance than today’s personal computer. Greg argues that this future is inevitable, and that furthermore, it’s a pretty great future. I think that’s probably the best way to look at it.

As I write in my earlier piece on the iPad, we’re going to have to look somewhere other than our desktop for open platforms in the future.

Needed perspective on iPad hype

I’m excited about the iPad. Not enough to have pre-ordered one or anything, but I think it’s going to be a cool device, and I find it easy to imagine myself reading stuff on one during a flight or using it to post to Twitter while I’m watching TV. It’d be nice to have a device for surfing the Web with a decent-sized screen that doesn’t get hot enough to fry an egg.

Gadget afficionados are licking their chops, but what shocks me is the degree to which media businesses are head over heels over the iPad, thinking that somehow a new form factor is going to reinvigorate their business. News Corp is going to charge more for an iPad subscription to the Wall Street Journal than they charge for a Web-only subscription, more than they charge to deliver the paper to your house, and even more than a subscription that includes both.

Scott Rosenberg compares the media’s reaction to the iPad to its obsession with CD-ROMS back in 1994. Media businesses want a ticket back to the good old days, and the iPad, purely through the virtue of being something untried, looks like that ticket. These guys are drunk on the possibilities of the iPad today, but the hangover is going to be a miserable thing to see. If I were more clever, I’d have already learned to program for that platform, and now I would be out charging insane hourly rates to build doomed apps for desperate publishers. Maybe next time.

Smart iPad writing

There’s a ton of interesting writing about the iPad floating around that you may have already seen.

Steven Frank writes about Old World and New World computing, and explains that the exemplars of the new world are the iPhone and the iPad (and their competitors from other companies). I agree. The first thing I thought when I saw the iPad was that it would be the perfect device for my wife. She uses her computer to read email, surf the Web, and do some basic productivity stuff. She hates laptops, and she’s not a fan of the complexity of desktop computer operating systems. She’s ready for New World computing. (I, on the other hand, want a 27″ iMac and the opportunity to steal the iPad when she’s not looking.) Steven’s piece is really great, full of astute observations. You should read it.

Alex Payne is disturbed by the iPad because he sees (as I do) that it is the beginning of the end of computers for people who tinker.

Adam Pash says that forcing people to choose between open and user friendly creates a false dichotomy. This is one of those things that I wish were true, but that I’m not sure actually is true.

Fraser Speirs posts the positive take:

If the iPad and its successor devices free these people to focus on what they do best, it will dramatically change people’s perceptions of computing from something to fear to something to engage enthusiastically with. I find it hard to believe that the loss of background processing isn’t a price worth paying to have a computer that isn’t frightening anymore.

If you’re interested in the iPad itself rather than its implications for the future of computing, you have plenty of options. Stephen Fry is incredibly impressed. John Gruber talks about how fast it is and the chip Apple has built to make it so fast. He posted more hands on details yesterday. Usability expert Luke Wroblewski talks about the new user interface interactions introduced in the iPad presentation.

And finally, I agree with Roger Ebert — they should have called it the iTab.

My take on the long term implications of the iPad is here.

Is the iPad the harbinger of doom for personal computing?

In 2002, there was a lot of fear of Microsoft’s trusted computing platform, Palladium. The idea was that Microsoft was going to add new security to computers that was enforced in the hardware which would put an end to viruses and some other security problems but would also fundamentally change the relationship between computers and their users. Your computer would no longer be fully under your control, nor would it be functionally anonymous. Steven Levy’s original article hyping Palladium explains the purported benefits, then Ross Anderson explained what was scary about it.

In the end, Palladium was a total failure. It never went anywhere. But people at the time reacted very strongly when the traditional idea of the general purpose personal computer was threatened. People were afraid that if Palladium were implemented, the PC maker, application developers, and media companies would all be able to exert control over your experience.

Now we turn to Apple’s iPad. It’s just an iPod Touch with a big screen, but that’s all that many people need from a computer. You can use it to surf the Web, read email, listen to music, watch video, or compose documents. That’s the personal computer use case for many people. And I think a lot of people are going to buy them.

The fundamental difference between a Mac and an iPhone is that I can run any software I want on my Mac. I can buy it on a DVD, I can download it from the Internet, or I can compile it myself. I can get rid of OS X and install another operating system. The Mac is a general purpose computer in the classic sense. The iPhone is not.

Apple decides which software I can run on my iPhone. Apple provides the only means by which I can get it. The platform is for all intents and purposes, closed, and the hardware is closed as well. Sure, the iPhone is great to use, but the price of using it is that you’re rewarding Apple’s choice to bet on closed platforms.

What bothers me is that in terms of openness, the iPad is the same as the iPhone, but in terms of form factor, the iPad is essentially a general purpose computer. So it strikes me as a sort of Trojan horse that acculturates users to closed platforms as a viable alternative to open platforms, and not just when it comes to phones (which are closed pretty much across the board). The question we must ask ourselves as computer users is whether the tradeoff in freedom we make to enjoy Apple’s superior user experience is worth it.

The Setup just published an interview with free software pioneer Richard Stallman about the tools he uses. He uses a crappy Chinese netbook as his only computer:

I am using a Lemote Yeelong, a netbook with a Loongson chip and a 9-inch display. This is my only computer, and I use it all the time. I chose it because I can run it with 100% free software even at the BIOS level.

If Apple is really successful, it’s likely that other companies will be more emboldened to forsake openness as well. The catch is that customers won’t accept the sudden closing of a previously open platform, that’s one of the reasons Palladium failed. But Apple has shown that users will accept most anything in an entirely new platform as long as it offers users the experience they want.

I think that it’s a real possibility that in 10 years, general purpose computers will be seen as being strictly for developers and hobbyists. The descendants of the iPhone and iPad and their competitors will rule the consumer market and people will embrace the closed nature of these platforms for the same reason that Steve Levy hyped Palladium almost 10 years ago — because what you get for trading off freedom is reduced risk. There will be few (if any) viruses, and applications will “just work.”

General purpose computing is too complicated for most people anyway, and the iPad’s descendants along with similar competing products from other companies will offer an enticing alternative. So I see the death of the traditional, open personal computer as a likely occurrence.

Will closed personal computing matter?

The other question that arises for me is whether, in the the long term, the computer you hold in your hand really matters. If all of the applications we use run on other people’s Web servers, and all of our data lives in the cloud, then the fact that our computers are closed appliances we use to get to the Web isn’t such a big deal.

When you look at the performance curve for JavaScript, it does not seem unreasonable to me to imagine that one day in the not too distant future there will be no difference in performance between desktop applications and applications running in the browser. Apple has done a lot to make it possible to build Web applications that are nearly indistinguishable from iPhone applications. It seems likely that every platform vendor will be following their lead, so for most users it won’t matter whether they launch an application by clicking on an icon or by choosing a bookmark in their browser. Indeed, on the iPhone you can already assign icons to Web sites as though they are full-fledged applications.

I foresee an era where people who really care about computing freedom use whatever closed personal computer is available, but run their open source applications on a virtual machine in the cloud somewhere running an open source operating system. Their data is stored in some other location, perhaps in encrypted format so that the fact that it’s not in their physical control matters less. It’s not quite the same as the traditional definition of a “personal computer” but it’s not any less free than what we have now, and it provides the benefit of being accessible from anywhere with an Internet connection.

A future where applications and data in the cloud are more our own than the computers on our desks seems bizarre, but I can see things playing out that way.

For more on the threat to open computing posed by the iPhone platform, check out this piece from Create Digital Music.

Daring Fireball on PastryKit

John Gruber has a piece on JavaScript framework Apple has developed for the iPhone: PastryKit. It’s interesting to see how close Apple is getting to providing the “native experience” in a Web application. It’s a lot closer than most people would have thought possible, I think.

Improving the iPhone app store approval process

This week, Apple got a lot of bad publicity when two iPhone developers abandoned the platform because of the way the app store approval process is handled. The first was Joe Hewitt, the developer of the Facebook iPhone application. You can read his reasons why here. Back in August he expressed his frustration with Apple but said he wasn’t going to boycott the platform. Then today Rogue Amoeba announced that they’ll be focusing on the Mac going forward because of problems they’ve had with Apple’s approval process.

Like most people who aren’t calling the shots at Apple, I’d prefer it if you could install apps on your iPhone by simply going to a URL and downloading them. Even if Apple wants to maintain the vetting process for apps sold through the official store, they could provide an alternate means that anyone can use if they’re willing to assume the risks of doing so. This would, essentially, be a way to let jailbreaking go legit. Unfortunately I don’t think it’s going to happen anytime soon.

As an alternative, I think Apple needs to adopt a different form of government for the iPhone nation. Right now, it’s a dictatorship. Apple exercises nearly complete control over the platform — there are a few jailbroken and unlocked phones that participate in a sort of underground, but if you want to be a legal citizen of the iPhone community, you have to play by Apple’s rules. And as in most dictatorships, Apple makes up the rules as it goes along, and isn’t accountable for enforcing the rules fairly, or offering due process, or even telling people what the rules are, exactly. It’s not surprising that so many people hate this situation — it’s not fair. And Apple’s profits say that it can get away with this behavior for awhile longer. You don’t see too many iPhone users or developers moving to other platforms but the competing platforms are slowly becoming more compelling.

Clearly democracy is out of the question. Apple is a business, and they’re not going to suddenly let the users start running the show. What I do think Apple should move toward is a constitutional monarchy. Apple’s executives remain the heads of state, and are ultimately the final authority on iPhone-related matters, but for everyday purposes the rule of law exists. Apple would write a constitution of sorts for iPhone developers and users, and get rid of the hidden, arbitrary rules. They’d create an open process for developers seeking approval for their applications, communicate reasons for denial, and give the developers a chance to appeal such rulings. This would probably be more manpower-intensive than the current process, but Apple is ridiculously profitable, and in the long term holding themselves to a greater degree of transparency and accountability would be good for the iPhone.

The current system isn’t going to work for a whole lot longer.

Feel the heat

Apple is already starting to up the transparency. I’m not surprised.

Older posts Newer posts

© 2024 rc3.org

Theme by Anders NorenUp ↑