How the Plasma Active Human Interface Guidelines Makes the Life of - - PowerPoint PPT Presentation

how the plasma active human interface guidelines makes
SMART_READER_LITE
LIVE PREVIEW

How the Plasma Active Human Interface Guidelines Makes the Life of - - PowerPoint PPT Presentation

How the Plasma Active Human Interface Guidelines Makes the Life of Developers and Users Easier 2012-06-30 Akademy 2012 Thomas Pfeiffer 1 About Me History with KDE: Joined Season of Usability 2008 (KDE HIG and UI Patterns)


slide-1
SLIDE 1

2012-06-30 Akademy 2012 – Thomas Pfeiffer 1

How the Plasma Active Human Interface Guidelines Makes the Life

  • f Developers and Users Easier
slide-2
SLIDE 2

2012-06-30 Akademy 2012 – Thomas Pfeiffer 2

About Me

  • History with KDE:
  • Joined Season of Usability 2008 (KDE HIG

and UI Patterns)

  • Worked a bit with Amarok
  • Worked with Calligra
  • Joined Plasma Active in 2011
  • Current KDE involvement
  • Plasma Active HIGs and interaction design
  • Calligra UX consultancy
slide-3
SLIDE 3

2012-06-30 Akademy 2012 – Thomas Pfeiffer 3

Why Human Interface Guidelines?

  • Consistency
  • +Knowledge transfer
  • +Expectation conformity
  • Proven Concepts that life easier for
  • Users
  • Developers
  • Interaction / UI Designers
slide-4
SLIDE 4

2012-06-30 Akademy 2012 – Thomas Pfeiffer 4

Why Especially in Active Apps?

  • Plasma Active Goals:
  • “Intuitive” interfaces (“Walk up and use”)
  • Seamless experience (Blurring borders

between applications)

  • Touch / Mobile Interfaces (with QML):
  • Less “unwritten conventions” / standards
  • Less examples / experience available
  • More possibilities / freedom
slide-5
SLIDE 5

2012-06-30 Akademy 2012 – Thomas Pfeiffer 5

Types of Active HIGs

  • General Guidelines / Best Practices
  • Widget-/Component-related Guidelines
  • Detail Guidelines (wording, fonts, etc.)
  • Integration Guidelines (e.g. SLC)
slide-6
SLIDE 6

2012-06-30 Akademy 2012 – Thomas Pfeiffer 6

Structure of an Active HIG

An HIG usually answers these questions:

  • When (range of application / purpose of

widget/component)

  • What (description of the widget/component/practice)
  • Why (rationale, optional)
  • How (code to implement guideline, if applicable)
  • Example
slide-7
SLIDE 7

2012-06-30 Akademy 2012 – Thomas Pfeiffer 7

Where and Who

  • Where are they?

http://community.kde.org/Plasma/Active/Development/ActiveHIG (preliminary location)

  • Who are they for?
  • Developers
  • Interface / Interaction Designers
  • (Translators / l10n / i18n)
slide-8
SLIDE 8

2012-06-30 Akademy 2012 – Thomas Pfeiffer 8

Current Status

  • Most new UI ideas/concepts currently

implemented are reflected in HIG

  • No basic guidelines yet
  • No code sections yet

➔Already useful, but still a lot of work

slide-9
SLIDE 9

2012-06-30 Akademy 2012 – Thomas Pfeiffer 9

Future Plans

  • Finish existing HIGs
  • Improve existing HIGs based on feedback
  • Cover all basic topics (currently empty pages)
  • Create HIGs on request by HIG users
  • Create HIGs for new

widgets/components/concepts

slide-10
SLIDE 10

2012-06-30 Akademy 2012 – Thomas Pfeiffer 10

What you can do

  • Use the HIGs :)
  • Give feedback (active@kde.org)
  • Request new HIGs
  • Help with writing new HIGs (just ping me at

colomar@autistici.org)

slide-11
SLIDE 11

2012-06-30 Akademy 2012 – Thomas Pfeiffer 11

Thank you for listening. Now let's rock the device world together!