Here’s a little challenge for you. How would you design a responsive interface for a custom car configurator? The customer should be able to adjust colors, wheels, exterior details, interior details and perhaps accessories — on small and large screens. Doesn’t sound that difficult, does it? In fact, we have all seen such interfaces before. Essentially, they are just a combination of some navigation, iconography, buttons, accordions and a real-time 3D preview.
“Be agile; release early; release often.” We know the drill. But is it strategically wise to keep rolling out features often? Especially once a product you’re building reaches a certain size, you probably don’t want to risk the integrity of your application with every new minor release.
The worst thing that can happen to your product is that loyal users, customers who have been using that one little feature consistently over the years, suddenly aren’t able to use it in the same convenient way.
CodePen has become the playground for developers. The sandbox where you can build whatever your imagination fancies. Practical things, experimental concepts — it’s a treasure chest, bound to fuel your ideas.
For this Quick Tip, we have done some digging around and found some interesting UI demos and concepts for you to indulge in and build upon: dialog and modal windows, signup and login screens, navigation and menus, sliders and toggles. Small bits of delight that make the user’s interaction with a website or app more pleasant. Enjoy!
How do you write a useful app for the Apple Watch? In what ways does it differ from coding for iOS? And what if you don’t have a Watch on hand to test with? Before the launch of the Apple Watch, our iOS team at myMail (one of the popular alternative email apps for iOS) worked tirelessly with a simulator to create a new Apple Watch app.
We wanted the first buyers of the Apple Watch to have the opportunity to use myMail from day one. What we learned through using the simulator and creating the app — including the Apple Watch’s UI quirks, passing data between devices, and the rigors of simulator-only development — is described below and (we hope) will help iOS developers get to results, faster, and avoid a few headaches down the road.
An “affordance” is a perceived signal or clue that an object may be used to perform a particular action. A chair sits at around knee height and appears to provide support. It affords sitting. A toothbrush has a handle a little longer than the human palm. It affords gripping.
All of the objects that surround us have affordances: some are explicit (the “Push” sign above a door handle), and others are hidden (a chair could be used to break a window or used as a weapon).
A module tab is a User Interface (UI) design pattern where content is separated into different panes, and each pane is viewable one at a time. The user requests content to be displayed by clicking (or in some instances hovering over) the content’s corresponding tab control.
Module tabs are seeing an increase of use as websites and web applications push for optimizing web page screen areas without sacrificing the amount of information presented at once.
No, they shouldn’t. At first glance, the decision to open links in new windows or not depends on the given site and the preferences of its visitors. Visitors to the sites with heavy linking are more willing to have links opened in new windows then open dozens of links in new windows manually. Visitors of less-heavy-linkage-sites are more likely to open some particular link in new window to remain on the site and continue to browse through it afterward.