This article is currently only available in German language
This article is currently only available in German language
Microsoft’s Modern UI design language has arrived in many applications with varying success. By now, almost everybody has seen Modern UI (formerly known as Metro), and Microsoft seems committed. Developers of Windows software have to think about the fact that a lot of established interfaces look out of place in a Modern UI environment. It needs to be adapted to the current state of interface design, even more with Apple similarly moving iOS 7 to a flat UI style. Working on such updates, we have collected a set of 10 design principles we call, for the sake of simplicity, “Desktop Modern UI”, and we want to share them with you.
“Form Follows Function (FFF)” – You can think for hours about these three words and for their explanation quite some words are necessary, for it is a frequently misunderstood design principle.
Have you ever thought about switching from Windows Forms (WinForms) to WPF seriously? Try something new and stop to develop along the old well known patterns? To be honest until a few months ago, I haven’t had any thoughts about making a transition. I was very familiar with Windows Forms and WPF would have been something I would have to learn from scratch. So it was only a test project and my applications remained Windows Forms applications. So, when I joined Centigrade earlier this year, after working as a developer for nearly 15 years in the financial industry, Centigrade made the transition to WPF long ago. Just take a look at related blog articles on our website! My colleagues in the field of design engineering are working for several years with WPF. Especially younger designers and design engineers only knew Windows Forms from their study – if at all. They never worked with it in practice. Many companies already use WPF, but despite the fact that already the fourth version of the technology is out lot of them are still in the evaluation phase. From my own experience, I can only report – it can even be worse. Especially, in the financial sector applications with a rather boring look and feel are created until today. Yet, things could be so much more appealing…
So a new chapter started in my programming career. With a healthy dose of skepticism, I joined my first WPF Project. I was hooked immediately. I have collected some of my experiences and summarized them within this article.
In April I blogged about metro style pictograms being the new sliced bread in icon design. Remember? The article was, of course, highly interesting, incredibly important and not to mention terribly knowledgeable – and naturally it was in no respect longwinded. Well. Let’s just say it was rather formal and academic. Today, dear reader, I am going to be emotional. And pretty much so. Why? Because bad user interface design can drive you up the wall.
Texts are important parts of most user interfaces, be it, e.g., as form field labels or longer help texts. This article is aimed at providing a common introduction to the topic „choosing the right font”. It contains some hints an pointers that simplify the search for the right typeface.
The first part of this article provided an overview of the concepts of the currently implemented user interfaces for the Kinect™ sensor. It pointed out technical specifications and explained the human-machine interaction within Kinect games. This second part now scrutinizes this interaction and assesses its potential for industrial application.
In November 2010, Microsoft® introduced Kinect™. As an expansion of the Xbox 360™ gaming console, it brings controller-free gaming to the living room and even long before its actual release it was believed to revolutionize Human Computer Interaction. Therefore, expectations were rather high and one felt reminded of the Natural User Interface (NUI) featured in the movie Minority Report. Will this futuristic vision soon become reality?
Comparing computer games with “serious” software applications may seem like comparing apples and oranges if we think of serious software as tools that allow users to achieve mission-critical productivity goals in their working live. In this respect, the two industries couldn‘t be further apart regarding their target audience and the way they rank productivity vs. fun. For this reason, we are oftentimes asked why Centigrade as a “serious” user interface design company collaborates so closely with the game industry and even has a branch office located in a building that’s otherwise occupied solely by game development studios.
Yet, the link between computer games and industrial software is more obvious than one may think. To summarize why we believe computer games can have a positive impact on the user experience (UX) of industrial software applications, this three-part blog post provides a bulleted list of ten arguments we keep on stating in this regard. The first part gives a high-level and process-oriented perspective on the topic, the second part will shed more light on the transfer of aesthetic and interactive aspects found in games to serious software and the third part will have a look at the game industry as a technical driver for innovations that spill over to other software industries.
In recent years, so called “natural user interfaces” (NUI) have grown in popularity. More and more often, interaction via touch and gestures is employed instead of using mouse and keyboard. The iPhone was greeted with great enthusiasm and played a major part in spreading touch screen system in the consumer market while also introduced gesture-based interaction in a playful way. There should be hardly any touch screen user who is not familiar with the pinch gesture that is used to resize or zoom images on the iPhone.
Keeping the background information of the previous article in mind, assume you want to make use of Blend to design a NUI based on Silverlight or WPF that lets you easily manipulate items on the screen. In the beginning, you won’t even touch the tool at all – you “invent” whatever gesture you think is intuitive to perform this operation. Most likely you do this in your head or on the whiteboard. You discuss and refine the design with your team mates or with potential users. At this stage everything is still low-fidelity and throwing away things isn’t costly yet. As soon as you have a good-enough feeling about the rough design, you start prototyping with higher fidelity. This is to be really sure your idea works. To provoke the intended interaction experience, caring about every single detail is exceptionally important in later prototyping stages.
In the first part of this series I described how user interface design tools bring together developers and designers in a seamless workflow and gave an overview of the technical environments of Adobe’s and Microsoft’s tools in that area.
In this article, I am going to focus on the use of pixel and vector graphics in design, deal with some of the pros and cons of the two graphic types and finally give an introduction on the scaling of bitmap GUI components.
This series of blog articles deals with the use of GUI development tools by designers and developers, with a particular focus on Microsoft Expression Blend and Adobe Flex Builder.
In the first part, I will have a look at the cooperation between designers and developers during GUI creation, describe some issues that can affect their collaboration and point out how GUI design tools can improve the overall design and development workflow.
These days, clients often mention the iPhone when describing their thoughts and goals concerning usability and user interface design, e.g. during project kickoffs.
On the one hand it’s nice to see user interface design and usability getting a good rap through the iPhone and more people realizing that the user interface is more than just the topping on the cake, but still, whenever those “Make it like the iPhone” statements are uttered, there are some things to discuss to set expectations appropriately.
First, it should be clarified that such a statement can be interpreted in two different ways. For one, it can mean “Make the user interface as easy to use and aesthetical as the iPhone’s”, which usually is the intended meaning. But it can also be interpreted as “Conduct the user interface design project in a way similar to the iPhone creation”, which is usually not the intended meaning, even though those two aspects are intimately intertwined.
Let’s have a look at both aspects.
|Subscribe to "Articles" blog|