Please enable JavaScript.
Coggle requires JavaScript to display documents.
User Interface Design Adaptation (how to evaluate adaptation (user's…
User Interface Design Adaptation
possible contexts of use
user-related aspects
: preferences, goals, tasks, physical sate, emotional state, etc.
technology-related aspects
: screen resolution, connectivity, battery, etc.
environment-related aspects
: location, light, noise, etc.
social aspects
: privacy rules, collaboration, etc
characteristics of interface that can be modified
presentation
dynamic behavior
navigation structure, dynamic activation, and deactivation of interaction
content
texts, labels, images
adaption strategies
convservation
ex. simple scaling of UI element
rearrangement
changing layout
simplification/magnification
same UI elements but with modified presentation
increase/reduction
progressive enhancement/graceful degradation in terms of UI elements
Remember
remember to be mindful of existing schema and metaphors that users have adopted (from focus-based to pointer-based to key-based and to touch-based interactions)
remember to think about device where it lives and access time available/makes sense on the device
3 important dimensions for improving cross-device user experience
appropriateness for task performance
so that the structure of interactive application provides an effective fit with what users expect to perform in each device
continuity
the flow of interaction across devices should be fluent and connected
consistency
UI for various devices should be coherent -- parts of the same application
relations between task to perform, UI, and platform
note: platform = group of devices that share similar interaction resources
same task -- same UI -- diff platform
same task -- diff UI -- diff platform
same main task -- diff subtasks -- diff platform
dependencies among diff tasks -- diff platform
tasks meaningful only on some platform
adaptation rules
how UI adapt to the context of use can be described through rules that can be classified according to the types of effect that they can achieve
replacement rules:
indicate how to replace some elements according to the current platform
splitting
: split UI into 2 or more separate presentation -- eg. pacman (bigger screen) > one presentation; pacman (small screen) > 2 presentations (one is playing, another is score)
removal rules
: removing content considered irrelevant for the target device
can be expressed in the format:
Event / Condition / Action
model-based approach
identifying a number of abstraction levels that can be considered when describing interactive applications
task and domain objects
: purpose is to describe
activity
that should be
performed
in order to reach users'
goal
and
objects
that need to be
manipulated
for this purpose
abstract interactive application
: the focus moves to the
interactive
part of application and aims to provide its
description
in terms
independent
of the interaction modality used
concrete interactive application
: the description is modality dependent but independent of the implementation language
interactive application implementation:
actual implementation in some implementation language
how to evaluate adaptation
user's awareness of adaptation
to what extent the user is able to realize that a change in the UI is caused by adaptation
appropriateness of adaptation
whether the system selects a good/appropriate adaptation strategy
transition of adaptation
to what extent the adaptation process allows users to realize what is happening during adaptation
continuity of adaptation
to what extent it is easy to continue the interaction after adaptation
impact of adaptation in decreasing interaction complexity
whether the interaction complexity of the system decreases
impact of adaptation in increasing user satisfaction
to what extent adaptation increases the user's satisfaction
conclusion
distribution: whether it is static or dynamic
migration: according to the state components that it is able to preserve
granularity: whether the solution can involve entire UI, groups, single UI elements, part of UI elements
trigger activation type: which can be on demand or automatic or mixed
interaction modalities: whether solution is monomodal, transmodal or multimodal
types of UIs activated: whether they are precomputed or generated at runtime or a mixed solution
device sharing btw multiple users: whether the sharing consists of the possibility of moving elements in the same device or whether user can interact with the same device
timing: whether UI changes are immediate, deferred or mixed
adaptation approach: whether it is scaling, transducing or transforming approach
architecture: whether the architectural solution is server-based or peer-to-peer