Serverless databases could save citizen science, if their interfaces stop scaring users away

Every time a volunteer photographs an unfamiliar moth, records a bird song, or logs the depth of a flooded stream, that observation usually travels to a server owned and paid for by someone else. Citizen science platforms such as iNaturalist, Pl@ntNet, and BirdNET have transformed ecological research by turning millions of ordinary people into distributed sensors, but they all share a hidden vulnerability: they depend on centralised server architecture for data storage, user authentication, and communication. When grant money runs out, those servers keep costing money, and communities that contributed their own data can find themselves locked out of platforms they helped build. A new study published in Web Ecology argues that peer-to-peer distributed databases could solve this problem, and that the decisive factor in whether they succeed will not be the underlying technology but something far more human: the design of the user interface.

The research, led by Julien Jean Malard-Adam of the Institut de recherche pour le développement and the Institut français de Pondichéry, together with colleagues at McGill University, the University of California, Berkeley, and Tamil Nadu Agricultural University, draws on workshops and user feedback gathered during the development of Constellation, a new open-source software tool for distributed scientific databases. Unlike existing data repositories, which produce immutable snapshots that must be re-issued with a new identifier every time the data change, Constellation offers mutable databases that can evolve continuously as new observations arrive, much like a shared spreadsheet. That flexibility matters for ecological citizen science, where projects grow and shift over seasons and years rather than producing a single fixed dataset.

The core problem the authors confront is conceptual. In the centralised server–client model that dominates today’s internet, a single server holds the authoritative copy of the data, verifies users’ identities, and mediates every exchange. Distributed systems abandon all of that. There is no single source of truth: every copy of the data on any user’s device is an equally valid source that can be shared with others. There is no guaranteed, unique system state at any given moment; instead, the system relies on eventual consistency, meaning that devices which update data in parallel while disconnected will automatically merge their changes once reconnected, converging on a shared state over time. Data are retrieved not by location-based URLs but through content-based addressing, in which a unique cryptographic hash identifies the desired content itself and can be served by any peer holding a copy.

Each of these differences carries direct consequences for interface design. In Constellation, users can “pin” data from other contributors to their own devices, guaranteeing its availability even if the original creator disappears. The interface therefore replaces the simple uploaded-or-not dichotomy of centralised platforms with a continuous gradient of availability, communicated through icons showing whether a database is pinned on the current account, pinned on the device, or not pinned at all. Contributors, in turn, want to know how many peers have pinned their data, a measure of both its safety and its usefulness to the community. The authors argue that such indicators should be subtle and visual rather than textual, sparing users long explanations of how peer-to-peer networking works.

Authentication changes just as radically. Without a central authority, users verify one another’s identities through key-pair cryptography: each user’s device generates two mathematically linked numbers, a public key that serves as an account identifier and a private key that never leaves the device and cryptographically signs every message. This eliminates passwords, registration, and the risk of forgotten credentials, but it introduces a new danger: if a device is lost or wiped, the account can be irrecoverably gone. The team’s first version of Constellation opened directly onto the user’s dashboard, ready to work, only for early testers to find the absence of a familiar login process disorienting. The interface was reworked to include a guided first-login flow for choosing a display name and profile photo, and the app now sends periodic reminders encouraging users to link a second device or back up their credentials.

Even the humble web link gets a redesign. Content-based addresses such as cryptographic hashes are visually intimidating to non-experts, so Constellation hides them behind human-readable database names, revealing the full identifier only when a user clicks a small link icon, much as conventional websites hide URLs behind buttons. This follows design guidelines drawn from user studies of distributed mobile applications, which found that users overwhelmingly prefer distributed software to look and behave like the centralised alternatives they already know, with peer-to-peer specifics surfacing only when unavoidable or when they offer genuinely new capabilities, such as connecting to peers without internet access.

The architecture also reshapes how projects are structured. Rather than a single central database, a Constellation citizen science project is a swarm of identically formatted individual databases, one per user, visually combined into a single dataset. Each user writes only to their own database, which means a malicious contributor can be blocked without polluting the entire project’s history, and data consistency conflicts between users largely disappear. Searching proceeds concentrically: a query first goes to the requester’s immediate contacts, then recursively to their contacts, with results appearing as a ranked list that expands through the network as the user scrolls. Trust levels between users, displayed as icons, rise incrementally through co-authorship and interactions with each other’s data.

To reach the two very different audiences such platforms must serve, the team split Constellation into an academic-facing interface, built on OrbitDB, the InterPlanetary File System, and the libp2p networking library, and a one-click generator that produces stand-alone data-entry apps for citizen scientists once researchers have defined their project’s variables and data structures. Academics can deploy a working, project-specific app with minimal or no coding, then customise the generated code if they wish. Media files are stored on IPFS with only their addresses recorded in the database, keeping local storage manageable, while the GossipSub protocol propagates updates efficiently across networks of peers that are not all directly connected.

The authors’ central lesson is that simplicity beats transparency. Drawing a parallel with Bayesian statistics, they note that the OpenBUGS software made a powerful but notoriously difficult method accessible, only to be superseded by the far more ergonomic PyMC and RStan, suggesting that peer-to-peer databases today sit where Bayesian inference did before user-friendly tooling arrived. With polished centralised alternatives like Google Sheets and KoboToolBox competing for users’ attention, distributed platforms must match their ease of use while offering concrete advantages: lower costs, no server setup, local-first data access, and genuine data sovereignty for communities. Users, the study concludes, care little whether a system is centralised or distributed; they care whether it works.

The research carries limitations the authors acknowledge candidly: their workshops involved between one and three dozen concurrent users, and larger deployments will likely demand further refinements, particularly in communicating network connectivity and data availability. Formal user-type analysis, such as the Hexad gamification scales, could sharpen future design guidance. But the blueprint they offer, mimic centralised systems, abstract away the cryptography, surface peer-to-peer features only when they add real value, may determine whether distributed databases escape their niche and become the resilient, community-owned backbone that long-term ecological citizen science has been waiting for.

Subject of Research: User interface design for peer-to-peer distributed databases in ecological citizen science

Article Title: User interface design principles for peer-to-peer distributed databases for ecological citizen science projects

Article References: Malard-Adam, J. J., Medema, W., Anandaraja, N., Harms, J., Dipple, J., Sheeja, & Jaisridhar, P. (2025). User interface design principles for peer-to-peer distributed databases for ecological citizen science projects. Web Ecology, 25(2), 201-212. https://doi.org/10.5194/we-25-201-2025

Image Credits: AI Generated

DOI: 10.5194/we-25-201-2025

Keywords: citizen science, peer-to-peer databases, distributed systems, user interface design, ecology, data sovereignty, Constellation, IPFS, eventual consistency, key-pair authentication, biodiversity monitoring, open-source software