Showing posts with label Widgets. Show all posts
Showing posts with label Widgets. Show all posts

Wednesday, October 03, 2007

Quo vadis, iPhone?

People all over the web are giving Apple hell for breaking unauthorized and unsupported third-party iPhone hacks with its 1.1 software update. There are two types of these hacks: ones enabling the iPhone to be used with any SIM card; and others which just let users install third-party apps on the device. The former directly hurt Apple and AT&T, therefore Apple is actively trying to prevent these hacks. The latter, however, don't do much harm, thus Apple doesn't go out of its way to break them. Break them it does, nevertheless, prompting liberation movements to spring up and demand the franchisement of the iPhone from the evil tyranny of Apple. What could be more ridiculous than that?

Some of these critics jump to the conclusion that Apple doesn't get the importance of third-party applications. Well, chance may have it that Apple doesn't plan to ever allow third-party apps on the iPhone, but we don't know that.

I'm more inclined to believe that Apple wants to do it right.

There's a common sentiment out there that accuses Apple of some sort of haughty elitism. Wil Shipley put it this way:

I know Steve Jobs; he's actually amazingly like my old business partner Mike Matas. They both love closed systems, for a simple reason -- they both know they're smarter than anyone else on the planet, and they don't need anyone else mucking up their systems. Steve would rather have no third parties for Mac OS X if he could get away with it -- Apple, of course, would do a much better job on anything, but since customers insist on Photoshop and Office and other apps, he puts up with them. (Well, except, now Apple has their own office suite.) Steve knows that on a computer, having a broad spectrum of apps is more important that having them all be Apple-perfect.

But on iPods, Airports, Apple TVs, and now iPhones, Apple wants every app perfect. Which is nice, in theory. In practice, it means innovation only happens at Apple's pace. The marketplace of ideas is much smaller, and the devices are much poorer because of it. (Example: Why can't I stream music from my iPhone or iPod touch to my Airport Express?)
Emphasis mine.

Now, we don't know if Apple plans to open up the iPhone for third-party developers. But Wil is right: Apple doesn't need anyone else mucking up its systems. Some of those unsupported, unofficial third-party hacks would do just that. Muck up the system.

If Apple opens up the iPhone for developers, making third-party apps official and a supported feature of the phone, it won't be able to afford to have those apps crash the phone.

Apps on a computer can crash, sure. We're used to that. There are about five ways to force a misbehaving Mac app to quit, and a crashed Mac up will leave the rest of your system intact.

But remember the days before Mac OS X? Remember the bomb?

Remeber when a crash could render your entire computer unusable?

Do you also remember what happened when your frontmost app got unresponsive? Basically, so did your Mac.

With the limited user interface of the iPhone, a misbehaving app can easily create the illusion of a misbehaving iPhone. How do you know that it's only Johnnie's Shareware Recipe Editor that froze, not your iPhone? Will you blame Johnnie's Shareware Garage, LLC, or Apple, Inc?

Besides, people are far less forgiving about a frozen phone than about a frozen computer. A phone is just a phone, even if it can double as a computer.

What next? Your car keys freezing? Your beer opener?

If Apple does plan to allow third-party apps, it needs to perform some magic that prevents the user from just about ever having an iPhone locked up by third-party software.

Perhaps a daemon should be running, monitoring every application's responsiveness, and returning to the home screen when the frontmost app is having problems? Add a status message that informs the user of this incident? Or should there be a well-advertised, sure-fire, and foolproof user action that never fails to quit a misbehaving app? These things would need to be sorted out.

And besides, Apple would need to isolate parts of the system from direct access by third parties. We know that the iPhone was completed on a tight deadline, remember why Leopard hasn't shipped yet? So, it's not unreasonable to think that its software still has some rough edges, and nobody other than Apple's engineers should really be playing with it for a while.

So even if third-party application development is in the iPhone's future, it's only reasonable to expect that it takes time to implement properly.

I think that, for the near future, iPhone development will consist of the following:

  1. Apple delivering significant and free software updates: Notice how Apple's subscription-based iPhone accounting suggests that the iPhone will have more features in the future courtesy of Apple.
  2. Hand-picked third parties delivering applications, either for free or for a small fee: think about Google Maps already on the iPhone, and iPod games that are sold via iTunes. The iPod is also a closed platform, but there's still some third-party development going on, closely controlled by Apple. There's nothing stopping Apple from doing just that. As they would get to "bless" any third-party app before it becomes available, Apple could maintain its strict quality standards for the phone. A rumor to this effect is already out.
  3. Web applications may transition into Widgets. Rumors already suggest that improvements to the WebKit framework are on their way, enabling "web applications" to be stored offline. What exactly separates an "offline web app" from a Widget? Not much, mostly the capability to run arbitrary code (including Cocoa Objective-C). I'm inclined to think that a Dashboard-like SDK may be a compromise between the needs of Apple and developers: a sandbox with limited access to iPhone features, but at least not something that runs on a server.
Unlimited, no-holds-barred third-party development could turn the iPhone into a PDA and more. It could turn the iPhone into a VoIP device, causing a loss of revenue for AT&T (and thus for Apple as well).

Apple's new software updates for the iPhone will certainly serve as an indication as to where Apple wants the device to be heading. The first software update has come and gone, and we still don't have a clipboard, making the iPhone basically useless for any text editing apart from typing out a quick e-mail. There's no user-accessible file system, no SSH client, no instant messaging, no editing capabilities for Microsoft Office documents. In other words, the iPhone is not a PDA, and it's definitely not targeted at enterprise users or geeks.

The iPhone may be the smartest phone ever made, but it's not a smartphone.

Does Apple even want to change that? I'm getting the impression that Apple wants the iPhone to be pretty much what it is today, and those of us who expect software updates to turn it into a device with a greatly expanded set of capabilities will be ultimately disappointed.

I hope to be wrong, but I think Apple wants the vast, almost unlimited potential of the embedded OS X operating system to remain largely unfulfilled on the iPhone.

If the rumors of the Newton's revival are true, then perhaps those of us waiting for an ultrasmart PDA from Apple should set our sights on this new mythical beast, and resign to the fact that the iPhone is, and will always be, a cellphone.

Read More...

Friday, June 22, 2007

Here is my executive summary of the WWDC keynote

There's a new Desktop and Dock whose main feature is that they look much better in full page print ads. Call it marketing-optimization, but it looks good. Everyone hates the mimicry of the new menu bar, but I don't think I'll have any problems with it.

The number one top secret feature of Leopard is apparently Stacks. Huh? Dock folders done kinda right? Okay... Gimme some more RDF.

Brushed metal is dead, Aqua is dying. Welcome back, Platinum! Everyone, quickly redesign your apps now! I find the new look a bit too dark. But I like the huge shadow the frontmost window casts.

Now there is absolutely no way to tell the Finder apart from iTunes. Cover flow will be useful. Yes, I'm serious. Especially with inline preview, as well as Quick Look. These may become as revolutionary (that is, for people who actually work on their Macs) as Exposé was. But what about the new huge sidebar? Will there be a way to hide it? Or shall we all buy Macs with bigger screens?

The Finder is incomplete, though. Where's the online Finder Store? I want to buy files for 99 cents, folders for $9.99. And we need a good visualizer and an equalizer.

OK, maybe this iTunes fetish thing is going a bit too far. Maybe Steve needs therapy. But at least the iPhone holds strong, and fights back any attempted iTunes influence: no silly search field, no pesky visualizer, and definitely no connection to that stupid online store.

Core animation is still cool. It's being used in subtly cartoonish ways. I hoped, based on Wil Shipley's raving commentary, that Apple would use it in the OS in a lot of fun ways, but it's not the case. Maybe Steve's legendary taste won't allow that.

We're still going to get Spaces. Too bad that it still seems to break Exposé.

Dashboard. Apple is taking it to a whole new level by… adding, count it, one widget. Movies. Pretty slick. U.S. only, I suppose, though…

iChat never fails to impress. At least it never fails to impress Phil Schiller. (Actually, nothing ever fails to impress Phil Schiller, but we love the guy.) He was almost hyperventilating when he announced, "We can look at a PDF together!" Would you have thought that fifty years ago? Travel to Mars, maybe. Pimp your PDF over the Internet? No way, no how.

Time Machine is huge. Educating people about the importance of backing up. Changing habits of users worldwide. Boom. Dunno if it works, but definitely looks amazing. The retro sci-fi icon is insanely cool on so many levels. Time Machine seems to be the backbone of the whole marketing theme for Leopard. Aptly, this keynote already makes me feel like it's WWDC '06 all over again. But the "Final Countdown meets Star Wars" imagery is definitely refreshing after Tiger's unimaginative metal-on-fur logo.

A leaked screenshot mentions "hourly backups […] saved daily" until your disk is full, which is ambiguous and sounds potentially stupid, but I hope it will soon be clarified, and turn out to be something smarter. Like, only backing up files that have changed.

Mail is cool too. Notes are great, just great. Really. Too bad they look horrendous. It will be an open architecture, so third parties, please fix it ASAP. Mail also recognizes addresses. But will this work with non-English addresses as well?

There was no mention of iLife. I still cling on to my speculation that it will be bundled with Leopard for free. I guess I don't know when to give up. But anyway, iPhoto now integrates with Mail, so that's one more indication that iLife will be part of the OS. Right? Please?

iPhone: no additional features were revealed. We still haven't seen the Calendar or Notes, we still don't know how text editing works in any of the apps. Can you select text? Can you cut and paste? No sign of either has been revealed, ever. Still no Spotlight, either. OK, we have less than a week and we'll see, but I'm beginning to think that version 1.0 of the iPhone OS will be even more stripped-down than I'd thought.

Read More...

Tuesday, June 12, 2007

iPhone: a new platform for web applications that could revive the NC concept

Well, anyone hoping for a real SDK for the iPhone must be disappointed as hell. But then really, how reasonable was it to expect Apple to not just finish the iPhone in time (which we know was a close call), but also create a complete set of developer tools for it, including user interface guidelines and all? I think those who are disappointed kind of deserve to be.

So Steve tossed a bone to developers. His suggestion that they should develop web apps for the iPhone will certainly infuriate a lot of them, and it does seem a bit audacious to me as well. However, I'm sure that once Apple gets around to creating it, a real SDK will be there for all aspiring iPhone developers. But, seeing how carefully Apple wants to control both the stability and the public image of the iPhone, that should take a while. I agree with just about everything that Daniel Eran says on the subject.


However, I also think Steve Jobs is really on to something here. I don't doubt for a second that there will be hundreds, maybe thousands of websites or web applications written specifically for the iPhone. Not just because whenever Jobs speaks, people will start to listen, and stuff will be happening (though the Jobsian charisma is definitely part of it), but also because the iPhone and its Safari web browser will very likely create a new business: that of handheld web applications.

I don't think web applications will replace desktop apps any time soon, though they will certainly continue to complement them. We all know how networks, especially something as slow as EDGE can limit the usefulness of a web application.

However, I think a web app may make a lot more sense on a less powerful handheld device such as the iPhone than on a full-featured desktop or notebook. Here's why:
  1. The iPhone has limited resources, while a web app usually lives on a powerful and scalable server. Therefore the remote app can perform operations faster than a local iPhone application could.
  2. The user interface of a web application is closer to that of an iPhone app than it is to a desktop application. Due to their greatly simplified user interfaces, iPhone apps have fewer advantages over web applications than desktop apps do, so web applications will look less out of place on the device.
Case in point: I've always been struggling with the mail clients on my smartphones. They were slow to connect to the mail server, check for new messages, download them all, make decisions about attachments, and so on. There was also a limit on the number and size of messages that my phones could store. 

So I switched to webmail. Google Mail has an okay webmail page for mobile devices, and for my other accounts, I installed IlohaMail on one of my web servers. This open-source PHP script is actually a mail client that lets you access any POP or IMAP mail sever on the internet, much like Apple's Mail App, except that Iloha runs on a server, and you interact with it via a simple web interface. So my web server does the heavy lifting (checking and fetching and rendering mail), all my smartphone does is display it as a web page. I don't have to force my poor little phone to perform loads of network operations, or to store megabytes and megabytes of mails or attachments in its limited memory. It all happens on my web server, and all my phone does is let me interact with all that data. Perfect!

Of course, handling mail should cause no problems for the iPhone. But more complicated tasks might. Heck, even an image editing solution such as Snipshot could probably be rewritten for the iPhone, and fill an important void – at least for the time being, i.e. before Apple opens up development for real, or supplies a native iPhone app that does all of this and more.

Thin clients or network computers never really took off. Well, the iPhone could become one that does – without really trying that hard. There has never been a mass-market handheld device running a full-featured web browser like the iPhone. If this isn't the time for the Great Handheld-Targeted Web Application Revolution, I don't know what is.

Read More...

Friday, November 10, 2006

Are Widgets worthless?

A caustically funny article by Mac360 states an unpleasant truth: Widgets are useless.
To quote:

Dashboard Widgets are worthless curiosities with high calories and low nutritional value, toy utilities for the weak minded, popular with recent switchers from Windows PCs, who, it seems, are attracted to glitter and bright colors, and Apple delivered.
I remember when Widgets were first rumored. I didn't believe them. Everything about them, including their design, seemed diametrically opposite to whatever Apple does. Sometimes I go hunting for widgets that make sense, but usually return empty-handed.

Here's what I use widgets for.

  1. Weather. I'm an expat, and thus I have a Weather widget up for my native Budapest as well as my current home, Luxembourg. I also put up weather widgets for my holiday destinations, or the current locations of some of my closest friends.
  2. Calculator. It's nice to have one around at the touch of a button.
  3. iTunes album art fetch. I don't even remember the name of the widget. I guess fetching iTunes album art is such an unimportant task that I wouldn't go to the trouble of launching a full-blown app for it, but a Dashboard Widget is painless enough.
  4. Translation. The widget beats the hell out of the clumsy web interfaces we have.
To sum it up: Widgets are nice when you need some fast piece of information, or to do some simple task, but don't really want to launch an app (or website) for it, either because the app (or web interface) in question would be a bit inconvenient, or because the information or task is so profoundly unimportant that it's just not worth the hassle. Or both.

I wonder if Widgets have a potential to mature a bit. I have the feeling that a few killer Widgets are yet to be conceived and built.

Read More...