Roadmap & non-goals
Orifold is in beta on the road to 1.0. Direction over dates — the list below is intent, not a schedule. The paper isn’t done folding.
Orifold is built part-time, so the order may shuffle and a fold or two may take the scenic route. The direction holds steady, though: more useful, more polished, more delightful — one crease at a time. Softly stated on purpose — “on the radar,” never “shipping Tuesday.”
🛠️ Now — on the bench
Section titled “🛠️ Now — on the bench”Steadying what already ships — signing, the qpdf engine, the companions, localization, and the documentation you’re reading. v0.11.0 hardens text/object edit composition and adds preservation-first OCR receipts; the workbench remains focused on widening the PDFs those guarded editing paths can handle safely.
Move the furniture is live as of v0.8.8. Pick the Select tool, click a real graphic on the page — an image, a logo, a line, a shape — then move, resize, layer, or delete it. Edits go into the file’s actual content (no ghosts, no leftover copies), compose with inline text edits, and survive save, reopen, and export with full undo/redo. v0.10.0 adds restyling for existing solid fill, stroke, and line-width channels on compatible vector paths. Still growing: duplicate, multi-select, adding a missing paint channel, gradients, and rotated-page support. See Move & edit objects.
🔭 Next — in the lab
Section titled “🔭 Next — in the lab”Being explored, high on the radar. Each is grounded in machinery Orifold already links — not a wish list.
✂️ Real redaction
Secrets that actually leave the file — not a polite black rectangle you can drag right off. Building on the same qpdf pass that already strips scripts and hidden metadata.
Batch folder processing and side-by-side PDF comparison have moved out of this roadmap and into the app. See Fold a folder and Compare drafts.
🌫️ Later — quietly brewing
Section titled “🌫️ Later — quietly brewing”- Automated UI smoke tests to complement the unit suite.
- Broader OCR language coverage and export polish, as real use surfaces needs.
🚫 Non-goals
Section titled “🚫 Non-goals”Being explicit about scope is part of the trust. Orifold is not planning to add:
- Cloud sync or accounts. The local-only boundary is the product, not a limitation to fix.
- Telemetry or analytics. There’s no server to send it to, and there won’t be.
- Real-time collaborative review or co-editing. That requires a cloud Orifold won’t build.
- Windows or iPad versions. It’s a native macOS app; a rewrite for other platforms isn’t planned.
A non-goal isn’t a “no forever” so much as a “not without changing what Orifold is.” If a feature would require a server or an account, it’s out of scope by design.