How to innovate without having to do it at all

A few days ago Apple introduced the long-awaited graphical revamp of its mobile operating system and I can't find more words than "ugly" to briefly describe it. Now, outside of the field of the first reaction, we do not have much more than disappointment to rescue: iOS 7 is basically the same system as always, but with a more garish color palette, transparencies that border on the ridiculous and not very encouraging news.

Although Apple is not a theme for this space, this event can serve as an example of poor design decisions on a somewhat more general topic: user interfaces and how to update them appropriately. Let's dismiss the Apple issue for a moment, but not before thanking this company for having eliminated all residue of desire for one of their devices from our minds.

Plain design

"Less is more". This phrase, perhaps repeated as a mantra by some lonely designer in another corner of the world; it is the basic principle that sustains the current trend for a simpler design and better adapted to the actual use that is given to the applications. However, this seemingly simple concept has degenerated into an effort to turn everything into a flat and simple reflection of already obsolete conceptions.

I explain. While designing physical objects is a process entirely tied to reality and its limitations, designing a computer application has its limit directly on the idea on which it was conceived. And there is always room for improvement, however magnificent it may be.

Let's think of a quick example: Google. Standardizing the appearance of your services is a great step towards consistency that directly benefits the user by avoiding the need to relearn concepts that are repeated throughout your platform. That's why the new Google+ experience is so frustrating: reinventing the wheel is useless.

There is no consistency. There is no concentration. The rules of the game changed too fast. And all this accompanied by ridiculous details such as the "happy bell" in the notifications or the unnecessary scrolling of the top bar.

La Linus Torvalds fury It is justified, but it has the wrong reasons. The problem is not the typography, it is the idea that Google proposes. The horror.

Holding on to preconceptions is not good and unfortunately, it will be something that we will see repeatedly during this flat and simplistic fad that continues to change absolutely nothing in the way we use our applications.

Simple design

In how many clicks can you write an email? An ideal route could take us from opening the program, pressing the "New" button and after typing it and verifying the details of the recipients and attachments; until giving a final click on «Send». Three theoretical clicks that sound like a reasonable thing even if in practice it is not.

Let's think about how many tasks could be brought to even similar efficiency and how the programs in charge of performing these tasks would look like; without even thinking of a "flat" shape for them. There is always a better way to do things, even if it is very difficult to find. A wonderful example is the 10 × 10 technique, which can be summed up as drawing the idea in question ten times, different each time, and then ten times more for the winning idea. A tiring process, but with an invaluable harvest.

One more example: how can we improve a relatively passive action, like listening to music? KDE has in my opinion one of the best audio players out there, but it has room for improvement, as we have seen that it has everything. A particularly widespread problem is repeated information. Let's take a look at the following screenshot:

Amarok playing.

The track name is repeated five times in the default layout. In the window title, above the progress bar, in the playlist and in the «Context» and «Lyrics» applets (the latter is not shown because Amarok did not find the lyrics of the song), not counting the notification that appears when the track begins. I want to think that just one time is enough, but this is unreal.

Following the new trend of removing the title from the window - which extends both to free desktops, such as Pantheon from elementary OS or GNOME, as well as proprietary ones, such as Mac OS X - at least one repetition of the track name could be removed.

The slim toolbar - which I use - takes another from us, and finally, a change to the applets would remove even one more.

These types of details are easy to correct and do not present serious conflicts to use a program. But there are examples galore of more serious problems, especially in the field of mobile applications.

Innovate without innovating

KDE has a great opportunity to improve exponentially in a hypothetical graphical update. A major graphical revamp would face the challenge of keeping the typical KDE customization in a new paradigm; but I really have confidence in the people behind this project.

Oxygen needs a facelift, but it's not really serious and to take it lightly would be wasting opportunities like Apple has done. The idea is not to turn KDE into a white canvas with colorful fonts, but to create a new and visually pleasing experience for us, its users.

We can ask for simple things. A more sober color palette in the icons to remove the stigma of the glass that they have been dragging for a long time. Simplify widgets of Oxygen without actually making it look so plastic as GNOME.

All of this involves enormous work. But I must insist that all those changes that would make us enormously happy do not really solve anything. We have to rethink the way we use our applications today and build something wonderful new from what we find.

I say KDE because I have gained enormous confidence in the project. I've gotten used to KDE and I don't see other environments with the same eyes anymore. I wish I could contribute more than just these words of encouragement to the designers, artists, and programmers who build this on a daily basis, and I say this because I believe they know what they are doing and where they are going.

There is no need to reinvent the wheel. You don't have to paint it white and blue and say it's new. You have to take that well-made wheel that is already KDE and turn it into a jet engine. And I am confident that this will sooner or later materialize on the screen in front of me.

The music presented in the screenshot can be obtained legally and free of charge at the following links:


Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   msx said

    Clearly this is a totally subjective and personal view full of misconceptions and wrong conclusions - totally discarded by the rest of humanity.
    Or at least for me.

    1.    anti said

      The article or iOS 7? I don't get.

    2.    DanielC said

      Yes, graphic design issues are being mixed with software.

      1.    anti said

        That was the idea. I mean, I meant that design is important in applications and in the way they are used, to find better solutions. That was the joke.

    3.    rainbow_fly said

      How bad you put things ahahaha

  2.   pandev92 said

    The only complaint I have about iOS is that now it looks like an android / windows phone more ..., it was much better before, but hey, I guess people will get used to it ...

    Regarding the subtraction, I love the new design of google +, the font rendering, because I don't know, because I force the same fonts on all the webs ...

    About kde, I would seek to create a new concept 🙂

    1.    cat said

      just as i read on another page: Android + WP8 = iOS7 xD

      1.    eliotime3000 said

        I saw the video of the iOS and the only redeemable thing that it has is that it finally enabled bluetooth to transfer files. The rest, rather reminded me of Android 4 (it is practically iDroid).

  3.   eliotime3000 said

    Apple is practically the Microsoft apprentice. The only thing he made really his own was the Apple II, it was the total authorship of Steve Wozniak.

  4.   Camilo Tellez said

    With this we can conclude that free software has a long way to go to improve its interfaces, usability and user-friendliness.
    That is what makes commercial software so attractive, because the first objective is the user experience.
    While free software is created in an informal and messy way, by volunteer programmers in their free time, proprietary software is much more formal, planned, they hire specialists in each area (programming, design, quality assurance, testing, etc.)

    1.    likewho said

      Are KDE and Blender (to name a few) done in a messy and informal way?

    2.    Andrélo said

      Is that when they make a simple interface, they throw shit at it…. Gnome Shell example

      1.    dwarf said

        Shell does not have a simple interface, it has a layer interface that is different. The problem is not that they minimize and clean, the problem is that they cut functionalities that do not look pretty because in their opinion "they are not necessary" ... quick example: the Nautilus split view. That, among many others.

    3.    dwarf said

      While free software is created in an informal and messy way, by volunteer programmers in their free time, proprietary software is much more formal, planned, they hire specialists in each area (programming, design, quality assurance, testing, etc.)

      You got blown away with such an irresponsible and typical noob comment. Forgive me, but you screwed up with what you said.

      Look, first of all you are saying that SL development is a hobby rather than a serious task and, please, refrain.

      Examples of what can be good interfaces are scattered everywhere and although KDE needs to improve on that (they are working on it for plasma workspaces 5) it is not even remotely an informal and little planned project, it has funding even from European government entities.

      I will not say more, it is not worth it.

    4.    x11tete11x said

      how good the commercial software, so attractive and programmed so neatly ... http://www.kuro5hin.org/story/2004/2/15/71552/7795

  5.   Tammuz said

    I thought he was going to talk about IOS7 but in the end he rambled on about gnome and KDE

    1.    dwarf said

      Why should I actually talk about IOS7 as such in a Linux blog (?) I say ...

  6.   Carlos said

    I agree with your analysis and it surprises me how several failed to capture them.
    Nowadays the user interface, the graphic section and the user experience of the application is as or more important than the functionalities of the application itself. And yes, this is something that developers have a hard time seeing ... this article may interest you:
    http://www.codinghorror.com/blog/2005/08/the-user-interface-is-the-application.html
    http://www.codinghorror.com/blog/2006/11/this-is-what-happens-when-you-let-developers-create-ui.html

    And KDE has a double challenge. The rest of the desktops have strongly changed the paradigm betting on a 'better' way of using the desktop, perhaps, simpler and more productive. I'm not sure that KDE should turn from its current north, we have an elegant, powerful, functional and fully configurable desktop. How to improve it? Complicated, but I also think KDE people know what they're doing.

    Greetings, very good entry!

    1.    dhunter said

      A few days ago I read that KDE is rewriting the HIGs on the usability mailing lists.

      1.    elav said

        So is..

  7.   dwarf said

    I do endorse Gerardo's opinion and, (although I appreciate you) Msx, I think you go a little off the mark with your opinion.

    The idea here, although it is nuanced with personal tones, is understandable.

    I've always fought with people over things like Elementary, that no matter how great their idea is and no matter how spectacular its design is, they sometimes cross the line between simplicity and functionality. I'm not saying that it is wrong to remove options, but not to remove them, not to uproot them as for example Gnome has been doing with Nautilus, hey, clean the interface in such a way that those options are still present for those who did use them, but that they do not hinder the idea of a more sober interface. If I explain myself? a program MUST be functional, not just pretty, because what is just pretty doesn't always work, you need a balance.

    1.    pandev92 said

      Well, elementary is a joke, okay, they try to copy osx ..., but it doesn't have half the functions of the applications and mac environment ..., I think they have crossed the line that divides the functionality of aesthetics and They have only bet on aesthetics ...

      1.    dwarf said

        Right, the problem is when they cross that fine line between cleanliness and functionality… hell, they shouldn't.