Posts tagged with: mobile

I got an Airport Express unit for Christmas, yippee!  Finally the massive wealth of songs on my iMac are flying through the air and spilling gloriously from the speakers in my living room.  It's awesome!  Although setup was a little funky with my aging wireless router, once I got it working I was amazed at how simple iTunes makes it to switch between speakers via AirTunes, and how nice the music quality is. Especially cool is that, with one stationery and two laptop computers in the apartment, it's simple to control the flow of the music via shared libraries.  Keeping a laptop in the dining room, for instance, makes it easier to play DJ without going to the office on the other side of the apartment when a track needs skipping. But even BETTER, I'm using Remote Buddy on my iPhone to control the tunes.  I can use it to change AirTunesspeakers from my office to the living room easily, and navigate through my playlists to find what I want to hear. Then it offers a simple remote-control interface to control the song or volume. This app is almost freaky because you can operate all kinds of apps via...

This is part of a series of posts about the Apple iPhone and the future of the mobile Web. With regard to the upcoming release of an iPhone SDK for native, third-party apps: keep in mind that Web apps are growing in popularity and functionality.  Many predict web apps will one day render the desktop tower more or less obsolete.  As apps like Google Mail/Reader/Docs/Calendar, Basecamp, Todoist and the rest become more ubiquitous, online file storage like .Mac and box.net become cheaper/easier/faster, and bandwidth pipes become less of an issue, the day will come when files and applications are all run online, and users log in through a thin client OR EVEN A MOBILE DEVICE to establish their identity and to operate the data and applications.  Google is banking on this.  You can bet that Microsoft is working to create Web-app versions of their software.  Apple seemed to be on the same page with the original, abandoned Safari SDK, and with the Google Maps and Search integration on the iPhone. What happened? Some have suggested that the problems involved got too complicated just to fix them instead of working around them. I don't know if that's true, but...

In my last post I wrote about mobile application design and how form should disappear in the face of function.  The implementation of MobileSafari on the iPhone comes so very close to giving developers a toolkit to accomplish this with pizazz, but there are a couple issues holding it back from its full potential:

The "dev kit" that Apple offers doesn't allow access to the phone's features. This was covered in my last post. Lack of access to the camera, microphone, speaker, alerts etc. hinder iPhone apps from being fully effective. MobileSafari's support for Web standards is subpar.  The implementation of the Web standards that Apple touted as an application development platform are disappointing.  Javascript behavior is slow and unreliable, and even some CSS properties do not behave according to the Web standards that Apple touted as the future of the iPhone.

This may have come as a surprise to Apple.As far as I know they have never said outright that the Safari browser and its Mobile counterpart can behave like two different animals, but as someone who spends a lot of time with both, I know it to be true. This is something that I had considered worth...

When I imagine a "digital lifestyle", it is long on "lifestyle" and short on "digital". I picture a level of integration between tech (iPhone, home computer, web applications and services), life (home, family, travel, friends) and the digital tracings of my life (photos, video, music, design, blog/microblog/ tumblelog) that allows me to enjoy what I'm doing without thinking about transferring from real life to digital.  It just happens, at least it does in my mind's eye. The advent of the iPhone had made it seem like the "digital lifestyle" was ready to integrate in this way.  Unfortunately, the actual product and process has fallen short of this mark. Apple's announcement that they are releasing a "real" iPhone SDK for native third-party applications is good news for the iPhone.  Applications so far, whether they were Safari Web apps or hacked native apps, have been restricted to a fairly primitive set of features. The main reason for this: no integration with the features that should make the iPhone a mobile wonder: camera, microphone, speaker, accelerometer on the hardware side, and Address Book, Calculator and Clock on the software side.

A good mobile app should be as transparent as...