TL;DR
This paper explores how to better support app developers in creating privacy-friendly applications for children. Using a Research through Design approach, the study identifies developers' needs and systemic barriers, suggesting that a multi-stakeholder effort is crucial to shift the industry towards prioritizing children's digital well-being.
What Problem Does This Paper Address?
Children are spending more time on mobile devices than ever before, and many apps designed for them employ data tracking and targeted advertising techniques that raise privacy concerns. While regulations like the UK's Age-Appropriate Design Code aim to protect children, developers face systemic challenges in implementing privacy-friendly practices. These challenges include a lack of clear, actionable guidance, the complexity of third-party libraries, and financial pressures from marketplaces that often prioritize data monetization. This paper aims to understand these barriers and explore how to better support developers in creating apps that prioritize children's best interests.
Methods
The authors employed a Research through Design (RtD) methodology, which involves using design as a method of inquiry to explore complex problems. Their process consisted of three phases:
- Ideation Workshop: Experienced HCI designers generated 12 speculative design concepts (Speculative Sketches) aimed at supporting privacy-friendly app development.
- Design Workbook: These sketches were refined into more detailed illustrations with descriptions, forming a standalone Design Workbook that participants could engage with independently.
- Speed Dating Interviews: The researchers conducted semi-structured interviews with 20 children's app developers. During these interviews, developers were presented with the 12 design concepts one by one, and asked to provide feedback, share concerns, and identify their requirements and preferred features. This "speed dating" approach allowed for rapid exploration of various design futures.
Datasets
Not discussed in the paper.
Key Insights and Ideas
- Developers need actionable, credible guidance: Current privacy regulations are often complex and difficult to translate into practical development steps. Developers want clear, concise guidelines backed by trustworthy organizations.
- Third-party libraries are a double-edged sword: While they simplify development, they are also a major source of data tracking. Developers need SDKs that are easy to integrate, lightweight, and guaranteed to be privacy-compliant, but also need assurance that these won't negatively impact user experience or app branding.
- Systemic barriers are significant: Developers feel pressured by marketplaces that incentivize data monetization. They are hesitant to adopt privacy-friendly practices if it means a competitive disadvantage or financial loss.
- A multi-stakeholder approach is essential: Addressing children's privacy in apps requires more than just developer tools. It necessitates the involvement of parents, regulatory bodies, and marketplaces to create a more supportive ecosystem.
- "Privacy-friendly" needs to be normalized: Developers are more likely to adopt privacy-enhancing features if they become a standard, expected practice across the industry, rather than a niche offering.
Key Results
The study identified 12 design concepts that developers reacted to. Key themes emerged regarding:
- Guideline Support: Developers favored simple, actionable checklists and requirement matrices over complex legal documents. They also expressed a need for formal training and certification to build credibility.
- Development Libraries: Participants were interested in "plug-and-play" SDKs that simplify privacy implementation but were concerned about potential negative impacts on user experience and app branding.
- Compliance Checking: Developers preferred constructive feedback from credible sources over automated tools that might be unreliable or easily gamed. They also stressed the importance of integrating compliance checks early in the development cycle.
- Alternative Funding: While concepts like crowdfunding and subscription marketplaces were proposed, developers were skeptical of their success, suggesting gradual changes to existing marketplaces and lobbying for ethical categories.
- Recognition of Best Practices: Developers saw value in badges and awards for privacy-friendly practices, but emphasized the need for these to be credible, independently assessed, and widely recognized to incentivize adoption.
Limitations and Future Work
The authors acknowledge several limitations:
- UK Market Focus: The study primarily focused on the UK app market, and future research should include stakeholders from other regions.
- Mobile Apps Only: The research concentrated on mobile apps, not a broader range of children's digital products.
- No Subgroup Distinction: The analysis did not differentiate between participant subgroups (e.g., by role or experience), though individual preferences for design ideas were noted.
- Sample Size and Generalizability: The sample size of 20 developers, mainly from the UK, may limit generalizability to a wider international audience, especially in regions where privacy regulations are less prioritized.
- Design Process: Future work could involve developers and other stakeholders more directly in the co-design of solutions and prototyping.
Future work should focus on developing multi-stakeholder initiatives, fostering trust in design guidelines, and exploring new ways to incentivize privacy-friendly development within the existing app ecosystem.
Summary updated