Pith. Sign in

RECORD

Personal Information Ecosystems and Implications for Design

Human-Computer Interaction · Submitted 18 Dec 2006

abstract compiled · 2026-09-23 · no language-model review

The authors' main claim There is a need for designers to design devices as part of a complete ecosystem, not as independent devices that simply share data replicated across them.

how it is stated · asserted 0.97 read the record →

Comment (0) Read on arXiv ↗
Cite ▾
arXiv IDcs/0612081 (version 1)
Pith IDUG5PUCHP, Pith's permanent record of this paper and its review
CitationManas Tungare, Manuel P\'erez-Qui\~nones, Pardha S. Pyla, Steve Harrison. "Personal Information Ecosystems and Implications for Design." arXiv:cs/0612081 (2006). https://pith.science/paper/UG5PUCHP
Claim paper

The compiled record

The paper's own sentences, arranged. Each label is drawn from a closed vocabulary; the number beside it is the probability the classifier gave that label. Numbers in the tables are the authors', checked by code. No sentence in this record was written by a model.

Open the compiled record

Compiled by classifier-1.13-20260917 via OpenRouter, question bank abstract-p1-20260923, 2026-09-23: 1 request, 5,537 input tokens, $0.0002 reported.

What the abstract itself states, as probabilities: claims first 0.05 · states limitation 0.07 · human participants 0.15 · controlled comparison 0.02 · randomized assignment 0.01 · states quantitative result 0.02 · compares with prior results 0.05 · mentions code or data availability 0.02.

The abstract, sentence by sentence

arXiv listing abstract v1. Results and the main claim are underlined; .

Today, people use multiple devices to fulfill their information needs. However, designers design each device individually, without accounting for the other devices that users may also use. In many cases, the applications on all these devices are designed to be functional replicates of each other. We argue that this results in an over-reliance on data synchronization across devices, version control nightmares, and increased burden of file management. In this paper, we present the idea of a \textit{personal information ecosystem}, an analogy to biological ecosystems, which allows us to discuss the inter-relationships among these devices to fulfill the information needs of the user. There is a need for designers to design devices as part of a complete ecosystem, not as independent devices that simply share data replicated across them. To help us understand this domain and to facilitate the dialogue and study of such systems, we present the terminology, classifications of the interdependencies among different devices, and resulting implications for design.

background contribution method result interpretation main claim

What the classifier reports for each sentence. The number is the probability it gave the label.
#sentencerolethe authors' own workstates the main conclusionstrength
s0 Today, people use multiple devices to fulfill their information needs. background 1.00 0.07 0.02 asserted 1.00
s1 However, designers design each device individually, without accounting for the other devices that users may also use. background 0.53 0.08 0.05 asserted 1.00
s2 In many cases, the applications on all these devices are designed to be functional replicates of each other. background 0.98 0.07 0.04 asserted 0.92
s3 We argue that this results in an over-reliance on data synchronization across devices, version control nightmares, and increased burden of file management. background 0.48 0.17 0.21 asserted 0.89
s4 In this paper, we present the idea of a \textit{personal information ecosystem}, an analogy to biological ecosystems, which allows us to discuss the inter-relationships among these devices to fulfill the information needs of the user. contribution 1.00 0.83 0.12 asserted 0.95
s5 There is a need for designers to design devices as part of a complete ecosystem, not as independent devices that simply share data replicated across them. future work 0.50 0.12 0.71 asserted 0.97
s6 To help us understand this domain and to facilitate the dialogue and study of such systems, we present the terminology, classifications of the interdependencies among different devices, and resulting implications for design. contribution 1.00 0.90 0.09 asserted 0.97

What kind of paper the classifier reports this is: position or commentary 1.00 · evidence from argument 1.00.

What was examined, and what was not

sources read
  • arXiv listing abstract v1
not examined
  • full text
  • figures and tables
  • references and citing sentences
  • relations to other papers
levels run
  • P abstract
not run
  • S sections
  • T body sentences
  • C citations
  • R cross-paper relations

Every quoted sentence on this record is the authors'. Every label is from Pith's closed vocabulary, with the probability shown beside it. Every number in the measurements table is the authors', checked by code. Record as JSON

The paper
Original abstract

Today, people use multiple devices to fulfill their information needs. However, designers design each device individually, without accounting for the other devices that users may also use. In many cases, the applications on all these devices are designed to be functional replicates of each other. We argue that this results in an over-reliance on data synchronization across devices, version control nightmares, and increased burden of file management. In this paper, we present the idea of a \textit{personal information ecosystem}, an analogy to biological ecosystems, which allows us to discuss the inter-relationships among these devices to fulfill the information needs of the user. There is a need for designers to design devices as part of a complete ecosystem, not as independent devices that simply share data replicated across them. To help us understand this domain and to facilitate the dialogue and study of such systems, we present the terminology, classifications of the interdependencies among different devices, and resulting implications for design.

Human review

Discussion

Know something about this paper? Leave a comment, or highlight any passage above to comment on it.