I know i know. Unsolicited redesign concepts have been reason for many discussions. Some like them, some hate them and Dribbble is full of them. I for my part think it can be a fun exercise to do and also a good source of inspiration for others.
Redsgned is a website showcasing the very best redesigns they find across the web, from web designs, branding, app designs, UI/GUI and product design.
Here’s something funny for the weekend: UX Reaction GIFs!
Imran Parvez wrote an interesting article on Medium about how to design a settings page. He covers some of the common mistakes and then some possible solutions with many references to the official design guidelines from Android and iOS.
Difficult product decisions should never become a setting. For example: If there’s a debate in your team which is building an email client, whether to show four lines of summary or two lines of summary for each email. Do not make it a setting!
Worth a read if you intend to design a settings page for your product.
Some very interesting insights on the design process for an ongoing CodePen redesign by Sparkbox. I love how open they share pretty much everything from User Interviews to Sketches to Wireframe Prototypes.
A collection of design insights about perceived speed.
Your website should be so simple, a drunk person could use it.
You can’t test that. I’ll do it for you.
WHAT: I’ll get very drunk, and then review your website. I’ll send you a document outlining where I thought the website needed help, and a screencast of me going over the website.
HOW MUCH: $150 per site.
There are some ideas in this world where you cannot tell if ridiculously stupid or simply genius. This is one of those.
"Design is how you treat your customers." – Yves Behar
— Christopher Stark (@digimgmt) March 21, 2015
On this weeks Keynote Apple revealed some more infos about the Apple Watch. The one thing that interested me most as a web designer (and would have made a very good reason to justify buying one) is if there will be some form of a real web browser. Unfortunately there’s not a whole lot of information about that and i cannot remember Apple saying a single word about it.
Peter Paul Koch mentioned in this article back in September 2014 that there will be Apps with WebViews, but nothing like a full featured browser, which still seems to hold true. He speculated that the reasons behind this are mostly hardware and user experience.
It’s possible that the current Watch hardware isn’t yet powerful enough to run a full browser, and that Apple will make sure that any app using the WebView doesn’t do anything heavy such as running JavaScript or animations. Even if that’s the case right now, the problem will go away as hardware matures, and I don’t think it’s the fundamental reason why the Watch doesn’t have a browser.
Instead, consider the user experience. How do you enter a URL on your Watch? How do you fill out a form? You don’t, as far as I can see — there may not even be enough space on the display for a Back button.
I quite agree with him, the technology/hardware side will mature fast and won’t be the problem here. But to be able to solve the UX of web browsing on smart watches will take some time, because we just don’t know yet how people will react to new ways of interaction. Will “Force Touch” enable useful new ways of interacting with a website? Will speech and motion recognition play a bigger role in tomorrows web design? We don’t know yet, but it’s completely imaginable that somewhere in the future we won’t even need to manually enter URL’s or filling out forms anymore.
It’s a situation we all know too good: You have that beautiful design turned up into a living prototype, media queries take care of all those different viewports and everything works just perfectly together. And then the client realizes that he needs two more items in the main navigation and suddenly your nice navigation starts to break apart and you start tweaking everything again and again. At least thats how i did it before. Not very flexible.
Heydon Pickering just wrote a great article on A List Apart about Quantity Queries for CSS which will make all of the above a thing of the past.
The
@mediaquery is the darling of responsive web design because it allows us to insert “breakpoints” wherever one layout strategy ceases to be viable and another should succeed it. However, it’s not just viewport dimensions, but the quantity of content that can put pressure on space.Just as your end users are liable to operate devices with a multitude of different screen sizes, your content editors are liable to add and remove content. That’s what content management systems are for. This makes Photoshop mockups of web pages doubly obsolete: they are snapshots of just one viewport, with content in just one state.
With a clever combination of of nth-child() and first-child() pseudo-selectors he achieves to count elements in CSS. This makes it possible to apply different styling to navigation elements, when there are equal to or more than what you specify. If you haven’t read this article yet, you seriously should do that right now!
Last week this jQuery Plugin popped up a lot on different channels. First: Yes, it looks pretty! But quick and easy? Not really.
I could imagine something like this could work for simple select fields, where you have just a handful of options to choose from. Maybe for the order quantity in a checkout process or something like that. But for a date-picker it doesn’t cut it.