Joplin 3.0 treated deletion and mobile plugins as note-system design

A note app adds a missing end state

On 1 July 2024, Joplin published its 3.0 release note. The headline additions were practical rather than theatrical: a trash folder for deleted notes and notebooks, multi-factor authentication for Joplin Cloud and applications, multiple columns in the desktop note list, and beta plugin support on mobile. The trash feature is the most revealing. A note-taking tool optimised only for capture has an obvious gap when deletion is either instant and frightening or so inconvenient that people keep everything. A recoverable middle state changes the rules for pruning an archive.

Deletion policy is part of organisation

Joplin says items moved to the trash can be permanently deleted after a chosen number of days. That makes retention a configurable policy rather than an accidental side effect of pressing Delete. It does not make deletion harmless. A user still needs to distinguish a note that is obsolete from one that records a decision, and a team still needs a rule for shared material. But the release shows why file-management behaviour belongs in a productivity discussion: an archive that can never be cleaned becomes harder to search; an archive that can be cleaned only by irreversible action encourages hoarding.

More surfaces also mean more dependencies

The release brought a multi-column list that can display and sort note properties, with plugins able to customise columns, and beta mobile plugin support. That opens a path to make a personal system more tailored across devices. Joplin labels the mobile support beta and notes that some plugins may not work or work only partly. Its current release-cycle page, retrieved 19 September 2026, records 3.0’s publishing window as 1–7 July 2024, while the separate synchronisation documentation explains that data can be synchronised through several supported targets. These are useful first-party records, not proof that any particular plug-in, storage target or conflict pattern is safe for a given collection.

Questions before expanding a personal knowledge system

• What is the retention period for deleted notes, and does it match the value and sensitivity of the material?
• Which plugins are essential, and do they work on every device where the notes must be usable?
• Can a full export and a restore be tested before relying on sync as the only copy?

Joplin 3.0’s productivity lesson is that a note system needs governed endings as well as easy beginnings. Capture, columns and plugins may make an archive more capable. Trash, authentication, exports and tested recovery are what make that capability less likely to become a long-term liability. The practical discipline is simple: rehearse deletion, restore and cross-device access with non-critical material before the archive contains the work that cannot be reconstructed. That small rehearsal also reveals whether the chosen retention window is practical rather than merely reassuring.