II.1 The universal flow: Upload → Options → Run → Result
One rhythm for fifty apps
Open any Documentize app and you will see the same four moments:
flowchart LR U[1. Upload] --> O[2. Options] O --> R[3. Run] R --> S[4. Result] S -.next app.-> U
Merger, Compressor, Ask PDF, Page SEO Checker: the details differ, the rhythm does not. Once you have it in your fingers, a new app is a two-minute lesson.
Anatomy of an app page
+-------------------------------------------+
| App name and one-line promise |
+-------------------------------------------+
| [ Drop files ] or [ Choose file ] | <- upload zone
| |
| Show all settings v | <- options panel
| Mode / level / language / password |
| |
| [ RUN BUTTON ] | <- named for the action
+-------------------------------------------+
| Progress ... Work is done! | <- result panel
| [ Download ] [ Delete files ] [again] |
+-------------------------------------------+
| How it works | FAQ |
+-------------------------------------------+
The labels in this sketch come from the shared interface texts: "Drop files", "Or choose file on computer", "Show all settings" / "Hide all settings", "Work is done!", "Download", "Delete files". Individual apps name their run button after the action (MERGE, COMPRESS, Recognize).
1. Upload
You can bring files in several ways. The shared "How it works" text says you can select files from the file system, Dropbox and Google Drive. Beyond that:
- Drag and drop onto the zone, or use the file picker.
- Several files at once where the app expects them (Merger, Compressor). Others, such as Sign or Protector, take a batch too; a few take exactly one document (Recovery handles one file per run).
- A link instead of a file. The shared message about oversize files says you can enter a URL from Google Drive, Dropbox or the public web to get past the direct-upload size limit. Some apps take only a URL (Page SEO Checker takes a page or sitemap address), and Chat can read a few public web links.
- Not a file at all. Some apps start from a sentence (SVG Maker, Chat), a GitHub repository (Part XI) or a typed question.
The page checks your files right after upload. You may see messages such as "Files that did not pass the check for their extension", "Files that did not pass the size check", "An empty file is detected" or "The number of files can be up to N". Those are the page protecting you from a failed run; see Limits.
If the file is protected, some apps ask for a Document password first. Others cannot accept encrypted input at all and tell you to unlock it first (Unlock).
2. Options
Hidden by default behind Show all settings. This is deliberate: the default must do the right thing for the common case, so you can press the button immediately. Open the panel when you need something else: a compression level, page size, language, a password. II.3 explains how to think about options.
3. Run
Pressing the run button starts a task: your files and options are sent to a server queue, a worker picks the job up, and a progress indicator appears. The panel can show messages such as "N / M pages of the document have been processed".
Three things can happen while you wait:
| Situation | What you see |
|---|---|
| Normal | A progress bar, then "Work is done!". The how-to text says to expect from 10 seconds to several minutes depending on file count and size |
| Busy server | A queue notice: your task is queued and the exact wait is unknown. You may leave an email address and get a link when it is ready ("Send result to:") |
| Long job | A note that this looks long and the result can be emailed; you can also come back later while the result is still kept |
You do not have to keep the page open for ever, but do not rely on it either: use the email option when it is offered.
4. Result
The result panel offers the essentials:
- Download. One file, or several files in a ZIP (for example Compressor names its bundle Compressed_documents).
- A summary where the app has numbers to report, such as original size, new size and percentage saved.
- Delete files. Removes your task's files from the server at once, instead of waiting for automatic removal (Privacy).
- Run again or start with another file. Many apps show a button such as "Merge again" or "Compress again".
Other things the result may include depend on the app: an on-screen verdict (Verify Signature), a report (PDF/A Validator, Recovery), a highlighted copy (Search), a linked wiki (PDF Knowledge Base).
The book does not claim preview thumbnails, a share link or one-click "open in another app" for every app. Where an app offers such a thing, its chapter says so.
Chaining: the loop closes
The result of one app is the upload of the next. In the browser this means download, then drop into the next page. In the CLI, MCP and API channels, the same chain can be scripted; see Beyond the browser. The rules for good order are in Part III.
Common stumbles
- "Nothing happens after I drop the file." Many apps wait for the run button. Check whether options are required (a password, a certificate, a range).
- "It says the file is too big." Use the URL route if offered, split the file (Splitter), or see Limits.
- "I closed the tab." Results are kept for a short time; see Privacy.