I’d like to start with one of the changes to application state management. Starting in OS X 10.7, developers will have API’s similar to iOS, and possibly requirements as well, to auto-save their application state. This means that when a user exits an application, and relaunch, it will re-open right where they left off. In addition, a few keen-eyed observers have noticed a lack of running application indicators in 10.7′s dock. This indicates to me that the dock will become similar to iOS’s dock, merely a launch area for frequently used applications, and not a means of managing open applications. This, combined with auto-state saving for applications, and an emphasis on full-screen application view, also indicates to me that the operating system will also handle memory and process management the way iOS does. Developers should no longer expect to leave their applications running at all times.

Obviously, if application state management changes to an iOS style system, then we should expect drastic performance increases on the Mac computing platform. If an iPad or iPhone can perform the way they do with the A4 processor and limited RAM, imagine what a desktop can do with copious amounts of RAM and processor power.

Another item I found very interesting was the introduction of the Mac App Store. While a logical next step for Apple, it caught me by surprise. I think this is a particularly noteworthy evolution of the Mac platform for both developers and end-users. To my eyes, the Mac App Store brings:

• Exposure for end users to indie software. Many new users to the Mac platform miss out on a lot of the capabilities of their Mac, simply because they are unaware of third-party hole-in-the-wall websites for software. Now they will see new and nifty applications highlighted for them, as well as Genius results for software they might also like.
• Exposure for developers. No longer a little site in a corner of the web, with their software going un-noticed. Now a proper repository, with great exposure, and millions of eyeballs viewing.
• Easy software maintenance for end users. Once a user has purchased software, updates will become something routine, a habit formed when they visit the App Store. Developers will have much less likelihood of having to troubleshoot out-of-date software. Not only easy maintenance of updates, but also easy maintenance of licenses. No longer a requirement to store different license files or keys in some central backup location or email.
• Easy software distribution for developers. Developers no longer have to worry about creating proprietary licensing or activation mechanisms. They no longer have to worry about creating a website to host their software. They no longer have to be concerned about creating proprietary updating mechanisms. All can be done through the App Store.
• Easy in-app upgrades. A new mechanism for developers to add extra content into their applications. Enough said.

The Mac App Store is a noteworthy addition to the Mac platform. I completely understand Apple’s decision to push it out within the next 90 days.

Another item of note is the coming of Push Notifications in the FaceTime beta. I suspect we’ll see this fully implemented in OS X 10.7. I suspect this will give rise to a new class of desktop applications and services.

These are the things I think particularly noteworthy in Apple’s next OS. Snow Leopard was a performance upgrade. OS X Lion looks like it will be an upgrade that brings huge advances in refinement to the desktop computing experience.

The reason I suggest that IT pros study design principles is so that they learn to appreciate the ‘user-level’ features for what they are, not dismissing them as merely useless pieces of eye-candy. When a tech can look at an object or interface, and not allow their ‘function over form’ mentality to get the better of them, they can better relate to how the user will experience the interface. When the tech appreciates on some level what the user appreciates, understanding between the two parties can grow.

Hand-in-hand with the previous point, IT pros should also study user interface experience. By beginning to understand how to implement or at least structure a good user experience, the eyes are opened to a new perspective on how the world functions. Studying and ingraining good UX principles in the core of the tech’s mentality will drastically shift how they approach their users, and how they approach the potential technologies to be implemented.

Now, you may ask why I’m suggesting the actual techs learn these things instead of just ensuring that the head folks know and understand these things. I’m a firm believer in the ancient Greek holistic approach to education. However, beyond that, I think that while the head of the body is responsible for the rest of a person’s functionality, when the whole body is trained and tuned to the same level, the performance level of the particular body jumps exponentially. Consequently, new and previously unattainable heights can be reached.

If you’re interested in some design oriented websites, check out these for examples (mostly centered around web design):

Smashing Magazine: http://www.smashingmagazine.com
Noupe: http://www.noupe.com
Net-Tuts: http://net.tutsplus.com

What is Flash used for? In my experience, Flash is generally used for the following:

• Ads
• Games
• Music Players
• Movie Players
• Photo Galleries

Lets look at each one of these categories in a bit more detail.

Ads: Those annoying, flashy (excuse the pun) banners you see on some of the riff-raff sites of the internet. The big, ugly, strong-coloured patches in the websites you visit… generally are Flash. Very few people appreciate Flash ads. As a matter of fact, they were one of the leading instigators in the ad-blocking plugin market.

Games: This I believe is the only category that truly justifies the ‘interactive’ benefit that Flash provides. There is nothing else that remotely comes close to the power of Flash interactivity for web interface games. However, I have a problem with the category. It is generally either children or reclusive adults that tend to play Flash games. The majority of the adult population use the web for information consumption. The majority of children/teenagers will use a dedicated gaming device. I also think that as the iTunes App Store market matures in the gaming category, the majority of users will find much more value in natively coded games.

Music Streaming Another category that Flash is very prevalent in usage. Sites like MySpace, Last.fm, and others tend to use a Flash player by default. The reason for this is that Flash tends to be a very quick, easy to implement solution for music playback and playlist generation. There is nothing else available right now that offers the webmaster anything nearly as easy to implement. Until HTML5 becomes a bit more prevalent, Flash will be used de facto for music playback in the browser. Fortunately for us iPhone/iPod Touch/iPad users, some of these sites have published API’s, and some have their own dedicated app in the iTunes App Store (e.g., Last.fm). Also, the majority of iPod Touch/iPhone/iPad users will have iTunes syncing their music to their device.

Movie Players I would argue that this category would come close to Music Streaming in prevalence of Flash implementation. Unfortunately for Adobe, HTML5 offers a native implementation for movie streaming, via the ‘video’ tag. As HTML5 browsers become more prevalent, and sites like YouTube switch to either a single HTML5 portal, or a dual HTML5/Flash service, Adobe will have a harder time justifying the need for Flash in the Movie Player category.

Photo Galleries As an amateur photographer, I’ve found that the many self-hosted photo gallery solutions for servers are Flash based. However, this is again generally due to laziness on the part of programmers, or because there are a lot of easy, of-the-shelf solutions for the photographers with little computer knowledge. There are many native web coded galleries that work just as well, and are not hard to implement. Unfortunately, the majority of photographers do not have much of a budget for displaying their photos on the web, and generally hire a low-cost (usually inexperienced) web developer to build a photo site for them. There’s no technical justification for using Flash to display a gallery of photos.

Over the next few years, as HTML5 capable browsers become more ubiquitous, and providers start providing dual-service HTML5/Flash streaming, the need for Flash Movie Players will become miniscule. Thanks to the iTunes App Store, the desire for Flash games is swiftly disappearing. As applications like Lightroom and Aperture continue integrating web-publishing, photographers using professional tools for their photos will have less and less need to hire a third-party, inexperience web developer for Photo Galleries. In the end, the only justification for a webmaster to use Adobe Flash is for publishing Ads, and using it as an easy-to-implement Music Streaming player.

Microsoft obviously is not going to take the iPad challenge lying down, and will be touting Windows 7 as a more complete experience (Flash anyone?) than the iPad OS. Unfortunately however, I don’t see Windows 7, good as it may be, to be a worthwhile competitor to the iPad, due to the reason outlined above. So what should Microsoft do?

I firmly believe that if Microsoft wants to take on the iPad, it needs to build a tablet from the ground up. They’ve got some great software and hardware engineers¹, and should leverage that talent to build a complete Microsoft tablet experience. Integrate it with Zune and Xbox. They’ve got the Zune app store and Xbox download on demand. Utilize the existing frameworks and build a custom, performance tuned device that can compete with the iPad. Microsoft has proven it has both the hardware and software talent… now they need to be combined.

First, in response to John Nack, who makes the point that Flash has brought standardization to the web. Yes, while it did bring a standard to the web for a while, once Adobe purchased Macromedia, Flash itself started fragmenting into many different versions which supported different levels of features. This resulted in many users having to upgrade their Flash plugins depending on the site visited. How is this any better a ‘standard’ than HTML5? Might as well force the user to upgrade their browser to a standards-compliant version.
So, Flash provides ubiquitous browser video playback? Who cares? YouTube and Vimeo are switching to HTML5, Hulu is committed to providing iPad compliant service, and everyone else doesn’t care what they use to play video in their browser. As Internet Explorer 8 begins mass penetration (via Windows 7) and Internet Explorer 6 support is dropped (as Google announced yesterday), Flash will become less & less important. Lets be honest here. The only reason Flash is really needed is IE6′s existence. Everything else can and should be implemented via HTML5 and standards-compliant services such as OpenType.
John Nack concludes with a point that the Flash team will likely be using the GPU to bring fast performance to the desktop plugin. Who cares? The iPad and iPhone are mobile devices. Utilizing a separate GPU to do the processing is irrelevant on a mobile device that uses System-on-a-Chip design.
He also makes the point that the download size for QuickTime is twice that of Flash. Irrelevant. Most of the Flash-haters he is targeting with this post (and most Adobe CS users) are running a Mac, with native support. And most people with iTunes installed (read: everyone with an iPod/iPhone) have QuickTime installed as part of Apple Software Update. So no, ubiquity is not dependent on the download size of your plugin.

Second, in response to The Flash Blog. Have of the sites you illustrated have an iPhone compliant version (as pointed out by Mark Hughes here), and likely more will by the time iPad launches. Other sites have worthwhile iPhone app alternatives. Why should I use your plugin if the iPad supports native HTML5, and the majority of video media is capable of being delivered to me that way (YouTube, Vimeo, and Hulu?) I don’t want to play Flash web games, and with the iPhone/iPod Touch/iPad, most games that people will be playing will be native iPhone apps anyway. So there is no use for Flash for media playback or gaming on iPhone OS. What does Flash offer me then?
Your Flash plugin performance sucks. Small wonder Apple didn’t want didn’t want a battery pig like that on the iPhone and iPad.

Flash is dead. I hate the platform with a passion, and while I’d love to watch it die a long and slow death, the faster it goes the better. With Google’s latest announcement that they will stop supporting IE6, HTML5 ubiquity will hopefully begin. Flash is useless if my content is delivered to me through other streams, whether the iTunes store, HTML5, or a dedicated app. If I want an ‘interactive’ game, I’ll stick with a native iPhone or iPad application. There is nothing that Flash offers me, and no real way for it to ‘innovate’ against the march of technological progress. Welcome to the New World folks.