Wytyczne dotyczące interfejsu

These guidelines are designed to help developers and designers create a beautifully consistent experience on the elementary OS desktop. They were written for interface designers, graphic artists and software developers who will be working on elementary OS. They will not only define specific design elements and principles, but will also instill a philosophy that will help you decide when it is appropriate to deviate from the Guidelines. Adhering to the suggestions contained here will provide many benefits:

Wytyczne te będą pokrywały podstawowe zasady tworzenia poszczególnych elementów interfejsu, przypadków ich stosowania oraz łączenia efektywnie w całość. Dzięki temu twoja aplikacja będzie bardzo dobrze integrowała się z systemem. Należy pamiętać, że te wytyczne zostały stworzone z myślą ułatwienia projektowania aplikacji, a nie odwrotnie.

Jednakże, należy zwrócić uwagę że jest to zbiór wytycznych - nie zasad. Każdego dnia powstają nowe, piękne rodzaje interfejsów, a mnóstwo z nich nadal czeka na odkrycie. Dokument ten jest cały czas "żywy", co oznacza, że będzie on nieustannie aktualizowany.

Po nie napisane do tej pory sekcje, proszę się zwrócić do GNOME HIG

Filozofia projektowania

The elementary OS HIG isn't just about a set of concrete rules; it's meant to be flexible and extensible. As such, this very first portion of the guideline is all about the guiding philosophy we employ. For a quick crash course, we like "The User is Drunk":

Czym NIE jest design

Before we get into all the things that make up elementary OS apps, there is a clarification that needs to be made. We need to understand what exactly design is about, but more importantly we want to smash two major myths:

  1. Design to nie jest coś co dodajesz PO ukończeniu produktu. Czy zdajesz sobie z tego sprawę czy nie, powinieneś bez przerwy projektować to co budujesz. Jest to wewnętrzna część procesu tworzenia. Design to nie jest po prostu wygląd. Nie składa się on z kolorów i czcionek. Design to sposób działania. Musisz podejmować decyzje czy dodać przycisk z ikoną, czy może z tekstem oraz określić najlepszy rozmiar i kolor tego przycisku. Decyzje składają się na design produktu jako całości.

  2. Design nie jest jak twoja opinia. Design powinien być poddawany testom. Jeden projekt będzie lepszy dla uzyskania danego celu od drugiego. Wyobraź sobie sytuację, kiedy musisz wybrać rower. Zwykły składak jest zupełnie inaczej zaprojektowany niż rower górski. Cechy takie jak waga, wielkość, rodzaj kół są bardzo ważne podczas dobierania roweru dla swoich potrzeb. Skoro rozumiemy, że design to proces rozwiązywania określonych problemów musimy także zrozumieć, że problemy te możemy rozwiązać na różne sposoby. W tym celu powinniśmy wybrać naefektywniejszy z nich.

  1. Design to nie okleina, Aral Balkan
  2. Projektowanie nie jest subiektywne, Jeff Law

Zwięzłość

Zawsze staraj się, aby twoja aplikacja była cały czas czytelna. Główne przeznaczenie twojej aplikacji powinno być zawsze od razu zauważone. Możesz tego dokonać na różne sposoby, lecz jednym z najlepszych z nich jest zasada zwięzłości.

Unikaj przeładowania

Często kuszące jest dodawanie coraz to nowych funkcjonalności do aplikacji. Powinieneś jednak pamiętać, że każda z nich ma swoją cenę. Za każdym razem gdy dodajesz nową funkcjonalność to:

Myśl modułowo

Build small, modular apps that communicate well. elementary OS apps avoid feature overlap and make their functions available to other apps either through Contractor or over D-Bus. This both saves you time as a developer (by other apps making their functions available to you), and is a courteous gesture towards other developers (by making your app's functions available to them).

Unikaj konfiguracji

Jeżeli to możliwe, unikaj stosowania widoków opcji lub konfiguracji twojej aplikacji. Dawanie użytkownikowi panelu opcji jest łatwą drogą do zmiany zachowywania się aplikacji. Jak to bywa podczas przeładowania funkcjonalnościami, możliwość ustawiania opcji oznacza więcej kodu, błędów, testów, dokumentacji i większej złożoności programu.

Build for the "Out of The Box" Experience

Design with sane defaults in mind. elementary OS apps put strong emphasis on the out of the box experience. If your app has to be configured before a user is comfortable using it, they may not take the time to configure it at all and simply use another app instead.

Zapytaj System Operacyjny

Zbierz jak najwięcej informacji. Zamiast pytać użytkownika o jego aktualne miejsce gdzie przebywa, zapytaj o to system. Zmniejszy to liczbę rzeczy, którą będzie musiał zajmować się użytkownik i sprawi, że twoja aplikacja będzie wyglądała na bardziej zaawansowaną i zintegrowaną z systemem użytkownika.

Czy na prawdę tego potrzebujesz?

Zapytaj siebie czy kolejna opcja do konfiguracji jest naprawdę potrzebna, lub czy będzie potrzebna użytkownikom. Nie pytaj użytkowników o takie rzeczy - od tego są inżynierowie i projektanci.

Gdy Absolutnie Musisz

Zachowaj kontekstowość. Zamiast przesuwać preferencje do okienka konfiguracyjnego, rozważ wyświetlenie ich w kontekście z obiektem, którego dotyczą ( bardziej jak opcje tasowania i powtarzania pojawiają się obok twojej biblioteki muzycznej).

Jeżeli twoja aplikacji wymaga wcześniejszej konfiguracji przed użyciem (np. jak klient e-mail), to postaraj się zaprezentować ten krok w głównym oknie jak Ekran powitalny. Upewnij się, że jesto to naprawdę wymagane. Dodawanie niepotrzebnych kroków i/lub ekranów z opcjami konfiguracji powstrzymuje użytkowników przed rozpoczęciem używania Twojej aplikacji do celów których została ona docelowo stworzona.


Zobacz Także:

  1. Pola wyboru, które zabijają Twój produkt przez Alex Limi
  2. Don't Give Your Users Shit Work - Zach Holman
  3. The Wizard Anti-Pattern - Stef Walter

Minimalna Dokumentacja

Większość użytkowników nie chce zagłębiać się w plik pomocy przed użyciem twojej aplikacji. Wręcz przeciwnie, oczekują oni, że twoja aplikacja będzie na tyle intuicyjna i prosta aby zrozumieli ją bez niczyjej pomocy.

Używaj zrozumiałej kopii

Avoid technical jargon and assume little-to-no technical knowledge. This lets your app be "self-documenting."

Provide non-technical explanations instead of cryptic error messages. If something goes wrong, a simplified explanation of what happened and how to fix it should be presented.


W celu uzyskania więcej informacji zobacz Styl Pisania.

Użyj obiegu

To co użytkownik widzi jest bardzo ważne dla jego user experience, lecz równie ważny jest workflow oraz sposób w jaki użytkownik korzysta z aplikacji. W tej sekcji przedstawimy kilka ważnych kroków dla typowego workflow:

Doświadczenie pierwszego uruchomienia

Wymagana Konfiguracja

When a user first launches an app, they should be able to get down to business as quickly as possible. If configuration is not absolutely required for the first use, they should not be required to configure anything. If configuration is required, they should be presented with a clean and simple welcome screen within the app. Avoid separate configuration dialogs when launching.

Prędkość uruchamiania

Pierwsze uruchomienie aplikacji to pierwsze wrażenie, jakie robi ona na użytkowniku: to szansa by pokazać jej design i szybkość. Jeśli Twoja aplikacja musi skonfigurować się w tle, zanim zostanie uruchomiona w widoczny sposób, użytkownik może odnieść wrażenie, że jest ona wolna i potrzebuje sporo czasu by się uruchomić. Zamiast tego, skup się na tym, by okno aplikacji pojawiało się szybko i by aplikacja była od razu gotowa do użycia, wszelkie działania w tle mogą ruszyć już po pojawieniu się okna aplikacji na ekranie. Jeżeli zadania w tle blokują kolejne działania (np. użytkownik nie może wykonać pewnych zadań, dopóki poprzednie nie zostaną zakończone), pokaż użytkownikowi jakiś znak, że program przeprowadza procesy w tle (patrz: Pomysły na widgety).

Witanie użytkownika

Jeżeli nie ma zawartości, którą można pokazać użytkownikowi, zapewnij mu możliwość wykonania pewnych akcji za pomocą ekranu powitalnego. Pozwól otworzyć dokument, dodać konto, importować płytę CD lub zezwól na jakiekolwiek działanie, które w kontekście tej aplikacji ma sens.

Resetowanie aplikacji

If a user explicitly "resets" the app (ex. by deleting all songs in a music library or removing all mail accounts in a mail client), it should return to its first-launch state.

Normalne uruchomienie

Gdy użytkownik uruchamia aplikację, wykonuje konkretną czynność i oczekuje szybkiej, a czasem nawet natychmiastowej odpowiedzi. Powinieneś/powinnaś skupić się na trzech kluczowych obszarach, jeśli chodzi o uruchamianie: szybkości, oczywistości tego co zrobić dalej oraz stanie aplikacji.

Szybkość

Jak zostało już wcześniej powiedziane, szybkość jest bardzo ważna, zwłaszcza podczas uruchamiania aplikacji. Odstęp pomiędzy momentem gdy użytkownik uruchamia aplikację, a zaczyna z niej korzystać powinien być tutaj jak najmniejszy. Jeżeli aplikacja wymaga tzw. splash screena - to znak, że robisz to źle

Oczywistość

When a user launches your app, they should know exactly what to do next. This is achieved by following the other interface guidelines (ensuring your app is consistent with other apps) and by offering up explicit actions from the get go. If the app typically displays "items," such as songs or emails, let the user get at those items by displaying them when the app opens. If there are no previously-opened items, you should offer to open or create a new item (such as a document) by using a welcome screen.

Stan

If the user has previously used your app, it's typically best to restore the state of the app when opening it again. This means the app comes up to right where the user left off so they can pick up their work again. For a music player, this means opening up with the view where the user left it and the song paused where the user closed the app. For a document editor, this would mean opening up with the same document scrolled to the same spot with the cursor in the same spot on the page.

Zawsze udostępniaj opcję "cofnij".

Czasami użytkownik może wykonać akcję, która niesie destrukcyjne bądź nieodwracalne skutki. Zamiast wyświetlać użytkownikowi ostrzeżenie, aplikacja powinna pozwolić na cofnięcie akcji przez odpowiedni okres czasu. Kilka przykładów, gdy taka funkcja bywa potrzebna:

This behavior should only as a last resort be implemented by providing a buffer time between when the app shows the user what happened and actually performing the action. To keep the experience responsive, the app should always look as if it performed the action as soon as the user initiates it.

This behavior strikes the best balance of keeping out of the user's way while making sure they don't do something unintended. It's important to keep the undo action unobtrusive yet simple and intuitive; a common way of doing so is by using an info bar, though other methods may also be appropriate.


See also: Never Use a Warning When you Mean Undo by Aza Raskin

Zawsze zapisany

Users should feel confident when using elementary OS; they should know that everything they see is saved and up to date.

Apps in elementary OS should operate around an always-saved state. This means that changes the user makes are instantly applied and visible and that making the user manually save things is a legacy or specialized behavior.

For example, a Song Info dialog should update the track information instantly without a user having to press a save button, user preferences should be applied as soon as the user manipulates the relevant widget, and closing an app should mean that reopening it will return to where the user left off.

Zamykanie

Kiedy użytkownik zamyka aplikację zazwyczaj oznacza to że zakończył pracę i chce wyjść z aplikacji

Zapisywanie stanu

Apps should save their current state when closed so they can be reopened right to where the user left off. Ideally closing and reopening an app should be indistinguishable from the traditional concept of minimizing and unminimizing an app; that is, all elements should be saved including open documents, scroll position, undo history, etc.

Zadania w tle

If it makes sense for an app to complete background tasks after the window is closed, the tasks should be completed soon after the window is closed. If the app performs repeat background tasks (such as a mail client), the background tasks should be handled by a separate daemon that does not rely on the app itself being open.

Zamykanie okna aplikacji

It is not desirable for an app window to simply minimize rather than close when the user attempts to close it. Instead, the app window should be "hidden". If it makes sense to continue a process in the background (such as downloading/transferring, playing music, or executing a terminal command) the app backend should continue with the task and close when the task is finished. If it's not immediately apparent that the process has completed (as with the file download/transfer or terminal command), the app may show a notification informing the user that the process has completed. If it is apparent, as with the music, no notification is necessary.

Ponowne otwieranie okna aplikacji

If the user re-opens the app while the background process is still executing, the app should be exactly where it would be if the window had been open the whole time. For example, the terminal should show any terminal output, the music player should be on the same page it was when closed, and the browser should come back to the page it was on previously. For more details, see the discussion of app state on a Normal Launch.


See also: That's It, We're Quitting by Matthew Paul Thomas

Integracja z pulpitem

An important advantage that developers have when choosing the elementary OS platform is the ability to seamlessly integrate their application with the default desktop. Outlined below are the several ways in which you can make your application feel beyond native in elementary OS. This section will cover things like:

App Launchers

The primary method of discovering and using your app will be through an app launcher found in Slingshot or in the dock. In order to provide these launchers you must install an appropriate .desktop file with your app. This includes giving your launcher an appropriate name, placing it in the correct category, assigning it an icon, etc.

.desktop files follow the freedesktop.org Desktop Entry Specification. They should be installed in /usr/share/applications. Users may create their own launchers by putting .desktop files in ~/.local/share/applications.

The contents of .desktop files should follow this formula:

Title is a(n) GenericName that lets you Comment.

Tytuł

You should not include descriptive words in your title. For example, Dexter is called "Dexter," not "Dexter Address Book." Midori is just "Midori," not "Midori Web Browser." Instead, use the GenericName attribute of your app's .desktop file for a generic name, and the Comment attribute for a longer descriptive phrase.

GenericName

If your app is easily categorized or described with a generic name, you should use that for the GenericName attribute in your app's .desktop file. If you can say, "My app is a(n) ____," then whatever fits in that blank could be the generic name. For example, Maya is a calendar, so its generic name is "Calendar."

You should not include articles (the, a, an) or the words "program," "app," or "application" in your app's generic name.

The generic name should be in title case and may be used around the system to better describe or categorize your app.

Komentarz

The system uses an app's Comment attribute (found in the .desktop file) to succinctly inform a user what can be done with the app. It should be a short sentence or phrase beginning with a verb and containing the primary nouns that your app deals with. For example, the following are appropriate comments:

An app's comment should be in sentence case, not include terminal punctuation (periods, exclamation points, or question marks), and should be as short as possible while describing the primary use case of the app.

Kategorie

Następujące kategorie mogą być użyte by pomóc w szukaniu lub przeglądaniu twoich aplikacji:

For more info, see the FreeDesktop.Org menu entry spec.

Słowa kluczowe

You may also include keywords in your launcher to help users find your app via search. These follow the convention of "X-GNOME-Keywords" (for in the app launcher) and "X-AppInstall-Keywords" (for in the app installer). For example, web browser might include "Internet" as a keyword even though it's not in the app's name, generic name, or description. As a result, a user searching for "Internet" will find the app. Here are some more examples:

Keywords should be single words (in title case) separated by semicolons.


See also: Desktop Entry Specification from FreeDesktop.org

Kontrahent

Contractor is a service and a protocol for exposing services easily between apps. It lets apps interact with other apps and services without hardcoded support for them. You simply add Contractor support, and then any service registered with Contractor is now available for your app to use. Your app can integrate with Contractor in two different ways:

Displaying Results from Contractor

Contractor results are typically presented to users in menu form. Keep the following in mind when presenting Contractor results:

Integracja z dockiem

Integrate your app with Pantheon's dock communicate to communicate its status to the user at a glance.

Paski postępu

Make progress bars unambiguous by referring to a single, specific task. For example, use progress bars to indicate the status of lengthy processes like file transfers and encoding. Do not use progress bars to compound the progress of different types of action.

Badges

A badge shows a count of actionable items managed by your app. Its purpose is to inform the user that there are items that require user attention or action without being obtrusive. This is a passive notification. A badge should not show totals or rarely changing counters. If the badge is not easily dismissed when the user views your app, it is likely that this is not a good use of a badge.

Wskazówki systemowe

Indicators are small icons that live on the top panel. They give users a place to glance for a quick indication of various settings or events. Clicking the icon shows a small menu with related actions available to the user.

Does Your App Need an Indicator?

The indicator area is prone to clutter and inconsistent paradigms. Given that users will probably install many third-party apps, we must be careful about the number of indicators we show and how they behave. Keep in mind that only a very small set of applications need or benefit from an indicator. Avoid adding an indicator if:


See also: Farewell to the Notification Area by Matthew Paul Thomas

Container Widgets

Okna

Windows form the foundation of your app. They provide a canvas with basic, built-in actions such as "closing" and "resizing". Although users may see windows as being all the same, elementary OS has several distinct window types. It's important to understand the types of windows available to you, window behavior in general, and behavior that is specific to a certain window type. This section will cover the different types of windows available in elementary OS. Although each type of window is a bit different, think of them all as a subclass of a window. Unless otherwise stated, they all behave as an average window.

Tytuły okien

When dealing with window titles, consider that their main use is in distinguishing one window from another. A good window title will provide a description that helps a user make a selection. Keep that in mind as you consider the following:

Dialogi

24
Dialog warning icon

Główny tekst zawierający podstawowe informacje i sugestie

Podrzędny tekst zawierający dalsze szczegóły. Zawiera on także informacje wyjaśniające każde nieoczywiste konsekwencje akcji.

24
Anuluj
Sugerowana czynność

Tekst powiadomienia

Zawiadomienie zawiera pierwszorzędny i drugorzędny tekst.

The primary text contains a brief summary of the situation and offer a suggested action. This text should use the CSS class primary.

The secondary text provides a more detailed description of the situation and describes any possible side effects of the available actions. It's important to note that a user should only need the primary text to make a decision and should only need to refer to the secondary text for clarification. This text should be placed one text line height beneath the primary text using the default font size and weight.

Make both the primary and secondary text selectable. This makes it easy for the user to copy and paste the text to another window, such as an email message.

Kolejność przycisków

"OK" is not Okay

When presenting a dialog to a user, always use explicit action names like "Save..." or "Shut Down". Consider how "OK" lets users proceed without understanding the action they are authorizing. Not all users will read the question or information presented to them in a dialog. Using specific action names will make it harder for a user to select an unintended action and may even encourage them to read the presented information before making a selection.

Preferowane Dialogi

Preference dialogs should be made Transient, but not Modal. When a user makes a change in a preference dialog, the change should be immediately visible in the UI. If the dialog is modal, the user may be blocked from seeing (and especially from interacting with) the change. This means they will have to close the dialog, evaluate the change, then possibly re-open the dialog. By making the dialog transient, we keep the dialog on top for easy access, but we also let the user evaluate and possibly revert the change without having to close and re-open the preference dialog.


Zobacz też:

  1. Why 'Ok' Buttons In Dialog Boxes Work Best On The Right by UX Movement
  2. Why The Ok Button Is No Longer Okay by UX Movement
  3. Should I use Yes/No or Ok/Cancel on my message box? on UX StackExchange
  4. Where to Place Icons Next to Button Labels by UX Movement

Wyskakujące

Popovers are like a contextual dialog. They display transient content directly related to something that was clicked on and close when clicked out of, like menus.

A popover should be used when a user wants to perform a quick action without getting out of the main UI. Some examples of where a popover could be used are adding a contact from an email, adding a bookmark in a browser, or displaying downloads or file transfers.

Popovers should not be used when displaying only a simple list of items; instead, use a menu. Likewise, don't use a popover if the user would spend more than a few seconds in it; instead, use a dialog. Remember that popovers are contextual and should directly relate to the UI element from which they spawn.

Paski narzędzi

A Toolbar is useful for providing users with quick access to an app's most used features. Besides Buttons, a Toolbar is one of the most frequently used UI elements. It may seem like a simple container, but it is important to remain consistent in its use and organization.

Układanie pasków narzędzi

Toolbar items should be organized with the most significant objects on the left and the least significant on the right, with the AppMenu always on the far right of the Toolbar. If you have many toolbar items it may be appropriate to divide them into groups with space in between each group. Keep in mind that when viewed with RTL languages, your toolbar layout will be flipped.

UI Toolkit Elements

elementary OS uses consistent user interface (UI) elements to bring a unified and predictable experience to users, no matter what app they're using. When used properly, this ensures a small (or nonexistent) learning curve for your app.

Koncepcja widżetów

Before we get into all the widgets available in elementary OS, we need to cover some basic concepts that apply to all widgets. Employing these concepts correctly will create a more seamless experience for your users and help you avoid sifting through bug reports!

Kontorlki które nic nie robią

A very common mistake for developers to make is creating controls that seemingly do nothing. Keep in mind that we want to present an environment where users feel comfortable exploring. A curious user will interact with a control expecting there to be some immediate reaction. When a control seemingly does nothing, this creates confusion and can be scary (Think,  "uh-oh I don't know what happened!"). In some cases, controls that do nothing are simply clutter and add unnecessary complexity to your UI.

Consider the "clear" button present in search fields. This button only appears when it is relevant and needed. Clicking this button when the field is already clear essentially does nothing. 

Czułość

Sometimes it doesn't make sense for a user to interact with a widget until some pre-requisite is fulfilled. For example, It doesn't make sense to let a user click a browser's "Forward" button unless there is forward history available. In this case, you should make the "Forward" button insensitive or a user may click it, expecting a result, and be confused when nothing happens.

It's usually better to make a widget insensitive than to hide it altogether. Making a widget insensitive informs the user that the functionality is available, but only after a certain condition is met. Hiding the widget gives the impression that the functionality is not available at all or can leave a user wondering why a feature has suddenly "disappeared".

Ukryte widgety

When a widget only makes sense in a certain context (not as an indicator of an action to be performed) sometimes it does make more sense to hide it. Take hardware requirements for example: It may not make sense to show multi-display options if the system only has a single display. Making multi-display options insensitive is not really a helpful hint on this system. Another exemption to this rule is a widget that a user will only look for in context, like the clear button example above. Finally, Keep in mind that insensitive items will still be recognized by screen readers and other assistive tech, while hidden widgets will not.

Odstępy

Wyrównanie


See also: Form Label Proximity: Right Aligned is Easier to Scan by UX Movement

Paski informacyjne

Infobars provide contextual information and actions to the user with varying levels of severity.

It is important to determine the severity or type of infobar to use. There are four types of infobars available:

Ekran powitalny

Ekran powitalny jest przyjaznym sposobem na pomoc użytkownikom oswoić się z Twoją aplikacją.

Użycie

Typically a Welcome Screen is used for apps like Noise or Scratch where you have to import or create objects in a library before you can interact with them. This provides your users with a clear path to getting started and points out any immediate steps they must take before your app becomes useful.

If your app lets users clear its library, make sure that it returns to the Welcome Screen instead of an empty list.

Labeling

The Welcome Screen consists of two sets of labels:

Iconography

Grouped with each action is an icon that helps to quickly visualize it. Most of the time these will be Action icons, but you can use Places icons when importing or setting a location and even Apps icons if you must open a configuration utility.

Lista źródeł

A source list may be used as a high-level form of navigation. Source lists are useful for showing different locations, bookmarks, or categories within your app.

Sekcje

A source list may be separated into different collapsible sections, each with its own heading. For example, a file manager might have a section for bookmarked locations, a section for storage devices attached to the computer, and a section for network locations. These sections help group related items in the source list and lets the user hide away sections they might not use.

Avoid nesting expandable sections within a source list if possible; if you find yourself wanting to do this, you may need to rethink the sections.

Hierarchia

Hierarchy is important with source lists, both within the widget itself and within the broader scope of your app.

Sections in the source list should be sorted from most important at the top to least important at the bottom. If you're having a hard time deciding the relative importance of each section, think about which section a user is likely to use more often. Sorting the sections this way ensures that the most important items are always visible, even if the source list is too short to fit all of the items, though of course items at the bottom will still be accessible via scrolling.

A source list goes at the left side of a window (or right side for right-to-left languages). Because the user reads in this direction, the sidebar is reinforced as being before (and therefore at a higher level than) the app's contents.

Przyciski

Buttons are an incredibly important widget to understand since your app will undoubtedly contain them.

Tool Buttons

Labeling

Tool Buttons are almost always icon-only and do not provide a button border. They should not be accompanied by a label.

Wskazówki narzędzi

All Tool Buttons should have tooltips, since they do not contain a label. This assists users with disabilities as well as giving a translation for an unrecognized icon. Tooltips should be done in Sentence Case.

Like text button labels, a tooltip should clearly describe what will happen when the button is pressed.

Text Buttons

Labeling

Text Button labels should be done in Title Case.

Like menu items, Text Button labels should consist of an Action or a Location but not a status. Make sure that a button's label clearly describes what will happen when it is pressed.

"Remove Account", "Transfer to Jim's Laptop", and "Import 20 Songs" are good labels.

"OK", "Get more storage!", and "Low Battery" are not good button labels. The "Get more storage!" label has incorrect capitalization and unnecessary punctuation. The other two labels do not indicate what will happen as a result of clicking the button.

Wskazówki narzędzi

Since Text buttons have a clear and explicit label, it's usually unnecessary to give them a tooltip.

Linked Buttons

Użycie

Linked Buttons are used to group actions that are either similar in nature or mutually exclusive. For example, they could group text options like Bold, Italic, and Underline. Or they can be used to group mutually exclusive states like Grid, List, or Column view.

Labeling

Linked Buttons should never contain colored icons. Only 16px symbolic icons OR text. Do not mix icons and text.


  1. Why The OK Button Is No Longer Okay by UX Movement
  2. Should I use Yes/No or Ok/Cancel on my message box? on UX StackExchange

Menu aplikacji

The AppMenu is an optional menu which is opened using the gear-shaped icon on the far-right of an app's toolbar. It provides relevant menu items in place of the traditional "File, Edit, View..." menu bar.

Użycie

Rozpatrz czy twoja aplikacja potrzebuje widżetu. Większość aplikacji ma widżet ale to nie znaczy że twoja aplikacja potrzebuje Menu Aplikacji.

When adding items to your AppMenu, consider the following:

Pola wyszukiwania

Apps that support the searching or filtering of content should include a search field on the right side of the app's toolbar. This gives users a predictable place to see whether or not an app supports searching, and a consistent location from which to search. Gtk+ provides a convenient complex widget for this purpose called Gtk.SearchEntry.

Distinguish Between Search and Find

Search is for filtering the contents of a library, i.e. Music or Videos, to the matching items. Search is typically initiated when typing anywhere in a library view.

Find is for highlighting matching instances of a string, i.e. in a text editor, web page, or Terminal. It is triggered by a keyboard shortcut (Ctrl+F) or with a search icon. The find bar appears in a revealer below the headerbar with relevant actions such as find next, find previous, highlight all, etc. The revealer may also contain other relevant actions such as replace or go to line.

Behavior

If it is possible to include search functionality within your app, it is best to do so. Any list or representation of multiple pieces of data should be searchable using a search field that follows these rules:

Labeling

Search fields should contain hint text that describes what will be search. You can set this using the entry property "placeholder_text".

Most search fields should use the format "Search OBJECTS" where OBJECTS is something to be searched, like Contacts, Accounts, etc.

If the search field interacts with a search service, the hint text should be the name of that service such as "Google" or "Yahoo!"

Checkboxes & Switches

Checkboxes

Checkboxes present a way for users to select items from a list.

Użycie

Use checkboxes when users are making a selection of items. Make sure that a user can toggle the state of the checkbox by clicking on the label associated with the checkbox.

Labeling

Labels associated with Checkboxes should usually be nouns or nounal phrases.

Przełączniki

Switches present a way for users to toggle certain features or behaviors "on" or "off".

Użycie

Don't use switches to include related items as part of a list, instead use a checkbox. Think of switches as acting on independent services and checkboxes as including objects in a list. This is an important distinction to make.

Notice that the option "Record from microphone" is a great candidate for a switch. You are enabling and disabling this recording service.

However, if there are two options "Record system sounds" and "Record from microphone" you are now dealing with a list of related items to include as part of a larger recording service (who's on and off state is independent of what services it includes). In this case, a checkbox is more appropriate to denote this inclusion.

Labeling

When possible, directly call out the service you are acting on. Do not use words that describe the state that the widget is describing like "Enable Multitouch", "Use Multitouch", or "Disable Multitouch". This can create a confusing situation logically. Instead, simply use the noun and write "Multitouch".


See also: 3 Ways to Make Checkboxes, Radio Buttons Easier to Click by UX Movement

Zeszyty

Notebooks are a type of widget that lets apps show one of multiple pages (also colloquially referenced as "tab bars").

Static Notebook

A Static Notebook is a small set of unchanging tabs, commonly seen in preferences or settings screens. The tabs appear as linked buttons centered at the top of the content area. A Static Notebook should typically contain two to five tabs.

Dynamiczny Zeszyt

A Dynamic Notebook is a way for an app to provide user-managable tabbing functionality, commonly seen in web browsers. The tabs appear attached to the toolbar on their own tab bar above the relevant content. Tabs are able to be rearranged and closed and a "new tab" button is at the left ot the notebook widget.

Iconography

Iconography is a key part of elementary OS. Icons make up the majority of the UI that your user will be actively engaging with; they're what bring the system to life and cater to the powerful recognition engine of the human brain.

Kształt

Your icon should have a distinctive shape/silhouette to improve its recognition. This shape should not be too complicated, but the icon should not always be a rounded rectangle.

Ostrzegawcza ikona dialogowaIkona CzatuIkona ZdjęćIkona nagrańOnline accounts iconIkona terminala

Metaphors

If you're creating an icon for a hardware device or a file type (such as those for MimeType or Device icons), its shape is typically a visual representation of its real-world counterparts. For example, the icon for a camera is a stylized camera.

Ikona aparatuIkona dysku twardegoIkona myszki
Pakiet ikonIkona tekstu HTMLIkona komputera

Ikony akcji

Action icons are used to represent common user actions, such as "delete", "play", or "save". These icons are mostly found in app toolbars, but can be found throughout the OS.

Ikona Ikona Ikona eksportu dokumentuIkona drukowaniaIkona zapisuIkona usuwaniaIkona wycinaniaIkona cofania zmianyIkona inwersjiIkona odtwarzaniaNew tag iconIkona menu

If your app makes use one of these common actions, reference its corresponding icon instead of creating your own. This ensures a consistent user experience and aids in user recognition of common functions.

If your app has a unique action, you may need to create your own. When doing this, try to follow the look and feel of existing action icons, and include it along with your app.

Rozmiary ikon

elementary OS uses six main icon sizes throughout the OS and it's best to include all six as part of your application.

16 pixel Terminal icon24 pixel Terminal icon32 pixel Terminal icon48 pixel Terminal icon64 pixel Terminal icon128 pixel Terminal icon
16 24 32 48 64 128
128 pixel Terminal icon
128

Design each icon for the size it's meant to be viewed at. In other words, do not design one icon and resize it to fill the remaining sizes, the best result is when each icon is designed individually. For more information about this practice (called "pixel-fitting") and its importance, we recommend reading Dustin Curtis' article, Pixel-fitting.

Paleta kolorów

Color, don't be afraid to use it! Many of the elementary OS icons use vibrant colors; it's best to reserve muted tones and greys for boring system icons.

Ikona MailaRSS Reader iconIkona przeglądarki internetowejIkona ZdjęćIkona internetuIkona kalendarza

Colors do have their connotations, so be cognisant of this when picking them. For instance: red is usually associated with error or "danger" and orange with warnings. But you can use these color connotations to help convey your icon's meaning, such as green for "go".

Symboliczne ikony

Symbolic icons are common system icons, that symbolize files, devices, or directories and are also used to represent common actions like cut, copy, and save.

Each symbolic icon is a reduced form of its full-color counter part. This minimal design ensures readability and clarity even at small sizes.

Symbolic vs. colored icon

Ikony Kolorowe kontra Ikony Symboliczne

The use of full-color and symbolic icons is not interchangeable, both have appropriate uses.

Full color icons are best used for:

Symbolic icons are best used:

Kompozycja

There are three aspects to note when designing an elementary OS icon:

Composition breakdown of elementary OS Videos icon Composition breakdown of elementary OS Terminal icon

Keeping these lines in mind while designing, means you can place elements along them so icons appear more consistent when put together. For example, notice how some elements in both the Terminal and Videos icon above relate to the mean line.

Common Measurements

If you're designing a square-shaped icon, like the one for Terminal seen above, then consider using these common measurements (in pixels) for each icon.

Rozmiar kanwy Base Line x-Height Mean Line Height
16x16 1 14 8
24x24 2 20 12
32x32 2 26 16
48x48 3 40 24
64x64 4 56 32
128x128 9 104 64

Wyjątki

However there are exceptions. Many icons (especially mimetype icons) have ascending and descending elements, which are those elements that extend beyond the base line and x-height line (shown here in pomarańczowy.)

Composition exception example in elementary OS Video icon Composition exception example in elementary OS Terminal icon

Rounder components will generally require some overshoot, to compensate for the optical illusion that makes them look smaller than their rectangular counterparts.

Outlines & Contrast

All elementary OS icons have a thin outline (stroke) to improve their contrast. The width of this stroke is one pixel for all icons, at every size. The color of the outline is a darker variant (30% darker) of the primary color of the icon. For instance, in the calendar icon below, the green header has a stroke of a darker green.

Example of contrast in elementary OS Calendar icon Przykład kontrastu w ikonie Ustawień elementary

To further improve contrast, strokes are also semi-transparent. This ensures that icons appear sharp against a variety of backgrounds. Also, if the element is near-white, this stroke acts as a border and contains, rather than overlaps, its corresponding element. See the above icon for an example of this.

Shadows & Highlights

If you picture an icon sitting on a shelf, facing you, with a light source above it, you may see a small fuzzy shadow near the bottom. Also, since the edges of an object tends to reflect more light due to your position relative to it and to the light source, they will have a highlight. Both these effects are something elementary OS icons emulate in their design to lend them a degree of realism.

Edge Highlight

To apply the edge highlight effect to your icon, draw a subtle, 1 pixel, inner stroke as a highlight. This outline is slightly brighter at the top and the bottom than it is at the edges.

Edge highlight example in elementary OS Music icon

Rzucany cień

To draw the shadow, you'll start by drawing a rectangle. Then fill it with a linear gradient that is perpendicular to the bottom margin of the icon. The gradient has three stops, the first and last of which have zero opacity. Then this entire shape is set to 60% opacity.

Next create two smaller rectangles to "bookend" the larger. Fill each with a gradient identical to the first, but make it radial instead. Center the radial gradient in the middle of a short edge with each stop directly out to the nearest edge—see below for an example. Both these rectangles are also set to 60% opacity.

Pictogram Shadow

If your icon has a pictogram, such as the play triangle in the icon below, you can give it a drop shadow to make it stand out from the background of the icon.

To do this, first duplicate the pictogram, fill it with solid black and set it to 15% opacity. Next, shift it 1 pixel down and place it below the pictogram. Create a copy of this shadow and give it a 1 pixel stroke (also black) and adjust this element to 7% opacity.

Icon Materials

You are free to add gloss (extra highlights) to your icon but this is only a good idea if you're emulating a surface that is more-reflective in real life (such as plastic, glass, etc.) For instance, a sheet of paper is not glossy therefore a icon emulating paper would not be either.

Dos and Don'ts

Below are some "do and don't" examples to consider when creating icons for your app.

Tekst

Although elementary OS primarily uses graphics as a means of interaction, text is also widely used for things like button labels, tooltips, menu items, dialog messages, and more. Using text consistently and clearly both in terminology and format is an extremely important part of designing your app and helps add to the overall cohesiveness of the elementary OS platform.

Writing Style

Use the following rules to keep your text understandable and consistent:

Be Brief

Don't give the user a bunch of text to read; a lengthy sentence can appear daunting and may discourage users from actually reading your messaging. Instead, provide the user with short and concise text.

Myśl w prosty sposób

Załóż, że użytkownik jest inteligenty, lecz niekoniecznie posiada wiedzę techniczną. Unikaj długich, niecodziennych słów i skup się na używaniu prostych i znanych czasowników, rzeczowników i przymiotników. Nigdy nie używaj żargonu technicznego.

Przechodź do sedna

Najważniejsze informacje umieszczaj na początku tekstu. Nawet jeżeli użytkownik nie przeczyta całości, nadal będzie wiedział najważniejsze rzeczy.

Nie powtarzaj się

Powtórzenia mogą być irytujące, a do tego niepotrzebnie wydłużają wiadomości.

Use Visual Hierarchy

Visual hierarchy aids users in reading and comprehending your text as well as knowing what is most important. Use headings and other text styles appropriately.

Język

While much of elementary OS is developed in English, there are many users who do not know English or prefer their native language. While putting text into your app, keep the following in mind:

Capitalization

All textual user interface items, including labels, buttons, and menus, should use one of two capitalization styles: sentence case or title case.

Sentence Case

Sentence case means you capitalize like in a standard sentence or phrase.

Only the first letter of the phrase and the first letter of proper nouns are capitalized. Used for labels and descriptive text.

Title Case

Title case means you capitalize like a book or article title.

Capitalize the first and last words. All nouns, pronouns, adjectives, verbs, adverbs, and subordinate conjunctions (as, because, although) are capitalized. Used for titles, buttons, menus, and most other widgets.

Notes/Exceptions

Proper nouns should always be capitalized properly; this means that, for example, Google should always be shown as "Google," elementary should always be shown as "elementary," and MPEG should always be shown as "MPEG." If you're unsure how a certain pronoun should be officially capitalized, refer to the documentation of the pronoun in question.

Interpunkcja

Proper typography is important throughout elementary OS. Not just for consistency within the OS, but for following proper convention and presenting ourselves as a serious, professional platform.

Unikanie częstych błędów

Hyphens & Dashes

Łącznik (-)

Używaj \u2010 w kodzie. Używany do:

Półpauza (–)

Używaj \u2013 w kodzie. Używany do:

Myślnik (—)

Używaj \u2014 w kodzie. Używany do:


If in doubt, refer to Butterwick's Practical Typography.

These rules apply to the English language; other languages may have their own conventions which should be followed by translators.

Using Ellipses

The ellipsis character (…) is used in the interface for two primary reasons: informing the user of an additional required information and letting the user know text has been shortened.

Dodatkowe informacje

An ellipsis should be used to let a user know that more information or a further action is required before their action can be performed. Usually this means that the user should expect a new interface element to appear such as a new window, dialog, toolbar, etc in which they must enter more information or make a selection before completing the intended action. This is an important distinction because a user should typically expect an instant action from buttons and menu items while this prepares them for an alternate behavior. More specifically, an ellipsis should be used when the associated action:

Skrócony tekst

Ellipses should be used when shortening text that cannot fit in any specific place. For example, if a playlist's name is longer than the space available in the sidebar, truncate it and use an ellipsis to signify its truncation. There are two ways to use an ellipsis when shortening text:

If you're unsure, it's best to use middle truncation as it keeps both the beginning and end of the string in tact. It's also important that you do not ship your app with any truncated text; truncation should only be the result of a user action such as resizing a sidebar or entering custom text.

Kiedy NIE używać Ellipsis


Be sure to use the actual ellipsis character (…) rather than three consecutive period (.) characters.

Nazywanie elementów menu

Menu items should have names that are either actions or locations, never descriptions. Make sure menu items are concise, but also fully describe the action that will be performed when they are clicked.

"Find in Page..." is acceptable as it clearly describes the action that will be performed when the item is clicked. "Software Up to Date" is not acceptable. What happens if I click this item? Where will it take me? What will it do? The outcome is uncertain.