Download Mobile Devices for Interacting with Tagged Objects

4.4. Requirements
75
have much background in software development, and even less so
on mobile devices with their specific intricacies. The development
of services for BIT should thus be easy to learn. Ideally, syntax, semantics, and concepts used in BIT should build on what is
already familiar to many developers from other domains. In addition, the lifetime of some services which are more of a promotional
nature may be limited. Other services require frequent changes.
BIT should therefore support rapid prototyping, short development cycles, and iterative design, which will also be beneficial for
the usability of services [80].
Design for low attention BIT is used in situations with a very different context than many other programs, even on mobile phones.
In virtually all of these situations, the user’s attention is split between the physical product, the mobile device, and an environment
that abounds with stimuli (such as announcements in a retail store
or a chit-chat with a fellow shopper). The design of BIT should
consider these factors and minimize the effort that is needed for
interaction.
Unified user experience In order to ease interaction with the plethora
of services that may be provided, BIT must enforce some restrictions with regard to user interface design. For example, the steps
needed to stop the use of a service should always be the same, no
matter how the service is implemented. BIT should also facilitate
the implementation of common user interface patterns that are
shared by most services, in order to save developers the trouble of
repeating themselves when writing code.
Security and privacy As we envision BIT to be a single tool that mediates all interaction between a user and every physical product’s
digital offerings, it would be easy to track nearly every move of a
user. Privacy is thus a major concern, and BIT must support users
in revealing as little as possible about themselves if they wish to
do so. BIT must also ensure that a service can only access those
resources for which it is authorized. For example, a service must
be constrained to read and write its own storage area only. Likewise, access to context information must be controlled. Finally,
BIT must mitigate potential threats originating from malicious
services in order to protect the mobile phone itself.