Ivan Sutherland’s Sketchpad MIT thesis was covered by Create Digital Motion after I posted the video clip from MIT’s New Media Reader featuring Dr. Alay Kay from Xerox PARC give a lecture on Sketchpad. The video clip has since garnered over 10,000 YouTube views and other “instances” of the film on video sharing sites — so appropriate given Sutherland’s contribution of the idea of a “master” and “instances.” His contributions to computer aided design history extend well into its origins and beyond its final outcome.

Peter Kirn says it best — what I think, he was able to say about this…

Additional Demonstration Footage Also Emerged

This Sketchpad film on YouTube: Part 1

The computer has been, in a sense, nothing but a very elaborate calculating machine. But, now we’re making the computer be more like, almost like a “human assistant” and the computer will seem to have some intelligence.

It doesn’t really. Only the intelligence that we put in it.

{Emphasis added.}

Professor Steven Coons
Associate Professor of Mechanical Engineering at MIT
Co-Director of The Computer Aided Design Project

Steve Jobs “just says no” to Flash on iPhone. Well, on first glance, that’s just what he says now, and we all know, like a good episode of Lost, there’s always more to unpack and nothing is what it seems. Considering Adobe’s product line, the so-called “missing middle Flash product” suitable for the iPhone doesn’t yet exist. The middle product refers to something between Flash Player for the desktop and Flash Lite for mobile devices. But, considering the pipeline, it’s only a matter of time before Adobe AIR Mobile hits iPhone and just about every other mobile device, smack dab in the middle of the entire mainstream interactive media ecosystem.¹

Despite all the nay-saying, Adobe seems determined to get Flash on OS X Touch.

The brilliance of both Apple and Adobe waiting for Adobe AIR Mobile to launch is that it addresses all issues and pleases both parties politically:

• AIR Mobile is likely to be built upon AJAX, WebKit and Flash Player with the ActionScript 3.0 VM, as it is on the desktop, so it will be robust, efficient, modern and support both Apple’s and Adobe’s standards. It will please developers, designers, open standards proponents, lovers of proprietary goodness, and every other regular user who just wants everything to just work.
• AIR Mobile will solve the installation and distribution problem inherent in Flash Lite. Flash Player for the desktop has never been about standalone application installation. AIR on the desktop bridges this gap. It’s only a matter of time before Adobe sends AIR into the mobile device space and allows creators to put mobile app icons on standby screens with a few clicks. Just think Apple AppStore, or jailbreak AppTapp for Adobe Mobile AIR.
• AIR Mobile will bridge the fading distinction between web – desktop – mobile by allowing creators to write software in one environment (eg. Flex Builder) and distribute codebase to all three of these crucial platforms in a truly hybrid sense.
• It’s really no coincidence that Apple and Adobe are both investing heavily in products named “Air” — the notion of the data-cloud, cloud-sourcing, everyware, and webware is nascent. Narrow-minded jargon-lovers will call it Web 3.0, but intelligent folks will hopefully leave this lame version number moniker behind and use the appropriately visionary language espoused here.

Multi-touch API is the key

The central unresolved issue that remains is a multi-touch API. Any version of Flash for iPhone will need to have its intrinsic APIs updated for multi-touch and that will need to translate to a higher-level ActionScript object so that designers and developers can trap events related to multi-touch gestures. Without gestures like pinch, flick, zoom and others, it’s really pointless to put Flash on iPhone.

At the end of the day, talk about politics, performance and battery life are probably just the red-herrings that both Apple and Adobe need to work out the vexing issue of multi-touch APIs. In fact, it will probably take a few years before all platforms (Windows Mobile, Symbian, Android and iPhone) all reckon with multi-touch on all levels of hardware and software.

The alleged YouTube Mobile Safari plugin in OS X Touch 2.0 beta is probably all the beehive needs to chill out and give Apple and Adobe the breathing room they need to get multi-touch worked out, and deploy Mobile AIR on a dizzying and divergent array of devices, platforms and crotchety carriers.

Previously:

• YouTube plugin for Mobile Safari Suggests No Flash in iPhone 2.0←
• Will iPhone Ever Run Flash?←

Footnotes

1. This is based only pure postulation and not informed by any confidential Adobe insight.

Specula-palooza Rocks On

The latest in Flash and iPhone rumor-mongering suggests a YouTube plug-in for Mobile Safari will accompany this summer’s Touch OS 2.0 update. An uncorroborated claim indicates that this plug-in is contained within the recently seeded developer iPhone SDK 2.0 beta firmware.

This would theoretically enable embedded YouTube movies to work on the billions of pages that currently flaunt the dreaded blue question mark icon. Presumably, a page with an embedded YouTube SWF player might show a thumbnail with a play icon that when tapped would load the clip in the native YouTube player or some embedded player within Mobile Safari. This would be similar to what happens when you load an embedded MP4 video file via the native QuickTime player within the iPod function.

In technical terms, Mobile Safari may parse the OBJECT and EMBED tags that point to the YouTube SWF player and redirect the path to the video into its own native player.

It’s important to note that not all YouTube videos would work. In fact, numerous clips not encoded to MP4 H.264 remain only available in the Flash codecs Sorenson Spark and On2 and therefore would not play in the Mobile Safari YouTube plugin. Although, Apple and Google seem to be colluding to convert the vast user-generated video library over into the H.263 format. It’s truly doubtful that OS X Touch 2.0 contains additional video codecs beyond H.263.

However, rather than subscribing to comment stream appearing below rumor sites, this YouTube Mobile Safari plugin is very likely not a clue towards a Flash player for iPhone. In fact, this could be the kiss of death for the chances of seeing it soon.

This kind of Mobile Safari plug-in access is precisely what Apple is shielding from Adobe (and other third-party developers, thanks to the sandbox intrinsic to the SDK). In many ways, a YouTube plugin acts as a trojan horse to usurp dominance from Flash in favor of WebKit and open standards. For most people who crave a Flash Player for iPhone, it’s the frequent dead-end to embedded YouTube clips that has them most irked. Once that kink is worked out, will users really miss Flash?

The other crucial importance of a Mobile Safari YouTube plugin is that it bypasses the main sticking point: how to implement multi-touch via an ActionScript API in the Flash Player!

We’re not suggesting Flash Player won’t ever appear on OS X Touch, but if a native YouTube plugin appears for Mobile Safari this summer, it has big implications for Adobe’s mobile strategy, and concerns the long-term viability of Flash as a de-facto standard if the mobile medium cannot be captured.

We’d love to see Flash on OS X Touch. There is a vast designer and developer community out there fluent in ActionScript that would thrive in a Touch world. It’s all about a multi-touch API from here on out. We’ve tinkered with both Mobile Safari web application design with WebKit and AJAX and also attempted to pick apart Cocoa Touch. There is no middle ground yet, and the Touch application market is nascent and fractured as a result. You’ve either got really crappy web applications or sketchy jailbreak apps. Yes, this summer’s launch of the AppStore will change the game forever. But, until the vast Adobe-enabled developer community is employed to create, the market will be constricted by limitations and learning curves.

Previously: Will iPhone Ever Run Flash? ←

It has been awhile since posting to mercurious. However, we’ve been hard at work updating our academic site. This site now documents recent student work:

• Freshmen Processing work
• Muzzi, the digital pet —music player hybrid
• Info Wraps, a mobile informatics research project

It also now features a commercial work samples page that highlights an eight-year career in the interactive media industry. Perhaps the most interesting additions include ancient works from the vault, some almost a decade old.

In fact, getting this site together in this manner has been long overdue.

» New and improved professorial site on parsons.edu

Hyperbole Essay Muses a Protestant Split Over Jesus Phone

Release a breakthrough product, ready the defenses. Slash prices within 60 days of its release. Pre-test an elaborate consumer store credit program. Maintain control of user experience, revenue streams, and product integrity. Expedite firmware drops to shore up security against an unpredictably vigorous, yet independent, and ingenious rogue software design movement. Monitor ensuing online chatter and surveil the field, ready to deploy assets.

Such is the life of Applists, at the brink of factioning off into a ruthless, fringe element, no longer allegiant to Pope Jobs. These followers protest, disillusioned with the rejection of their effusive prayers and deeds in the name of the product’s church. Emblems of the faith, splendid exemplars of user interface mantras led by installers as elegant as “undocumented features,” spreading customizations and innovations of every whim as if Gnostic Gospel. Each passionate shortcoming of the breakthrough product, much hyped, yet still maligned beyond nitpick, had been redeemed, by painstaking devoted minds, dedicated to unlocking the mysteries of the revolutionary creation, without manual, in disobedience to advice and guidance.

Today the mark is 1.1.1 vs. 1.0.2 — those who have crossed over towards Applist orthodoxy and those resistant, not yet yielding, making due without holy sanctions, verified creed. Perhaps it’s the attraction of a more personal relationship with the Godhead, the sacred code, Kabalah’s sublime intertextual numerology, the open principles of touch-based human interface guidelines and their applications, Gnostic texts canonized by Memex. This divine intimacy of the populace is too much for the orthodoxy to stomach, unmediated transgressors. Only deep within the Vaticanal campus of Cupertino, could the details of iPhone be realized and celebrated through masses. Or could they? The orthodoxy obediently applies edicts from axis mundi, replete with sharia, releasing newly inscribed sacraments of commerce, and trivial revisions to interface ritual, all as sacrifices to the Godhead in the name of stablity, security, and eschatology. The reformists resist the superficialities of bug fixes, feature tweaks, and new revenue streams in favor of purist pursuits of homebrewed exchange and unmediated gadgeteering.

Watch the iPhoneDev splinter group, the prophets Erica Sadun, and her followers, all Digging, the global audience, Natetrue and Nervegas and Nightwatch, all the great disciples of the tripartite theory of Jobs, Ives, and Schiller; now splintering off into a Protestant reformation, rejecting the hegemonies, the hierarchies, the corporate religiosity that puts shareholder before stakeholder, priest before parishoner, mission before congregation, partner before customer, policy before press, business before pleasure.

Other churches reap followers by addressing the misgivings of these loud voices, the difficult choice of switching allegiances, and selecting new identities could be the most drastic reaction to the Applist inquisition. Once dedicated followers, so-called fanboys, mavens, influencers, the variously labeled, occasionally ridiculed, persecuted acolytes of American design purity, objects painstakingly assembled by Chinese workers, clothed in their consumer best, they are lovingly delivered to lavishly spoiled consumers, whose lives change instantly, noticeably, invisibly, despite clear markings and insignia.

Needless to say, we aren’t the only ones jolted into a state of doubt, of second-guessing, a crisis of faith. Our iPhones remain 1.0.2, our AppTap apps continue to dance upon our SummerBoard with a flick, semi-useless, yet somehow indispensable reminders of cherishing the essentials of open, of freedom, of flexibility. We remember not to take for granted the simple joys of the original Applist congregation, enabled to seek more personal relationships with what the breakthrough product enables, beyond expansion and customization: retrogaming, instant messaging, operating systemics, electronic literature, voice recordings, recreation, media redistribution, virtualization, and location-based positioning.

The factionalization inevitably reflects the disconnect between the hierarchy and its Diocese. Cupertino must enforce and enrich its control and influence over the essential elements of its worldview, the device software. There are specific fiduciary duties towards contractual partners and shareholders that assess profound regard in refocusing the consumers attention towards revenue streams and away from endeavors that distract from ongoing tithing. Yet the followers, in their humanistic zeal for coming to know the the device software more intimately, more greatly, more intrinsically, unlocked an interconnection that may not have even been intended for mere mortals. This Pandora’s box exemplifies the detachment of the Tripartite from its congregation. Such a clearly precedented trait of Applists was forgotten, and now fracturing ensues.

Will devotees of Apple fracture into subservient and subversive sects, now prompted to select allegiances?

Web Ink for Mobile Media Curriculum

Adobe published a case study on my work with students at Parsons Communication Design & Technology in the area of mobile media design.

Mobile Touch Screen WordPress Theme In The Works

In response to the proliferating importance of portable touch-screen interfaces, we have started the design and development of a WordPress theme for iPhone and iPod Touch devices. The theme will make your WordPress site look and behave like a native application, taking advantage of the special requirements of a touch-screen, flick-and-slide scroll interface minimizing zoom-pinching, all using Joe Hewitt’s iUI JavaScript and CSS library.

The project is currently in a pre-alpha release state. We have released an early alpha, with a distant dream publish it to the official WordPress theme site. Anyone who is interested in helping to test and develop the concept should contact us by email. Let it be known that we are not the first to attempt a WordPress iUI theme, although we are working a more comprehensive implementation than what Justin Barkhuff has already achieved while on his year-long honeymoon!

» Try WordPress Touch pre-alpha on your iPhone or iPod Touch.

If the Touch theme does not appear right away, keep trying, by refreshing or revisiting this link. For some reason, the cookie that tells WordPress to use this theme isn’t registering correctly.

Release Notes

• You can simulate the experience by viewing the Touch theme without an iPhone or iPod Touch by using Safari 3.1 or the Webkit nightly build, the iPhoney simulator, or the official iPhone simulator as part of the SDK.
• Viewing this theme in other browsers will probably yield unpredictable and undesirable results.
• Your browser will remember your theme choice in a cookie. To reset back to the standard theme, choose Preferences > Theme > Desktop within the Touch theme main menu.
• As stated above, if you don’t succeed in triggering the WordPress Touch theme to appear, be persistent. This is an known issue to be resolved. It has something to do with the theme switcher plugin I’m using.

Design Goals

• Optimize WordPress consumption for the WebKit touchscreen user-interface model — in progress
• Focus on mobile use-cases, to allow a quick consume, easy lookups — in progress
• Employ best practices for iPhone and iPod Touch interface design conventions — in progress
• Allow options for auto-detection, user-selection and return to standard desktop views — in progess
• Introduce glossy icons for menus, with preference to disable — to do
• Introduce auto-resizing thumbnail management and disabling LightBox photo gallery features — to do

Specula-palooza

Risking iPhone coverage overexposure, today we ponder one of the most interesting questions about the future of Flash, iPhone and web standards. Despite assurances by Uncle Walt that Apple and Adobe are hard at work on a Flash Player for iPhone, plenty of naysayers, skeptics, and player-haters have voiced strong speculations that Flash will never appear on the iPhone for strategic, practical and technical reasons. A quick scan of comments on various iPhone related entries across the web reveals an almost universal plea amongst everyday users indicating that a dearly missed feature from Mobile Safari is the presence of a mainstream multimedia plugin. In fact, the world’s most popular piece of software in history, is well known to be absent from iPhone.¹

Mobilizing the Means of Production

Those who have written about why iPhone should not have a Flash Player don’t mask their agendas. These voices are usually programmers and developers who have always been hostile to Flash, mostly because it threatens their grip on the means of production, by bringing software and interface design to the masses. Indeed, we’ve seen the worst and the best of the web, as a result. Furthermore, because Flash has always been a mainstream, populist, albeit proprietary media format, it has been deployed for reach and ease of creation, rather than robust performance. When imagining a Flash Player for iPhone, its high-octane thirst for processor cycles does not bode well for battery life.

Monopolizing Web Standards

The second significant argument against iPhone Flash is Apple’s strategy to deploy its WebKit “web standards” platform for all third-party application development. Indeed, the recently redesigned Apple.com site has reduced its use of Flash significantly, in favor of JavaScript and browser based features, so-called AJAX. The argument goes that Apple doesn’t want to forsake its influence on the consumer-level interface design market by inserting Adobe’s trojan horse into the battlefield.² This perspective does make a lot of sense, but leaves out a tremendous amount of nuance, that we’ll investigate here.

A Muted Voice

The assumption that web standards based technology, such as JavaScript, can wholly replace Flash functionality is only somewhat true, especially on iPhone.³ Certainly, the support of JavaScript and its embrace by the web developer community over the past three to five years has changed the face of the web, earning the popular title of version 2.0. However, Flash offers some essential multimedia capabilities that JavaScript alone cannot yet offer. This includes audio support. It’s no coincidence that Bejeweled for iPhone is mute. Especially considering that many iPhone users may have stereo headsets plugged in during use, there are unimaginable uses for audio based applications, especially when combined with locative media technologies. Imagine a sort of audiopedia. The differences don’t start and end with audio support, however. Even Apple’s newly touted Web Gallery feature, part of a .Mac subscription with the iLife personal media suite needs to use Flash for its carousel photo browsing interface.⁴ Indeed, only the Flash Player offers the multimedia engine to manipulate the images as a responsive interface with the reach required on this consumer grade product.

I Want My MTV

Certainly, the most common deployment of Flash Player on the web recently is for web video. It was almost shocking to watch the FLV video format surpass RealPlayer, Windows Media and QuickTime as the most important, influential web video format, in what seemed like a matter of months, with much thanks to YouTube and others. A recent Adobe Flash Player 9 public beta featured H.264 video support, which seems part of its strategy to preserve the dominance of Flash video, especially as Apple and Google migrate towards this non-Flash based video standard. However, until the myriad of embedded SWF FLV players on perhaps billions of web pages get updated to auto-detect the client and deliver the appropriate video by codec, the web will still appear to be littered with missing plugins on Mobile Safari.

Assumptions and Speculations

Let’s proceed with the assumption that Walt Mossberg was correct, and indeed, Apple and Adobe have reached an agreement to release Flash Player iPhone in some manifestation, at some time. Of course, he could be blindly speculating like the rest of us, just running on the fact that it feels crazy for Flash not to be there. But, let’s hope he’s as well-connected and respected as they say he is.⁵ There are several scenarios for the future of Flash iPhone, which should only contribute to the over-saturated discourse by further complicating the biased opinions with an understanding of Adobe’s perspective, previously, and conveniently left out of the discussion.

A Straight Port of Flash Player 9

In this scenario, Adobe compiles the current version of the desktop Flash Player 9 for the ARM processor of iPhone. This scenario would allow all of the existing web-based Flash content to function within Mobile Safari. Authors who create content in ActionScript 3 would enjoy a noticeable improvement of performance and energy efficiency on the iPhone, since this type of content would play in the more recent Flash Virtual Machine, a marked improvement over previous runtime environments, across Windows, Mac OS X and Linux. However, the vast majority of Flash content on the web right now was created in ActionScript 1.0 and 2.0, and so does not take advantage of the improvements to the runtime. Indeed, the skeptics are correct when they assume that running web pages with Flash content, even animated banners, would put an unfortunate drain on the battery.However, what’s crucially missing from a simple straight-on port of Flash Player 9 for iPhone is a substantial confrontation with the multi-touch interface. This is likely the deal-breaker for this scenario. Although, ActionScript and Flash button symbols might offer some means of developing and designing for the iPhone’s multi-touch interface, it’s more than likely that despite the best efforts of Flash coders, the existing means to respond to mouse-based interactions will fall short of the requirements needed to respond to multi-touch. Gestures like pinch, tap-zoom, and flick are difficult to imagine as ActionScript events. Indeed, Adobe probably needs to reckon with the reality that ActionScript needs a true multi-touch API. This could be one of the many reasons why we can only assume that iPhone Flash is in development now, and may be for quite some time, especially based on Apple’s delay in releasing an official iPhone SDK.

Probability: Very Low

Flash Player 10

Looking into 2008, perhaps third or fourth quarter, we have to assume that Adobe will continue to release improved versions of the Flash Player. Version 10 is likely to provide Adobe with the required release cycle needed to fully contend with Apple’s native iPhone application API and SDK release schedule. It’s much more likely that ActionScript libraries will be written that allow true response to the multi-touch gestures, such as pinching, flicking and zoom-tapping. It’s really difficult to imagine a Flash Player on iPhone without this crucial ActionScript API.Furthermore, this allows Adobe to potentially release new versions of the Flash and Flex authoring tools that will compile in Flash Player 10, and subsequently, support a runtime environment that is tuned to the needs of the ARM architecture and precious battery life. It’s been frustrating to read the Flash iPhone haters and their blatant neglect for Adobe’s expertise in the area of building a Flash Player for mobile devices. There has simply been no mention of the possibility of Flash Lite for iPhone.

Probability: Medium

Flash Lite 2.1

Flash Lite is a very special version of the Flash Player for mobile devices, such as Symbian Series 60, Windows Mobile and others. It is not the Flash Player that typically sits in an embedded browser, like the vast majority of Flash content out there. Instead, Flash Lite content exists as standalone, full-screen, mobile applications, or more appropriate mobile media implementations such as a standby screens, wallpapers, screen-savers, and even the device’s native UI.Not only is Flash Lite compiled to the particular device, and so is limited by its processing and memory capabilities, but it also has proven to be very energy efficient, accordingly. Indeed, authors must specifically design and code for Flash Lite. It is in no way, a conversion from desktop Flash content. In this manner, designers and developers alike, are rightly forced to contend with the requirements of mobile media, in terms of interface, content and use-case considerations.It’s possible that Adobe could port Flash Lite to iPhone instead of the expected desktop Flash Player. In this regard, Flash Player would exists as a widget on the SpringBoard home-screen of iPhone, and not as a Mobile Safari plugin. Although it would not fix countless broken plugins in pages that use Flash Player, it would offer mobile media design opportunities for Flash on iPhone. Specifically, Flash Lite already offers APIs to interact with mobile phone specific features, such as triggering the vibrate, detecting battery life, and cell network signal strength. These capabilities are not offered on the desktop version of Flash Player, and may or may not be available in Apple’s official native iPhone application API or SDK. Only time will tell.In this scenario, Flash Lite becomes an avenue for designers and developers familiar with Adobe’s toolsets to create applications that exist as standalone native experiences, rather than embedded modules of Mobile Safari. In many ways, this supports the special needs of mobile media more appropriately than simply making the familiar Flash just work. Imagining a port of Flash Lite for iPhone could mean the opening of a vast market for native iPhone widget applications, designed by designers, and not restricted to hard-core Objective C programmers. Indeed, this is a threatening prospect for those that are eager to carve out a niche in iPhone application development. However, Flash Lite 2.1 probably does not offer the means to react to multi-touch gestures like pinch, flick and tap-zoom, and so it’s probably not the version we will eventually see.

Probability: Low

Flash Lite 3

Just as the desktop Flash Player is constantly updated, the mobile Flash Lite player is also expected to be evolving. It is said, that a forthcoming version of the Flash Lite player, perhaps 3, will bridge the gap between the embedded browser Flash content and the standalone mobile specific Flash Lite content.⁶ In other words, Flash Lite 3 could play not just in the mobile device’s web browser, but could also run within its native operating system environment. This jives with Adobe’s efforts to seed the use of Flash outside of the browser and distribute a desktop based native runtime, called AIR, the Adobe Integrated Runtime. In addition, a Flash Lite 3 would address the concerns of a multi-touch API, and the required energy efficiencies for battery life, memory usage and processor cycling, as well as provide ActionScript to trigger mobile device specific features intrinsic to Flash Lite.In this case, Flash would exist in two manifestations on iPhone: as standalone native applications on the SpringBoard home screen, and as a Mobile Safari plugin, playing the usual desktop based content. This gives developers, designers and end-users the best of all worlds. Flash content can be created with mobile use in mind, considering the unique user interface and energy efficiency required. Everyday users will enjoy not only the full multimedia web they’ve grown accustomed to on the desktop, but also will enjoy a market of native mobile applications that arguably, the Objective C programmers of the world, simply cannot singlehandedly service.

Probability: Medium-High

Conclusions

Flash will appear on iPhone eventually. There is no doubt that Adobe will roadmap this device into its strategy for Flash Player, Flash Lite, or both.Yes, there are significant performance, interface and user considerations that must be addressed as Flash appears on iPhone. Adobe has already demonstrated an accomplished ability to service the mobile media market. It’s only a matter of when, and what form iPhone Flash takes as it appears beneath our beloved glass multi-touch screens.One can only imagine the pressure Adobe’s product planners are putting on its Flash Player team to fit iPhone into the needs of the short-term and long-term strategy. In the short term, Adobe needs to get Flash on iPhone within the next three to six months to capture the required developer and designer audience, and compete with the ascendancy of Mobile Safari and native iPhone applications. In the long term, Adobe needs to get it right, and release a iPhone Flash Player that addresses the specific needs of both mobile media and the vast legacy of desktop Flash content out there. A premature release could spell long term disaster for Flash, as it needs to compete with the rapidly expanding Open Source and Web Standards movement. We haven’t mentioned Microsoft’s entry into the web media space with its recently launched Silverlight platform, but until we stumble upon a site that actually uses it, it’s irrelevant.Although there are many who would like Flash to just go away, because it’s not open source, not free, and tends to be used to bombard us with annoying banner ads and horrible interface design models, Flash is not going away anytime soon. However, how Apple and Adobe navigate the uncharted territory of merging mobile and desktop user experiences along with multi-touch interfaces, will certainly determine the relevance of Flash in the years to come.

Footnotes

1. See Adobe statistics on Flash Player downloads.
2. See Roughly Drafted’s analysis.
3. See A List Apart’s analysis.
4. See Cabel Sasser’s Twitter which claims dibs on this observation.
5. See the profile of Walt Mossberg in the New Yorker.
6. Speculative, but based on reliable, but undisclosed interactions with Adobe. Also, see Bill Perry’s entry on the subject.

Read Packing Lite: A mobile media interface design primer on Adobe’s Developer Center to get my perspective how to adapt to directional-pad based devices in Flash Lite. I detail the process of transferring SWF files to Nokia Series 60 devices and analyze a 4-way menu example from Adobe’s Content Developer Kit (CDK).

» Packing Lite on Adobe.com

Nullriver Software releases full GUI iPhone Installer

iPhone enthusiasts and novices rejoice as the first native application installation software is released allowing you to install and maintain 3rd party iPhone applications in a user-friendly, graphical interface. Multi-step command-line hacking is no longer required to get programs installed into your iPhone. A natural Mac installer automates the process of getting the installer set up on your iPhone. Enjoy the beta before it goes shareware, as widely anticipated. This makes our own step-by-step guide← and countless others somewhat obsolete!

Download AppTapp Beta →

Article to be published on Adobe Developer Center

Packing Lite: Getting Started Designing Interfaces for Mobile Media

I wrote an article/tutorial for Adobe’s Developer Center to be published at the end of August covering how to get started designing interfaces in Flash Lite on Nokia Series 60 devices. It details how to get equipped for mobile media design using Flash and the Flash Lite platform, install Flash Lite content on Nokia S60 phones with Bluetooth or Nokia’s PC Suite, discusses the unique interface design challenges, and looks at an example, highlighting the issues.

Stay tuned, as I’ll be sure to post the link to the article when it goes live. Article pushed live at 5 PM PST, August 17, 2007←

For the uninitiated, Processing→ is an open interactive media platform published on free software license via MIT by Casey Reas→ and Ben Fry→. Originally created as a learning tool, it is maturing through a Beta phase currently while winning tremendous support within the academic and design community. It appears to be emerging as the [tag]Sketchpad[/tag]↔ of the future. Sutherland→ would be so proud of his fellow alumni.

• Download Sample Chapters→ in PDF
• MIT Press→

For those in-the-know, this MIT Press release, Processing: A Programming Handbook for Visual Designers and Artists will be noticed on August 24, 2007. A substantial amount of the book is available in PDF format now. The free preview certainly suggests how tremendous and definitive this text is going to be. Take a peak at this inspiring passage from the introduction. It begins by describing the world view of Processing and the philosophy about software it epitomizes:

Software is a unique medium with unique qualities
Concepts and emotions that are not possible to express in other media may be expressed in this medium. Software requires its own terminology and discourse and should not be evaluated in relation to prior media such as film, photography, and painting. History shows that technologies such as oil paint, cameras, and film have changed artistic practice and discourse, and while we do not claim that new technologies improve art, we do feel they enable different forms of communication and expression. Software holds a unique position among artistic media because of its ability to produce dynamic forms, process gestures, define behavior, simulate natural systems, and integrate other media including sound, image, and text. (p. 1)

The introduction continues on to beautifully frame the pursuit of aesthetics through software. The free preview includes not only complete Table of Contents and Index, but also a very solid introduction to Processing and some of fundamental concepts. It’s enough material to function as an ideal free resource for getting started, while also leaves you thirsting for more.

Indeed, a more comprehensive review is forthcoming.

Adobe Integrated Runtime demonstrated by Big Spaceship.

This afternoon, Joshua Hirsch and Jamie Kosoy from Big Spaceship, here in Brooklyn, presented Building Adobe AIR Applications with Flash CS3 on the Adobe Connect presentation service. They did an excellent job of introducing the new capabilities of Adobe’s new desktop application delivery platform. In particular, they focused on how Flash CS3 can be used to compile AIR programs. Although still in Beta, AIR remains un-implemented in Flash CS3. The online seminar walked us through the tricky process of configuring for AIR development and introduce us to the command-line tools required to build and test AIR projects. However, Grant Skinner apparently has an extension set for Flash CS3 that assists with this process as we await Adobe’s full integration into the Publish Settings of Flash CS3. The links and notes of the presentation are posted here for reference. This post is likely to be updated and fleshed out as I process and try things out myself.

What is AIR?

AIR brings Flash and other web formats to desktop standalone applications. We should start to see more ‘downloadables’ once this catches on. Probably the best way to figure out AIR is to look at some examples on Adobe Labs→I’ve been a fan of kuler→ ever since I started following the Adobe Labs, and discovered Apollo, the codename for AIR. This is a great example of how being able to break out of the browser will encourage creative technology to engage with us more deeply.

Presentation Links

How to get started with AIR and Flash CS3

• Presentation Event Details
• About Adobe AIR
• AIR Developer FAQ
• Download AIR SDK
• Download FLEX Builder
• ActionScript 3.0 Language Reference
• Get the Flash Debug Player
• Get FlashTracer extension for Firefox
• Get Grant Skinner’s AIR Panel for CS3
• Big Spaceship’s Lab

Raw Notes from the Presentation

Here are the raw notes from the presentation. I’ll try to decipher them into more sense once I get my head around it all myself.

 airglobal.swc locations: MAC:    /Applications/Adobe Flex Builder 3/sdks/moxie/frameworks/libs/air/airglobal.swc PC:      Program Files/Adobe Flex Builder 3/sdks/moxie/frameworks/libs/air/airglobal.swc move and rename to MAC:    /Applications/Adobe Flash CS3/Configuration/ActionScript 3.0/Classes/playerglobal.swc PC:      Program Files/Adobe Flash CS3/Configuration/ActionScript 3.0/Classes/playerglobal.swc (you should make a backup of your old playerglobal.swc) AIR SDK: MAC:    Place all files in /Users/[you]/ PC:      Place files whereever you want. (I use c:AIR_SDK) Set environment variables: Right click "My Computer" Hit Properties. Go to the "Advanced" tab Click "Environment Variables" In "System Variables", under Path add path you put the sdk. If there is no Path var, you can add it. ADL syntax: adl myApp.xml Flash Tracer: After installing extension, Tools --> FlashTracer Click "Options" in the bottom right of the AddOn. PC Path MUST be: C:Documents and Settings[YOU]Application DataMacromediaFlash PlayerLogsflashlog.txt Mac Path MUST be: Hard Drive:Users:[YOU]:Library:Preferences:Macromedia:Flash Player:Logs:flashlog.txt If no Logs directory or flashlog.txt file is missing, you need to add them. ADT syntax: adt -package myAirFile.air myApp.xml foo.swf bar.swf icons videos etc

Between 1962 and 1964, Dr. Ivan Sutherland created Sketchpad: A Man-Machine Graphical Communications System, arguably the world’s first computer graphics system, and non-procedural programming system.

Video

In this video, Dr. Alan Kay, from PARC, discusses Sketchpad and its significance in determining the nature of Object Oriented graphical interfaces.

[flash http://www.youtube.com/v/495nCzxM9PI]

Geneology

In this Computing Family Tree diagram◊, note how Sketchpad is considered the origination point for the modern operating system, as we know it.

Links

• Sketchpad, PhD. Dissertation, .pdf (3.9 MB) ↓
• Sketchpad, Wikipedia→
• Sketchpad, YouTube→
• Sketchpad, Archive.org→

See Also

Lecture: The Origins of Interactive Media ↑

Originally published in the Atlantic Monthly→, “As We May Think→” (July, 1945), a member of the Manhattan Project proposes the [tag]Memex[/tag]↔, a sort of microfilm-based knowledge desk. Many consider the Memex to be the pre-digital precursor to the idea of the Web and Internet as we know it today. It may reflect the dawn of the information age.

I am constantly referring to the Memex in my [tag]lectures[/tag]↔ and research as a significant historical precedent to modern informatics, information design, hypertext and interactive media.

A diagram depicting “Computing’s Family Tree”◊ sources the Memex at the root of all modern operating systems. See also Dr. Ivan Sutherland’s [tag]Sketchpad[/tag]↔ for the world’s first interactive computer graphics system.

Links

• Original article, Atlantic Monthly→
• “As We May Think”, Wikipedia→
• ‘Memex,’ Wikipedia→
• ‘Informatics,’ Wikipedia→

See Also

Lecture: The Origins of Interactive Media ↑

Impressions.

Although Gizmodo→ is recommending that those who haven’t already early-adopted should wait for the first software update, the iPhone is a stunning achievement. Really the only salient reason offered by Gizmodo for waiting applies to users who constantly MMS and/or SMS to multiple recipients. Despite owning many phones capable of both these features, we must admit that we rarely, if ever, use these features. Otherwise, the iPhone offers a feature set where we find ourselves using it instead of our laptop, perhaps because the elegance of the multi-touch interface makes the conventional OS seem blasé by comparison. Or, maybe it’s that we truly enjoy the personal nature of using the device, and marvel at its ability to overcome the limitations of the screen size, input methods and network capabilities.

Problems.

Update, August 2, 2007: iPhone Sofware Update 1.0.1 delivers the goods→ 

Unresolved issues that are real disappointments.

1. Issue Resolved→  The iPhone Car Bluetooth interface is not working well with my Audi A3 factory Bluetooth integration. Although it pairs beautifully and offers a terrific integration with the navigation system’s interface, the Bluetooth connection does not remain connected, and periodically drops and inconsistently reconnects. Perhaps the polling frequency of the Bluetooth software implementation needs to be adjusted in the forthcoming software updates to more reliably maintain the headset profile connection?
2. Issue Resolved→ The iPod Car integration kit is not working. This extremely expensive, official dealer-installed accessory that allows an iPod connected through the glove box to offer audio playback through the factory unit and charging does not seem compatible with the iPhone. The compatibility warning appears, suggesting the Airplane Mode to be activated. In either setting, the audio does not playback through the system. It is reduced to an inconvenient car charger. This is perhaps our greatest disappointment and we do hope that Apple improves compatibility with various Dock Connector accessories in the future updates.
3. I hate to write about this, but indeed, my first iPhone was a lemon. It froze, crashed and resisted the restore process. AppleCare customer service and my local Apple Retail store offered stellar customer service, however, and gladly replaced my unit, without much hassle. The replaced unit runs flawlessly, and clearly, there was a hardware issue, probably a faulty NAND RAM unit with my first one.

Wish List.

The Top Ten features that we’d love to see in the forthcoming software updates.

1. Junk Mail filter. It’s a shame that junk mail filters have truly become an essential aspect to any usable email client, and anyone who uses a standard POP or IMAP account can attest to the difficulty of using the iPhone email client without spam filtering.
2. Improved Bluetooth implementation. We’re talking full A2DP wireless stereo headset support, more aggressive polling to maintain headset or car kit connections, and full disk mode access via Bluetooth. Basically, a non-crippled, optimized implementation, and that’s not too much to ask.
3. Improved Dock Connector accessory compatibility. Obviously, Apple is worried about the interference caused by the AT&T cellular network frequencies. You’ve heard that distinctive ‘dih-dih-dih-dih’ that interferes with speakers nearby your phone as a call comes in. It would be better if you could accept this interference and enable full compatibility mode for legacy dock connector devices.
4. Disk Mode. You should be able to mount the iPhone as a USB drive and through Bluetooth to exchange files. This should also enable the file based editing of wallpapers and ringtones. In addition, manual media management should be allowed through drag-and-drop control in iTunes, as supported in iPod connections.
5. iChat. Surely, AT&T strong-armed Apple into not including iChat on the initial 1.0 release to swindle customers into opting for biggest SMS account features. It’s no coincidence that even the most expensive plans limit text messaging to 200 per month. However, an iChat client offered by Apple is badly needed.
6. Games. The multi-touch interface, motion sensors and brilliant screen are begging for games. You simply need something to enjoy on this device while you’re in the subway or in other network dead-zones. Not to mention, games are, uh, well, fun.
7. Nike+ compatibility. The Nike Plus system should work on the iPhone. It is not recognized as a compatible accessory.
8. Dock Remote Control. This is perhaps the most elaborate request, that will likely be enabled by a third-party and then absorbed by Apple into a Leopard upgrade release. We’re talking an SMS interface on your laptop/desktop, call control with caller ID, brightness/backlight control, iTunes remote access (so you can play off your iPhone instead of off your main device), and the ability to configure certain settings.
9. iSync Bluetooth synchronization support for Contacts, Calendars, Notes, non-media data. Obviously, Bluetooth is too slow to sync media files. But that feature could be achieved over WiFi, as is implemented on the Apple TV product.
10. iTunes Music Store. We’d like to buy music, movies, TV shows, games and subscribe to Podcasts directly on the device. Maybe it would only work while on a WiFi network until the 3G iPhone arrives, someday.

The Origins of Interactive Media.

交互式多媒体的起源

A brief examination of two influential American scientists who pioneered the idea of interactive information systems and graphics. Dr. Vannevar Bush, The Memex↑ and Dr. Ivan Sutherland, Sketchpad↑. Their research accomplishments resonate through every aspect of modern computing. A lecture given on Thursday, June 21, 2007, 13:30, Room B413 at the Academy of Arts & Design, Tsinghua University.Sponsored by Information Art & Design in collaboration with Communication Design & Technology, Parsons The New School for Design.

Lecture downloads available below.

Lecture Images

Lecture Downloads

» Download Lecture PDF↓ (6.5 MB)

» Download Lecture PowerPoint with QuickTime video ZIP ↓ (135 MB)

» Download Lecture Poster PDF ↓ (780 KB)

» View Lecture SWF in a Popup Flash Player → (20 MB)

See Also

• Memex, The Dawn of Informatics↑
• Sketchpad, The World’s First↑

A collaboration between the Academy of Arts and Design, Tsinghua University, Beijing and Communication Design and Technology, Parsons The New School for Design

Objective

Develop a design prototype to present to the Art and Design Academy and BOCOG proposing an interactive Mobile Visitors Guide for the 2008 Beijing Olympiad. Comprising of a desktop web product and a downloadable mobile media component, the Mobile Visitors Guide will offer travelers to Beijing helpful information about Olympic events, venues, the visual identity system, transportation, language assistance, and the unique and vibrant culture of China. In particular, the mobile component offers visitors a useful electronic assistant to navigate the city and manage culture shock and language barriers.

Goals

The workshop students (RedStudio) will present prototypes and design documents suggesting and demonstrating how this product might be further defined and developed. The short timeframe (three weeks) will not allow the creation of a fully functional product, but we hope that it inspires further study and development.

Solution

Adobe Flash technology offers the best platform to rapidly design and prototype the Beijing Olympics Mobile Visitors Guide. Using Flash Player to deploy the desktop web feature prototype and Flash Lite to deploy the mobile media prototype on Nokia Series 60 handsets, the students will easily integrate design and content across delivery mechanisms for a unified and integrated user experience.

Mobile Media Enabling World Class Hospitality

Everyone knows that the Chinese are famous for great hospitality, and preparing for the 2008 Summer Olympics is no exception. However, the rapid pace of development and the intricacy of the Chinese language and culture creates
barriers for visitors to enjoy their experience in Beijing. Now that most people carry a mobile phone or laptop when they travel, the Mobile Visitors Guide solves common problems for foreigners to help them communicate across languages, discover the delights of the city, manage its challenges, and more easily find their way around.

An Essential Companion

In the New China, driven by high technology and media innovations, visitors to the Olympics Beijing 2008 should enjoy digital services to help them make the most of their time here, whether on their laptop or mobile phone. Consider these modules:

• Find your way. Visually link event schedules to venue locations and find your way by subway, taxi, bicycle or walking.
• Keep score. Follow sports events by medal counts, in real-time, as winners are announced.
• Communicate. Blaze through the language barrier with common translations for useful phrases and situations on your mobile. Get pinyin transliterations, hanzi characters and audio pronunciations. Point your way out of a tricky situation using Chinese characters on your mobile’s screen. Hand over your mobile and let the Beijinger listen to your needs.
• Participate in China’s Cultural Olympics at the National Art Museum of China and use a mobile phone in an experimental large-scale group interaction within the gallery spaces.
• Explore and discover the Old Beijing and take a guided tour through the famous hutongs, an intricate maze of traditional culture and cuisine.
• Meet the Five Friendlies. The Fuwa have a great life story and getting acquainted with them will help you better enjoy their intricate symbolism which elegantly evokes the many layers of Chinese language and culture, not to mention the universal spirit of the Olympics.

Conclusion

This project prototype was presented to the Academy of Arts and Design, Tsinghua University on June 20, 2007. Relevant industry critics from Nokia and Microsoft R&D laboratories in Beijing attended the presentation.

Presentation Photos

See also

Red Studio: Teaching Design at Tsinghua↑