Differential D14985 Diff 40842 source/introduction/convergence.rst

Changeset View

Standalone View

View Options

source/introduction/convergence.rst

1Optimized convergence 1​Optimized convergence
2===================== 2​=====================
3 3​
4Kirigami is made with convergent applications in mind. "Convergent" for 4​Kirigami is made with convergent applications in mind. "Convergent" for
5us means that one instance of an application can adapt its user 5​KDE means that one instance of an application can adapt its user
6interface (UI) depending on the context, most importantly depending on 6​interface (UI) depending on the context, most importantly depending on:
7 7​
8- Primary input method (for now "pointing device + keyboard" vs. touch, 8​- Primary input method (for now "pointing device + keyboard" vs. touch,
9 in the future possibly also simple directional inputs like TV 9​ in the future possibly also simple directional inputs like TV
10 remotes, game controllers, in-vehicle controls, ...) 10​ remotes, game controllers, in-vehicle controls, ...)
11- Physical screen size (for now phone vs. tablet vs. laptop/desktop 11​- Physical screen size (for now phone vs. tablet vs. laptop/desktop
12 screen, in the future possibly also TV screens, smart watches, ...) 12​ screen, in the future possibly also TV screens, smart watches, ...)
13- Screen orientation / aspect ratio (mostly portrait vs. landscape) 13​- Screen orientation / aspect ratio (mostly portrait vs. landscape)
14 14​
15Kirigami is not about simple "responsive" user interfaces, though (i.e. 15​Kirigami is not about simple "responsive" user interfaces, though (i.e.
16those which just adapt their layout a bit), but really optimized ones. 16​those which just adapt their layout a bit), but really optimized ones.
17For example, "pointing device + keyboard" UIs should use 17​For example, "pointing device + keyboard" UIs should use
18mouse-over/hover effects to reveal inline controls, whereas touch UIs 18​mouse-over/hover effects to reveal inline controls, whereas touch UIs
19should use touch gestures. 19​should use touch gestures.
20 20​
21When navigating through hierarchies, portrait mode mode shows only one 21​When navigating through hierarchies, portrait mode mode shows only one
22column/page at a time, whereas landscape shows multiple ones. 22​column/page at a time, whereas landscape shows multiple ones.
23 23​
24UIs for bigger screens show more controls permanently, whereas UIs for 24​UIs for screens with different input methods show more controls permanently, whereas UIs for
fabianrUnsubmitted
Done

I actually think that bigger screens should not necessarily show more controls, but should depend on the used input control too. E.g. a TV witch you navigate with a remote control should not show more controls in my opinion.
So we should not focus just on the screen size, but on the input method too in the next section.

fabianr: I actually think that bigger screens should not necessarily show more controls, but should…
25small screens show only the most important controls always, while 25​small screens show only the most important controls always, while
26showing secondary controls only on demand. 26​showing secondary controls only on demand. The convergence for these
27​screens will prefer to show only the most important controls when the
28​screen has become smaller. Developers and designers must determine which
29​elements on the screen are the most relevant for use.
27 30​
28Kirigami Components will do some of that adaptation / optimization work 31​Kirigami Components will do some of that adaptation/optimization work
29for you, but be prepared to also manually adapt your user interface for 32​for you, but be prepared to also manually adapt your user interface for
30different devices. 33​different devices.