Storytelling takes many forms. In the past, stories were told orally, with people telling and retelling myths, fables and even histories. As writing technology became more prevalent, we began to record our stories, and we told them in the pages of books.
Now, our society is awash in different devices and technologies, and those traditions of spoken stories and printed stories are blurring. Multi-screen narratives are being told across all kinds of platforms, pages and devices, making for truly immersive experiences. We are watching them, tapping them and learning from them.
<picture> element supports a number of different types of fallback content, but the current implementation of these fallbacks is problematic. In this article, we’ll explore how the fallbacks work, how they fail and what can be done about it.
WordPress is built by volunteers. People from all over the world collaborate to create the core software, to write the documentation, to provide support, to translate WordPress, to organise events, and to generally keep the project running. Individuals work on WordPress in their free time and companies ask their employees to get involved.
A bunch of WordPress contributors.
Part of WordPress's success is that it is not simply a development community. There are designers, user experience experts, support volunteers, writers, users, accessibility experts, and enthusiasts. This diverse input strengthens the project. It also means that there is space for you to get involved. Whatever your skill set, there is room for you in the WordPress community.
Android is huge: 480 million people currently use Android devices, and 1 million new devices are activated daily. This means that every three weeks, the number of people who activate new Android devices is equal to the entire population of Australia. (Recent studies by Nielsen show that more Android devices are on the market than iOS devices.)
Popular apps that become available on Android experience huge growth. For example, Instagram grew by 10 million users with the launch of its Android app — in just 10 days.
Nearly half a year ago, we introduced our eBook subscription model, also known as the Smashing Library. We knew we were onto something good, realizing that the Smashing Library was the next step in offering quality content — at a price you’ll still be able to afford all of the coffee you need to stay up long enough to read the entire library and, of course, the free eBooks.
To give you a taste of what to expect from the eBooks in the Smashing Library, we are happy to present you with The Smashing Editor’s Choice: A Smashing Library Treat — a free eBook that contains a wide range of topics, including new coding techniques, user experience strategies and more.
This article is about design consultancy. It’s about wrangling that client who uses empty sentences like, “We want a snappy, simple experience,” or, “It should be on brand and should really pop.”
It’s about commanding the room and setting a vision before moving on to wireframes and pixels. While I’ll talk in terms of consultation, these ideas can be applied to the design phase of any new project.
Responsive design is about more than just layout; it’s about designing for the Web, which means, mostly, for people with browsers. And that’s just about everything we know about the people who visit our websites: they are probably using a browser. All the rest we just don’t know.
Up until not so long ago, we used to base our designs on some rather general assumptions about screen size and input type. With the rise of devices with various screen sizes and alternative ways to interact, these assumptions have turned out to be unreliable. We need to upgrade the defaults that we use when we start designing our websites.
Welcome to another interview in the series called “How I Work.” These interviews revolve around how leading thinkers and creators in the Web world design, code and create.
The goal is not to get into the specific nuances of their craft (as that information already exists online), but rather step back and learn a bit about their habits, philosophies and workflow for producing great work.
Infinite scroll promised to provide users with a better experience. However, the good is often accompanied by the bad and the ugly. Once we understand the strengths and weaknesses of infinite scrolling, we can begin to use it to empower our interfaces.
Human nature's framed perception demands an hierarchic interface; an interface that would make it easy for users to find their way around. Infinite scroll, sometimes leaves users feeling disoriented as they travel down the page that never ends.