GroupR_FinalReport
GroupR_FinalReport
To make sure our new privacy features are helpful and easy Throughout the interview process, we carefully took notes,
to use, we'll be asking for feedback from people through capturing not only the participants' words but also the
tests. This way, we can make any changes needed to ensure context and subtleties of their responses. This attention to
these features work well for everyone. detail ensured that we could revisit the insights of each
interview during our analysis phase. Each member of our
To ensure the effectiveness and user-friendliness of these team had a clear role during the interviews, whether leading
proposed features, we plan to engage directly with users. the discussion or taking notes. This structured approach
Through a series of contextual inquiries, cognitive allowed us to collect rich data while maintaining a
walkthroughs, and feedback sessions, we can make any comfortable atmosphere for our participants.
changes needed to ensure these features work well for
everyone. The design of our inquiry reflected our commitment to
understanding the user experience fully. We weren't just
THE DESIGN PROCESS – CONTEXTUAL INQUIRY looking for quick answers; we sought to comprehend the
PROCESS AND RESULTS narratives behind users' interactions with privacy and
The design process delves into the comprehensive account security settings. This comprehensive approach underlined
of our project's development, detailing the thought behind the main area of our study, combining a respect for our
our design decisions and the insights we gathered through participants with a need for meaningful data.
our contextual inquiry. It's divided into two segments: 'The
Process,' which outlines our methodological approach to the Results And Discussions
interviews, and 'Results and Discussion,' which interprets Through the data generated from our contextual inquiry and
the findings from our affinity diagramming and how these the affinity diagramming process, we identified key themes
findings influenced our feature development. that directly influenced the design of our low-fidelity
prototype features. These themes surfaced as distinct
The Process patterns in user behavior and preferences, guiding our
Our project set out to deeply understand the choices users decisions to enhance user experience over privacy settings.
make when they navigate digital privacy and security
settings. The goal of our interviews was to learn what users One pronounced theme was the user’s desire for more
know, how they feel, and what they do when faced with control over their data, particularly the ability to restrict
decisions about their digital privacy. We designed our data usage on a need-only basis. This preference was
especially pertinent to location data, which many apps tend specific user needs and preferences, we aim to increase user
to access indiscriminately. The resulting feature, toggleable satisfaction and trust in digital platforms. These
privacy settings with granular options, addresses this issue improvements represent a step towards more transparent
head-on. It allows users to selectively permit app access to and user-friendly digital experiences, where users can feel
their location data, satisfying their need for more granular confident in their interactions with technology.
control. This was conceptualized after observing that users
The development of these features was not only driven by
often improvised their own solutions to limit app
user feedback but also by the underlying ethos of
permissions, signifying a gap in the current app
empowering users to make informed decisions about their
functionality that needed to be bridged.
digital privacy. Each feature contains a specific aspect of
Another significant finding was the user’s split attitude user concern, offering solutions that are both practical and
towards data usage information during app installation. attuned to the evolving landscape of digital privacy.
Some users showed a preference to experiment with the app
The Design Process
first and adjust settings later, while others advocated for In designing our prototype, we put our persona, Abby, at
upfront control. Our optional popup on data usage during the center of all our decisions in the design process. As a
the installation of apps is a balanced response to this 4th-year student who also maintains an active social life, we
problem. It provides a high-level overview of data usage for can assume that their available time to learn and understand
users who value briefness and allows for deeper inspection our new features is limited. This, in addition to their
and control for those who prefer in depth details. This hesitancy in learning new technology, our focus in
feature elegantly encapsulates the varying degrees of user designing our features was intended to enhance the usability
engagement with privacy information, offering a quick of our app by making it as quick and easy to learn as
installation process for some and detailed control for others. possible. We catered our tasks to reflect what we imagined
The third feature, allowing users to track and visualize Abby's typical experience would be, hoping to craft a
personal information leakage, was born out of the concern system that finds a balance between their privacy and its
for managing privacy across numerous apps. Users found it ease-of-use.
challenging to navigate the multitude of privacy settings Toggleable Privacy Settings with Granular Options
scattered across different apps. By introducing a centralized We envisioned Abby encountering situations where she
data information display, we aim to alleviate this problem, feels their privacy is compromised, such as discovering
offering users a unified view of their privacy settings and excessive location tracking by their favorite social media
any potential information leakage. This responds to the app. This scenario sparked the inspiration for the
problem of disperse settings management and makes the development of our Toggleable Privacy Settings with
oversight of personal data more approachable for the Granular Options feature, allowing Abby to have more
average user. control over their app's permissions, aligning with their
The process of translating these themes into tangible desire for selective location tracking only during specific
features involved evaluating the impact of the identified activities like uploading photos. Our design was aimed to
problems. For example, the granular privacy settings provide them with a solution that felt intuitive and
feature was a direct response to the observation that users customizable, allowing them to exert control over their
often felt their choices were too limiting. By enabling users privacy without adding unnecessary complexity. We
to have nuanced control over their privacy settings, we achieved this by maintaining a familiar look to existing UI
address a widespread and fundamental user need. on mobile devices such as iOS, Apple’s operating system
for mobile devices.
Similarly, the data usage popup feature reflects the user’s
need for more accessible information about what data an Optional Popup on Data Usage During Installation
app will access. This was a compromise between the two Abby's cautious approach to learning new software guided
user groups—those who want to use the app quickly and our design decisions in our design for the optional popup on
those who wish to know more before using it. This feature data usage during installation. Abby, being wary of dense
aligns with the observed concern for transparency and user terms of service agreements, would appreciate a clear
control, providing a streamlined yet informative installation overview of an application's data usage before installation,
experience. while still enhancing their awareness of her digital privacy.
As with the first feature, we utilized the familiarity of
Lastly, the visualization of personal information leakage existing App Store UI for our design decisions. For the
represents a proactive approach to privacy management. It aspects of our design that did not have existing designs the
provides a way for users to see what data has been accessed user could pull from, such as the modal popup before the
by apps, addressing the problem of hidden data practices, installation of an application, we kept the design as simple
and giving users a tool to monitor and secure their personal as possible by only including the essential items needed
information actively. such as a short list of icons representing the types of data
These features embody our commitment to enhancing user usage and a button to continue with the installation.
privacy in practical, user-driven ways. By addressing
Tracking and Visualizing Personal Information Leakage
We recognized Abby's need for an efficient way to manage
her digital footprint without conflicting with her busy
lifestyle. This led to the development of the Tracking and
Visualizing Personal Information Leakage feature. By
providing Abby with a centralized dashboard to monitor
and manage privacy settings across all her installed apps,
we aimed to simplify the process of ensuring her data
security, empowering her to make informed decisions
without investing excessive time and effort.
The Prototype
As our features heavily utilized the use of existing mobile
design philosophies for familiarity and ease of learnability
for our user, we opted to use Figma which has powerful
tools for designing modern mobile interfaces, as well as
having a vast library of existing components—such as in in
Figure 2 Familiar IOS Design
Figure 1—which we were able to learn from to create our
own. Repetition
The adoption of reusable components not only streamlined
the development of our features but also aided in
reinforcing repetition, a fundamental design principle
crucial for enhancing learnability. By incorporating
reusable elements, we enforced a consistent design
throughout our system, enabling users to quickly grasp and
navigate its functionalities.
In figure 3, we showcase the UI elements designed to
facilitate granular control over location tracking
permissions, prominently feature our iOS inspired menu
designs. Using Figma's component creation capabilities, we
Figure 1 IOS UI Kit for Figma ensured consistency in the appearance and functionality of
Familiarity toggle switches and dropdown menus across the app.
The ideal result of our features is for them to be “invisible”
to the end user. That is, they are intended to feel as familiar
to the user as possible without impeding on their intended
goals.
We did this by pulling designs and concepts from Figma’s
component library and our existing preconceptions in what
to expect. In figure 2, we display two screens which are
very similar to an IOS app store and settings. We found that
trying to innovate on these aspects of our features made it
more difficult to learn as a first-time user.