Tag Archives: flash

Ben Truyman | Critical Mass Chicago

In this post, I’d like to outline a handful of techniques and technologies we as creators for the web can employ today. Although some of these methods are only available in more modern browsers, I hope to explain how we can still maintain support and offer alternative solutions for older browsers.

A Bit of History

Back in 1997, I had just began dipping my feet into web development — more specifically HTML. Later that year, a new version of the HTML specification was to be released, known as “HTML 4.0”. Three U.S. Presidents, a dot-com bust and a housing bubble later we find ourselves still writing the same old HTML, now “HTML 4.01”. CSS shared a very similar story. Technicalities aside, my point is simply this: HTML and CSS have not seen a new major release of their specifications in several years.

The Future Is Now

You may have heard that there are two new kids on the block: HTML5 and CSS3. Although both of these specifications haven’t been finalized, modern browsers are beginning to implement features of HTML5 and CSS3. Of course, older browsers don’t have most of these features, but that’s okay.

Think about this for a moment: we’re still supporting and trying to create “pixel perfect” designs for Internet Explorer 6, a browser shipped with Microsoft’s nine year old operating system Windows XP. Let me say that again, we’re still designing websites that are meant to look exactly the same in modern browsers like Mozilla Firefox and Google Chrome but also a browser that is almost a decade old. Sad, but true.

Here’s where I propose we ditch that old idea and start using something I call “pixel imperfect” designs by using a well known strategy called Progressive Enhancement. Essentially, one design does not fit all browsers anymore. We need to accept the fact that browsers ARE different and they each offer their users different capabilities. We’ll need to start creating variants of our designs to show the potential experience in both modern and legacy browsers. What’s great about using Progressive Enhancement is that we can design our solutions in a way that less capable browsers still receive a great experience because we’re simply “layering” on new features that more capable browsers will utilize when they’re supported.

Implementations

Font Embedding

Arguably one of the most (if not THE most) important additions to CSS3 is the official support for embedding fonts. No longer are we stuck with having to cut images or use Flash when we want to use fonts not considered “web-safe”. We can use whatever fonts we want as long as the seller of the font permits web embedding. Several font providers like Typekit and FontShop are already providing solutions for embedding fonts on the web.

browser font embedding photo

No more opening up Photoshop to do minor copy tweaks, or re-cut all of a site’s images containing copy when we want to translate it to another language, or using slow Flash solutions unsupported by most mobile platforms.

The best part about CSS3 font embedding: it’s supported in virtually all browsers used today! That includes Internet Explorer 4+, Firefox 3.5+, Opera 10+, Safari 3.1+, and Chrome 4+.

What Else? Do I see Drag ‘n Drop?! Read On

View CommentsAdd a comment

David Fasullo | Critical Mass Toronto

Flash was only the beginning.

Today, if there’s one thing FITC is known for, it’s inspiration. In less than a decade since its first incarnation as a Toronto-based festival celebrating Flash, FITC has spread around the world and broadened its scope. Now, there’s something for everyone: writers, designers, developers, or creative explorers. It’s that spark of inspiration that unifies the speakers and attendees. I’d like to think it’s that same spark that inspired the entrepreneurs to create Flash (FutureSplash Animator, at the time), and possibly the same spark that inspired the first flock of flashy individuals to come together and create this event.

As if the speakers, networking and parties weren’t enough to bring people together, each year the event is centered on a theme. This year’s “Playground” theme was most evident in the speaker introductions. Each introduction was pre-recorded (and edited) by event creator, Shawn Pucknell’s young daughters. And while it would have been funny, I’m glad they didn’t do this introduction for the “Cool Shit Hour”. Alternatively, they could have just called it the “Cool Stuff Hour”. But that doesn’t seem to have the same impact.

The “Cool Shit” presenters included myself, Chris Allen (blog.ff9900.org), Didier Brun (@didierbyte), Joa Ebert (@joa), & Mikko Haapoja (@MikkoH). And in spite of some technical difficulties, great work was shown. Didier got the whole room singing “Hey Jude” with his great audio analysis prototypes, Joa live-coded a music visualizer with his notorious keyless keyboard. Mikko showed his devotion to creative development with a 3D painting app created using the Voxel Engine/Fancy Engine. And Chris demoed an awesome Star Wars Trench Run game for the iPhone. With each of the 5 presenters getting roughly 10 minutes each, I’m glad there wasn’t enough time for any Apple/iPhone remarks.

Reporting Back More from FITC 2010

View CommentsAdd a comment

By Neil Clemmons | Critical Mass Chicago

There’s a lot being written about the iPad – reviews, new applications, the ongoing debate on Flash, what the device does and what it doesn’t do.

Beyond the device, however, there are some implications and the longer-term impact it will have as we create digital experiences.  New devices and interfaces have a profound impact on consumer expectations, competitive moves, and the evolution of digital interfaces.  The Wii ushered in new interface concepts and ideas.  Same with xBox and xBox Live.  The iPad will do the same in its influence on the conventions and expectations of our industry.

We have several of the Wifi iPads in our offices and have had a number of discussions with our team about its implications.  Some see immediate opportunities for the iPad to ‘fit in’ to their lifestyles.  Others are still debating if it replaces something or is a supplemental access and consumption device.  It’s bigger than a phone with no ability to do more than SKYPE calls.  But it’s not quite a notebook with all the file access and productivity tools – so the iPad makes compromises in both directions.  The limitations will change in time as new applications, new peripherals, an updated OS, and improved connectivity come.

One thing the smartphone and iPad do is to force a focus on ‘what’s important’ versus ‘what’s possible.’  As sites or applications evolve, they become more bloated, more confusing, and lose the punch they can have.  Redesigns of a site or an application can be liberating, in removing the old conventions.  But invariably we worry about ‘moving the cheese’ of the habituated consumer and thus add rather than subtract in making experience design tradeoffs.  This is where Apple and the developers of iPad apps demonstrated tremendous courage in leaving behind the conventional interfaces and tools.  We need more courage to advance the customer experience.

What’s the take away after a week of using the iPad from an experience standpoint?

Here are the 7 Areas of Implications for digital marketers:


#1 – Fragmentation.

Josh Bernoff (Forrester) wrote about the Splinternet earlier this year.  That theme is in full force on the iPad.  Media and content fragmentation continue as new devices enable content consumption in new and different formats.  Information ubiquity that started with the smartphone is further exacerbated with a new form factor.  iPhone apps that are played on the iPad look OK, but you’re much more engaged by an iPad native app.   The need for liquid experiences that adapt to the screen become even more important as we look at alternative form factors.

#2 – Development Challenges.

We have to think differently about how content and experiences are created, disseminated and maintained.  Monolithic frameworks start to break down when there are hundreds of thousands of developers creating new experiences.  And with Apple changing their developer terms and conditions, it looks like Apple will expect you to use their tools and frameworks, rather than many of the cross-platform frameworks.  We have several clients working with Android, iPhone, Blackberry and other instances for applications.  The iPad and follow-on products from other vendors based on Windows 7, Chrome, or Android tablets will further exacerbate the challenge of consistency and maintainability.

#3 – Personalization.

We’re at the early stages of more personal (and relevant) consumption of media – that means the customer is even more in control of the experience.  Most will seek out an application rather than a web browser to consume their content where possible. Android, the iPhone OS, Windows Phone 7, Blackberry are all targeting what Mary Meeker with Morgan Stanley says will be a bigger market than the desktop PC market by 2014.  The browser lives on at the desktop, but many of these new devices will take a very different approach to content and experience access. Remixing content from feeds, apps, alerts, and personalized experiences will become even more important.  Add in the intersection of social to these experiences and you quickly see that use cases with these new devices will become even more personal.

Read on for 4 more Implications of the iPad

View CommentsAdd a comment