Protective Systems Fail at the Usability Layer

Apps request photo or calendar access, but users don't realize they're granting access to ML-powered inferences—not just raw bytes. The permission model treats data as static files, not inference fuel.

Method: Priva-See, an LLM-based inference system, analyzed data from 465 participants' phones and made privacy-invasive inferences despite accessing only a subset of user data. The system reflects how real adtech companies would leverage ML to build user profiles. After seeing what Priva-See inferred, participants significantly changed their willingness to grant app permissions.

Caveats: Study showed participants inferences from their own data but didn't measure long-term permission behavior changes.

Reflections: How should OS-level permission systems communicate inference capabilities versus raw data access? · Would showing users sample inferences before granting permissions meaningfully change consent patterns? · Can technical controls limit ML inference on permitted data without breaking legitimate app functionality?

Platforms tout teen safety controls, but presence of a setting reveals nothing about whether teens can actually find, configure, and maintain it over time.

Method: Expert evaluation of six privacy tasks across TikTok, Instagram, Snapchat, and YouTube established baseline interaction costs. Then 11 teens aged 14-17 attempted the same tasks in moderated sessions. Most participant attempts exceeded the expert baseline, and recurring dark patterns appeared across tasks—obstruction, sneaking, and interface interference that made protective settings harder to use.

Caveats: Small sample (11 teens) and four platforms. Findings may not generalize to other demographics or apps.

Reflections: Do dark patterns in teen safety settings correlate with platform business model incentives? · Would regulatory requirements for maximum interaction cost improve real-world protection? · How do interaction costs for safety settings change after platform redesigns?

AI code interfaces render output either instantly or token-by-token, but neither matches how programmers actually read: selectively, non-linearly, guided by syntactic structure.

Method: Eye-tracking study with 53 participants compared static, character-based, and structured rendering (revealing code in semantically meaningful chunks derived from syntax hierarchy). Dynamic rendering induced fewer but longer fixations and more sustained focus. Structured rendering further guided attention toward semantically meaningful units and supported high-level understanding before low-level details.

Caveats: Lab study with controlled code snippets. Real-world coding involves editing, debugging, and context-switching not captured here.

Reflections: Does structured rendering improve bug detection rates in AI-generated code? · How should rendering adapt when programmers explicitly request low-level details first? · Can structured rendering reduce cognitive load during code review of large AI-generated functions?