Date post: | 12-Jan-2015 |
Category: |
Technology |
Upload: | webcat |
View: | 340 times |
Download: | 0 times |
The Browser is not a Document Readerwith @RachelNabors of RachelNabors.com
The Era of Flash
Smell the load screen.
Everyone wanted to be a Dunkleosteus, erm, Flash Developer.
iOS says no to Flash
Rise of the Front End Dev
The environment was irreversibly changed.
● HTML5, CSS3, and JavaScript were able to rise to the occasion.
● Many designers, developers and generalists began crossing into each others' territories.
New Niches
An evolving role
● Clients have gotten used to hearing, “You can't do that on an iPhone!”
● Designers and developers have let themselves be limited by Internet Explorer
Increasingly static
Equal & Opposite ReactionsFrom:● Interactive● Show-offy● Over-the-top● Unorthodox design
To:● Content-first● Reserved● User-focused● Magazine-like
from the anime Serial Experiments Lain
“My prediction is that, unless the leadership vacuum is filled, the Web is going to retreat back to its origins as a network of hyperlinked documents. The Web will be just another app that you use...”
—Joe Hewitt, Web Technologies Need an Owner, 2011
We have the power● HTML5 Audio, Video● SVG● Canvas● CSS3 Animation and Transitions● Web Audio API● Web GL
We can do thisApply what we've learned from the worst offences of Flash:
● User Experience● Accessibility● Performance and size
Interaction != “Flashy”Not every interaction is going to look like this: http://codepen.io/rachelnabors/full/lqswg
We can do interactions right, for all experiences:http://www.apple.com/mac-pro/
Return of the Interaction Developer
What we can do● Define yourself by the things you make, not
the tools you use
● Evolve with the environment
● Cross pollinate, reach out to people outside your circls
And above all else remember:
What we build today determines what browsers and networks support tomorrow.
Thank you! @RachelNabors of RachelNabors.com