Coding Our Tomorrows – And Building the Future of the Web – The Future, Yesterday

View Github Repository Open presentation in a new window

svenaas

See all presentation from svenaas

Coding Our Tomorrows – And Building the Future of the Web – The Future, Yesterday

0 0

cot

Coding Our Tomorrows

On Github svenaas / cot

Coding Our Tomorrows

And Building the Future of the Web

Sven Aas / @svenaas #csfuture

Speaker introduction. Hashtag. Hope to have a few minutes for questions but you can also ask them online.

The Future, Yesterday

I'd like to start by talking about the future of the past.
Your browser does not support the audio element. Sputnik Beep via NASA's awesome Soundcloud Channel
The Usborne Book of the Future (1979), Future Cities (1979)
The Usborne Book of the Future (1979) "The electronic household" 1. Giant-size TV 2. Video movie camera 3. Flat screen TV - used for shopping 4. Recordable video disc player 5. Domestic drink robot 6. Electronic mail slot (via remote photocopying)
The Usborne Book of the Future (1979) It's a watch. It's a phone. It's an emergency beacon. Note the pop-out antennas.
The Usborne Book of the Future (1979) Note the camera drone.
Your browser does not support the audio element.
Image: Crazywatches / Audio: oldpulsars.com The Hamilton Pulsar P1, released 1972, cost over $2,000.
"Wall Street" (1987) The Motorola DynaTac 8000X, released 1983 for $3,995.

The Future, Today

Raspbery Pi WikiMedia Commons image by Lucasbosch This is the higher-end B+ model, which costs $35.
Indiegogo Campaign Photo Misfit Shine has accelerometers, Bluetooth, and a battery that lasts for months.
Apple Watch Gallery Photo
Photo via Stanford Stanford/Berkeley project. No batteries — runs on energy from ambient radio waves. No external antennas. 50cm range. Will cost "a few cents" to make. We can put these things EVERYWHERE.

The Internet of Things

Flickr photo by thrp Embedded computing devices on the internet with unique addresses. These are the contents of a student's bag. Proximity tags in the books to connect devices to supporting resources? How might embedded devces be useful in these objects? Position sensors in the gloves? Accelerometers in the pencil to digitize notes? Medical monitors in the personal care products? Display devices in the glasses?

What's the fundamental unit of the Web?

The website? What is a website made of? The webpage?

The internet isn't made of pages.

That's yesterday talking.

How do we experience the web?

WikiMedia Commons image by JohnnyMrNinja The computer?
Un iPhone para tu gato from iPhone Diario The phone?
Via Soulful Abode The tablet?
WikiMedia Commons image by cloudzilla The TV?
Flickr photo by Steve Jurvetson The Car?
Flickr photo by Anthony Hicks The Fridge?
Via International Business Times The watch!
Noha نهى by Hossam el-Hamalawy Designers and programs CREATE (and experience) websites on computers. It's easy to get caught in the trap of assuming that this is how users experience them. With every day that goes by this gets farther from the truth.

The Future, Tomorrow

People don't view your content on your website.

But that's not the only trap you've got to avoid. There's also this. Let me say that again.

People. Don't.="color:>View. Your content. On your website.

Why not?

I'll give you three reasons.

Syndication

RSS Throwboy by Jack Amick First: Syndication. This used to mostly mean RSS. Today it also means giving your content a life outside your website.

Sharing

Min Ming Lo's Share: The Icon No One Agrees On via Gizmodo Reason Two: Sharing. OK. *Maybe* we go right to a website. But what do we do when we find an interesting article? We share it. And where do our friends discover it? Not on the website. (Note the inconsistent icons — these are from Min Ming Lo's article about sharing icons)

Use Case Fluidity

Photo via Mobify Reason Three: Use Case Fluidity. Consider: Device variety. Users might user anything to interact. Consider: Device fluidity. Users aren't constrained to a single device even during a single ineraction. See: Apple's Handoff continuity between devices.

Cards

Why Cards Are the Future of the Web by Paul Adams Twitter and Google's Cards. iOS and OS X Notifications. Apple Watch Glances.

Don't try to control how people access your content. Just make sure it's possible.

Web Standards

Flickr photo by Jeffery Zeldman Compatibility.

Accessibility

Flickr photo by League of Michigan Bicyclists

Semantics

  • Microformats
  • ARIA
Flickr photo by Jacob Davies

But it's not just your content

Users expect to get their data in and out of your site.

Flickr photo by julochka

Interchange formats

  • XML
  • JSON
  • YAML
Flickr photo by Greg Williams

And it's not just content and data portability

Your services have lives outside of your site.

Think: mapping (directions, geolocation). That's for ad driven sites. What about sales driven sites? Think: product reviews (and purchase!)

Interoperability

Flickr photo by Arturo Vidich

APIs

Flickr photo by Eric Lumsden

Web Services

Flickr photo by Ralph S

Web Resources

Flickr photo by Joachim S. Müller

Objects

Flickr photo by Jay Reed Representational State Transfer (REST)

Integration

Flickr photo by eldeeem Integration between services and APIs

Tomorrow

You're building things, and users are out there. They could access the things you're building in ways you haven't considered — in ways you can't imagine. They're using things OTHER people have built that you haven't even heard of. But these things can work with what you're building to make it even more valuable.

Be Ready for Tomorrow

  • Free your content
  • Free your users' data
  • Be inclusive
  • Take advantage of standards
  • Design for interoperability
  • Avoid unnecessary constraints
Thirty years later I'm just as fascinated about the future. And I love that here at CrowdSource Summit I can look out into the room and I can see it.

Thank You

And See You Tomorrow

Questions?