Mr Branding

Tuesday, June 16, 2015

Build a Media Player with HTML

The possibilities for media in HTML have taken off with the introduction of the video and audio elements in HTML5. Now we can embed video and audio in websites without the need for proprietary technologies like Flash or Silverlight.

With browser support better than ever, and new technologies like WebVTT starting to arrive, now is a great time to get to know (or to revisit) these new HTML elements.

Learnable has just launched Getting Started with HTML Media, a course that gets you up to speed with HTML's new media elements and how to take them to the next level with CSS and JavaScript.

Here's a video from the course that gets the ball rolling, showing you how to structure the HTML code for a custom media player. (Later videos demonstrate how to build on this with CSS and JavaScript to create a fully functioning, custom media player.)

Loading the player...

You can download the source files for this demo on GitHub.

If you found this useful, check out the full course at Learnable—which takes you from the basics right up to developing a fully functioning, custom media player, playing both audio and video.

Continue reading %Build a Media Player with HTML%

by Guilherme Muller via SitePoint

Bringing Sanity and Order to Device Testing

This article is part of a web dev series from Microsoft. Thank you for supporting the partners who make SitePoint possible.

It seems like every other day the public is granted some new means of accessing the web. Some days it’s a new browser. Others it’s a new smartphone. Or a tablet. Or an e-reader. Or a video game console. Or a smartwatch. Or a TV. Or a heads-up display. Or a car. Or a refrigerator.

I worked on one project where the client provided me with a spreadsheet detailing 1,400 different user agents that accessed the login screen for the m-dot site. In two days!

As further evidence, consider the enlightening details of this post from Jason Samuels of the National Council on Family relations, a non-profit organization:

In 2008, visits from “mobile” devices accounted for only about 0.1% of their traffic. In 2014, that number had skyrocketed to 14.4%.
In 2008, they detected 71 different screen resolutions, which is already a lot to consider. By 2014, however, they were seeing 1,000 unique screen resolutions each and every quarter (with over 200 of those recording 10+ visits per quarter).

That last stat blows my mind every time I read it. You can’t design for 200 different screens, let alone 1,000. It’s a fool’s errand. And don’t even think of trying to test on that many devices.

And yet, here we are designing websites that can (and will) go anywhere. We need to thoroughly test because we can’t make any assumptions about the browsers and devices being used to access our content.

Testing can be tedious, time consuming, and costly. Surely there’s a way to make it easier. There sure is: Instead of getting hung up on creating one experience that needs to be nearly identical on every browser, we can be smarter about how we build things and treat experience as a continuum.

We can build websites that are both nimble enough to work on low powered devices over slow networks and smart enough to take advantage of advanced features and sensors when opportunity knocks.

Wha?! We can have our cake and eat it too? Yes. Yes we can.

Continue reading %Bringing Sanity and Order to Device Testing%

by Aaron Gustafson via SitePoint

Mr Branding

Tuesday, June 16, 2015

Build a Media Player with HTML

Bringing Sanity and Order to Device Testing

How 3 Modern Tools are Using Flexbox Grids

Petar Stojakovic

America Cup 2015 Chile

Cuneyt Sen Freelance Designer

Trebbe – 1000e basiswoning