Changelog

Files live with their work

File management, part 1 of 2

A plan is rarely just a list of tasks. There is the PDF the task is about, the screenshot that explains the bug, the spreadsheet the project keeps coming back to. Until today those lived somewhere else — a downloads folder, an email — and Projectifier only knew the task. Now a file is a thing Projectifier holds, next to the work it belongs to.

What’s new

Attach files to a task. Open a task and you’ll find an Attachments section beside its notes and subtasks. Add a file from your computer and it uploads right there, with a progress bar while it goes. Click it to open it; images and PDFs open in a tab, everything else downloads with its original name.

Files in projects and areas. Every project and area page has a Files section for the documents that belong to the whole thing rather than one task.

Drop it in the inbox. Drag a file onto the inbox and it lands there like any other capture — unfiled, waiting to be assigned to a project or area when you get to it. A file is a thought you haven’t placed yet, too.

Remove it, and it’s gone. Deleting a file removes it from your account. Deleting a task, project or area takes its files with it.

How much you can keep

The quota is a number of files, not a number of gigabytes — it’s easier to read on a pricing page and in the meter on your settings page.

  • Free: 20 files
  • Adaptive: 50 files
  • Private: unlimited files

Any single file can be up to 100 MiB. Your settings page shows how many you’ve used — 14 of 20 files — and where to go when you need more.

How it works, briefly

Your files never pass through Projectifier’s servers. When you add one, the app asks its storage bucket for a short-lived, signed address and your browser uploads straight to it; when you open one, you’re handed another short-lived address to read from. The bucket is private and encrypted with a key Projectifier manages, and the addresses expire within minutes. Projectifier keeps the record — what the file is, where it lives, who owns it — and the bucket keeps the bytes.