A Java™ developer who is used to developing GUIs with Swing and who is now trying to get into Android might be surprised: Java is not the same on Android.

The fact that Java is different on Android has been discussed in some blogs on the net already, so I just sum it up to this: Android applications can be written by any developer who knows the Java programming language. But the number of available runtime classes on Android is different: there are fewer classes in Android regarding package java.* compared to Sun Java Standard or Micro Edition. The most surprising fact for a Java GUI developer might be that there is no Swing on Android.

This article demonstrates some aspects of how a simple Java Swing application with a nice Look and Feel was transferred to Android. The main focus is set on how to write the application with the Android SDK and the styling and theming abilities of Android.

More and more operating systems use a border resembling frosted glass for their windows, like, e.g., the Aero Glass® decoration known from Windows Vista® and Windows 7®. Providing this ‘special effect’ on the Java™ platform is still not easy to realize. Most Look and Feels use opaque borders, which do not visually match the surrounding designs of these operating systems.
This article describes a pragmatic approach to solve to this problem.

As described in January’s post, animations can fulfill essential purposes in user interface design. This article provides some insight into a study that has been conducted with the goal of exploring the effects of animations regarding user experience.

There are a lot of free icon libraries out there, however, only few of them focus mainly on medical icons and we wanted this gap to be closed: we introduce Centigrade’s stock icon library MedicalSeries, containing 60 icons that you can download free of charge.

A prototypical sequence in user interface design proceeds from wireframes to interaction design and finally to visual design. The user interface is successively refined, starting with abstract statics, then specifying the basic dynamic aspects until finally visual specifics are added. This is compatible with the view that visual aspects of a user interface are more or less the icing on the cake – details that should only be taken care of after the foundations for a user-friendly have been laid. But this view may be flawed.

Red is not always red, green is not always green. For quite a large amount of people it is not easy to distinguish between red and green hues. About 6% of all males have the same difficulties to tell orange from olive-green as unaffected people have to distinguish between burgundy and ruby-red – oftentimes, it is impossible. This most common kind of color vision deficiency is called Deuteranomaly, also known as “green weakness”. The following article will deal with the question of how this wide-spread impairment impacts the production process of high quality icons.

After dealing with general market trends in part 1 of this blog series this second and final part provides a more detailed comparison of Google Android and JavaFX.

User interface prototyping is an essential activity in the field of user interface design that provides a basis for continuous evaluation and improvement of a to-be-designed user interface. In usability engineering, the focus of using prototypes lies on evaluating the usability of intended approaches and on generating concrete recommendations for advancing an interface design. While doing so, there are several aspects to keep in mind in order to maximize the efficiency of prototype use for usability engineering. Three issues are described in this post.

Centigrade specializes in creating GUIs, in many projects with a particular focus on the implementation of Java Swing based GUIs for desktop applications. With the advancement of the mobile market, it is an obvious step for Centigrade to also have a look at Java based mobile GUIs. This article gives an overview on the mobile market today and includes a comparison of the two major Java players in that sector, Google Android and JavaFX.

In the previous part I took a closer look at how and to what extent Microsoft Expression Blend and Adobe Flex Builder offer pixel-graphics and vector-graphics tools to enable GUI designers to create modern user interfaces. In addition I outlined the concept of 9-Slice-Scaling, a method to make pixel graphics scalable without any quality loss. In this last part of the series I’m going to give a short example of how the concept is implemented in both tools and finally provide an overall comparison of the two tools to point out their strengths and weaknesses.

The previous part of this series outlined why it is not possible to just create one single vector-based instance of an icon to scale it to any desired size. This part raises the question, on the one hand, what tool support would need to exist in the future in order to serve an icon designer’s everyday work adequately and, on the other hand, what tool support already exists to make his life at least a bit easier in the present times.

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.

The previous part explained why both a pure pixel-based or pure vector-based approach to icon design implies drawbacks. As Centigrade provides professional icon design services, we continuously investigate how to make our icon design process more efficient and overcome technical shortcomings.

Wireframes are an essential tool in the usability engineer’s toolbox. They can be created easily and support communication regarding fundamental layout and interaction design. Usually, little to no resources are spent on visually “styling” the wireframe in order to efficiently focus on the fundamentals without investing too much effort in visual details that are likely to undergo significant visual changes later.

If members of the design team / stakeholders lack experience with using wireframes, certain problems can occur that may impair a user interface design project, two of which shall briefly be described.

It is still a common complaint uttered by usability professionals that organizations in general and software developers in particular “just don’t get” usability engineering. They are frustrated because they have all good intentions to provide support for creating user-friendly systems but the reactions they get are reserved at best and developers simply don’t buy into the whole usability engineering process.

So, whose fault is it? Who is it that is just not getting it?

As often in life, it takes two and an occasion to create a problem. Let’s have a closer look.

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.

“Who needs usability engineering, anyway?” – This is a question that one might hear from people whose experiences with usability engineering services have not been too good.

In the previous part I gave a quick introduction to resolution independence. This part explains what technical limitations exist that complicate the job of creating high quality resolution independent icons.

About two years ago there have been some lively discussions on resolution independent user interfaces in the context of icon design. An interesting start page for past discussions is Sven Porst’s blog article. At that time, resolution-independent UI-related products such as Mac OS X Leopard, Windows Vista or Silverlight were either yet to come or have been used solely by a small bunch of insiders. Now, almost two years later, these are established brands – reason enough to shed some light on this topic again and to see if something has changed during this time, and if so what.