Dropover: how to decide what you need

Most people arrive at Dropover already convinced that a shelf would help, and then stall on a different question: which version, which settings, and whether the paid tier is warranted. That question cannot be answered from a feature list, because a shelf app is not one product. It is a transport tool, a file action runner, an upload client, and a folder watcher, bundled together. Deciding well means working out which of those four is actually being bought, and then checking the handful of constraints that can rule the whole category out regardless of how good the shelf is.

Start by counting stalled drags, not features

The only measurement that predicts whether a shelf is worth installing is how often a drag cannot be completed in one motion. That happens when the destination is on another Space, behind a full screen application, inside a collapsed window, or several folder levels away from what is currently visible.

A week of normal work gives a usable number. Under five occurrences, the problem is real but small, and the free path covers it: copy with Command C in Finder and press Option Command V at the destination, which moves the file instead of copying it. Between five and twenty, a shelf pays for itself in attention rather than seconds, because a stalled drag interrupts a train of thought rather than merely costing time. Above twenty, the shelf becomes part of the daily routine and every other axis below starts to matter.

Counting also exposes the case where a shelf is the wrong purchase. If the files in question are already saved and the difficulty is locating them later, nothing about a shelf helps, because shelves act during transport. That is a search and naming problem, and buying a shelf to solve it produces an app that gets opened twice and then ignored.

The trigger decides whether the app gets used

Every shelf app has to be summoned, and the summoning method is the single setting that determines whether the habit forms. Dropover opens a shelf when the pointer is shaken, and it can also be opened with a customisable keyboard shortcut, by dropping files on the menu bar icon, or by dropping them onto the notch on hardware that has one. Shake sensitivity can be tuned, and the gesture can be disabled for specific applications.

Those options are not interchangeable in practice. A shake is discovered by accident and needs no memorisation, which suits occasional use, but it also fires when nothing was intended and it requires the pointer to already be in motion with files held. A keyboard shortcut never fires accidentally and works before a drag begins, which suits heavy use, but it has to be remembered for a week before it becomes automatic. The menu bar target works reliably for files coming out of an application that does not drag well.

Choosing one and turning the others off is better than keeping all of them. Multiple triggers mean multiple shelves appearing in different places, which is the most common reason a shelf ends up containing files nobody remembers putting there. The app exclusion list matters here too: any application where dragging is itself part of the interface, such as a video editor, belongs on that list.

Transport only, or actions as well

The second axis is whether files need anything done to them on the way. Dropover can share shelf items through Mail, Messages, AirDrop, or any destination in the macOS Share menu, and it includes built in actions such as resizing images, extracting text, and creating ZIP archives. Instant Actions run a task the moment files are dropped on them, with no further clicks.

This axis splits cleanly by job. Someone assembling attachments for an email needs transport and sharing, and every shelf app delivers that. Someone who resizes screenshots before sending them, or zips a folder several times a day, is buying an action runner that happens to have a shelf attached. The distinction matters because action runners are compared on which actions exist and how easily new ones can be defined, not on how the shelf behaves.

A practical test before deciding: list the operations performed on files immediately after moving them. If that list is empty, the built in actions are a bonus that will not be missed if they are absent. If it has three entries that repeat weekly, those three entries are the actual requirement, and a shelf without them is the wrong purchase even if its shelf is better.

Uploads and links are a separate purchase decision

The third axis is whether files leave the machine. Dropover Cloud uploads from the shelf and returns a public link, requires no registration, is free, and lets an upload carry a title, a password, a custom expiration date, or a different link type. Shared pages carry no branding, tracking, or ads, and uploads can be viewed or deleted later from the menu bar or Preferences. Seven services are supported in total: Dropover Cloud, iCloud Drive, Dropbox, Microsoft OneDrive, Google Drive, AWS S3 and S3 compatible providers, and Imgur.

One behaviour is worth stating plainly because it is often assumed wrongly. Dragging files onto a shelf does not upload them. The shelf holds a reference, and an upload happens only when an upload or sharing action is chosen explicitly.

The decision here depends on who receives the link. For links sent outside an organisation, expiry and password matter, and so does the ability to delete an upload afterwards. For links that circulate internally, a shared folder in storage the organisation already pays for is usually simpler, and the shelf becomes unnecessary for that job. For anyone who pastes links into chat all day, this axis outweighs the shelf itself, and the service list is what to compare.

Automation is the axis that is hardest to substitute

The fourth axis is whether shelves should appear without being asked for. Folder monitoring can watch a location such as Downloads and show a shelf automatically when new files arrive, and shelves can be created for new screenshots. Custom scripts can run through AppleScript, Automator, or UNIX tools, custom actions can be built for repetitive tasks, and Siri Shortcuts can add, upload, or access files. Alfred and Raycast extensions exist for people who already live in a launcher.

This is where the built in tools stop being equivalent. The Shortcuts app can react to an item being added to a folder, but it runs a process rather than presenting the arrivals for a human to look at and choose from. That difference is the entire value of an automatic shelf: it is a staging area for a decision, not a rule that acts on its own.

Deciding this axis takes one question. Are there folders where files arrive on someone else's schedule, such as downloads, exports from a camera, or a synced folder shared with colleagues? If yes, automatic shelves are the feature to weigh most heavily. If everything arrives because it was saved deliberately, monitoring will be switched on during setup and forgotten.

Constraints that can rule the category out

Four facts about how Dropover is sold and supported can settle the decision before any feature is considered.

It is distributed exclusively through the Mac App Store, with no direct download. It requires macOS 13.0 or later, according to the App Store listing for version 5.3.1. It ships in four interface languages: English, German, Dutch, and Simplified Chinese, following the system language by default. And business licence seats are not available at present, described as planned, although purchases restore across machines signed into the same iCloud account.

Any one of those can be decisive. A Mac managed by an organisation that does not permit App Store installations cannot run it at all. A Mac still on macOS 12 cannot either. A team that needs one invoice covering eight people has no supported path today. And a workplace that requires interface text in a language outside those four will not get it from settings.

Axis	What decides it
Stalled drags per week	under five, no purchase needed
Trigger	shake for occasional use, shortcut for daily use
Actions on files	list what happens right after a move
Uploads	who receives the link, and does it expire
Automatic shelves	do files arrive on someone else's schedule
Licensing	App Store only, macOS 13.0, four languages, no team seats

How to use the trial as an actual test

The trial runs 14 days with every feature enabled, and when it ends the app keeps working with a 3 second wait before the shelf can be interacted with. Removing that wait is a one time in app purchase rather than a subscription, and nothing is charged automatically when the trial expires. That structure allows a real test instead of a rushed one.

A trial that answers the question looks like this. For the first three days, change nothing except the trigger, and use only transport. Keep a note of how many times a shelf was opened. On day four, turn on folder monitoring for exactly one folder, and see whether the automatic shelves get used or dismissed. Around day eight, try the two or three actions identified earlier, and check whether they replace what is currently done by hand. Leave uploads for last, because they are the easiest feature to be impressed by and the least often needed.

What that sequence produces is a count and three yes or no answers, which is enough to decide. The alternative approach, switching everything on during the first hour, produces an impression rather than evidence, and impressions expire faster than trials do.

Settings that are worth deciding once, not adjusting later

Two behaviours sit beneath every axis above, and getting them wrong produces problems that look like bugs.

The first is whether items leave the shelf as moves or as copies. Dragging an item off a shelf moves it by default, holding Option copies it instead, and anything destined for a different volume or disk is copied by default unless Command forces a move. A preference exists to copy by default in every case. Deciding this deliberately matters because the two mistakes are not symmetrical: an unintended copy leaves a duplicate that gets noticed eventually, while an unintended move leaves a file missing from where a colleague or a script expects it.

The second is how long shelves persist. Shelves can be pinned to stay available, given custom titles, docked at the edge of the screen and pulled back when needed, and up to 10 recently closed shelves can be reopened. All of that is useful and all of it encourages shelves to accumulate. A shelf holding files for three weeks is no longer a staging area, it is an undocumented folder whose contents exist only as references, and the files it points at may already have moved.

A workable rule is one unpinned shelf for transport, plus at most two pinned shelves that have names describing an active task. When a third pinned shelf seems necessary, the files in question probably belong in a real folder instead. That single limit prevents most of the confusion people report after a few months of use.

What to change first

Count stalled drags for a week before installing anything, then choose one trigger and leave the others off. If the count is low and nothing needs doing to the files in transit, the built in move on paste behaviour and the Share menu already cover the job at no cost.

If the counting reveals that most interruptions come from switching between a file browser and a separate terminal rather than from moving files, no shelf reaches that. What Atriens keeps in a single window is listed on the Features page, and the Pricing page states the cost.