Where Elegant Paper is heading after 2.0. Intentions organized by horizon — not promises.
See what is already in 2.0Read first
A conservative roadmap: intentions, not promises. No dates. The order changes with your feedback — and nothing here is in 2.0.
The release is available on the Microsoft Store. We are now watching the first feedback to prioritize the next improvements.
Dragging black boxes over the thumbnail and flattening the redacted sheets, so the redaction is irreversible rather than a black rectangle sitting on top of readable text — the failure that ends up in the newspapers. It is the one PDF job nobody sensible uploads to a server, which is exactly why it is our next big one. It missed 2.0 because a rushed redaction is a leaked redaction, and that is the failure you do not get to apologise for.
A blank sheet (or one with a keyword) closing one document and opening the next, with the number of sheets found shown BEFORE anything happens — like everything else in the app. Today the scissors between thumbnails are manual, and for an office’s weekly stack that is not enough.
Sending a hundred documents to the desk at once hits the memory ceilings that keep the app safe. 2.0 made the heavy work far faster, but the ceilings are where they were: we want to raise them without giving up on having one — working as a stream instead of loading everything at once.
Remembering your device’s choices (resolution, colour, duplex, feeder) so you do not reconfigure them for every stack of paper.
Paper already reads the text in your scan. The idea is to hand it to its sibling so that its search finds things inside a PDF instantly, with no deep scan. It only makes sense with both halves ready at once — half of it is a declared, empty folder, and we do not ship that.A suite job, not a Paper one.
The windowless mode does OCR and compression today. Running a whole recipe from the command line is the step that makes the scanner folder sort itself out — and it deserves to be born alongside the sibling automation that will call it.A door with no bell does not open by itself.
The recognition engine is the Windows one: the languages you see are the ones you have installed. We want to follow what Microsoft offers and make installing them easier from inside the app.Depends on Windows, not on us.
Receiving files through the Windows Share menu requires a foundation change in how the app is packaged. It is under evaluation, together with the same step in Elegant File Explorer.No timeline.
Elegant