Why does Flick ask to move to Applications?

You opened Flick from a place it can't update itself in: the disk image, or a temporary copy macOS runs because the download was never moved. Choose Move to Applications and Flick copies itself into your Applications folder, opens that copy and quits.

The question reads Move Flick to Applications? with two buttons, Move to Applications and Not Now. Flick asks only once, the first time it runs from one of these places. It notes that it asked before it shows the question, so it never asks again, whatever you choose. The simplest way to avoid it is the usual one: drag Flick into Applications from the disk image's window before you open it, as the installation guide shows.

What Move to Applications does

  1. Copies itself into Applications

    The copy is always named Flick.app, whatever the original is called, so “Flick 2.app” from your Downloads folder still replaces an older Flick there instead of landing beside it. Flick finishes the copy before it puts it in place, so a failed copy never leaves a half-written app in Applications.

  2. Prepares the copy to update itself

    You've already approved this download, so Flick clears the download's quarantine flag on its copy. That lets the copy run straight from Applications, where it can install updates.

  3. Opens the copy and quits

    The copy in Applications opens a moment after this one quits, so the two never run at the same time. The original stays where it was: eject the disk image, or delete the download, whenever you like.

If you choose Not Now

Flick starts normally from where it is, and doesn't ask again. It works, with two catches:

  • From the disk image, Flick keeps working only while the disk image stays open.
  • From either place, Flick can't install updates.

You can fix both later by moving it yourself.

Replacing an older copy

If your Applications folder already holds an app named Flick.app, what happens depends on which one it is. Whatever is replaced goes to the Trash, never straight to deletion, so you can put it back.

In ApplicationsWhat happens
An older Flick, or the same versionIt goes to the Trash and the new copy takes its place, with no further question.
A newer FlickFlick asks Replace the newer Flick? and names both versions. Keep It leaves it alone; Replace moves it to the Trash.
A Flick whose version can't be comparedFlick asks Replace the Flick in Applications? before doing anything. If the app's details can't be read at all, Flick treats it as a different app (next row).
A different app named Flick.appFlick asks Replace the other Flick.app in Applications? The other app goes to the Trash only if you choose Replace.
A Flick that's runningNothing is replaced. Flick says Flick is already open from Applications: quit that copy, then drag the new one into Applications in Finder.

If you choose Keep It, this copy keeps running from where it is, just as with Not Now.

Why it matters for updates

When you install an update, Flick downloads the new version, checks its signature, replaces the app where it is and opens again. A disk image can't be written to, and the temporary copy macOS runs a download from isn't a place Flick can replace either, so updates only work once Flick lives in a normal folder such as Applications. Your settings, Accessibility permission and license carry over to each update. More about how Flick updates.

Move it yourself

  1. Quit Flick

    Click Flick's icon in the menu bar and choose Quit.

  2. Drag it into Applications

    In Finder, drag Flick from the disk image's window, or from your Downloads folder, into the Applications folder. If Finder says an item with that name already exists, choose Replace. Lost the disk image? Download Flick again.

  3. Open it from Applications

    If macOS asks you to approve Flick again, do it the same way as the first time: how Open Anyway works.

  4. Check that windows show up

    macOS can show Flick as allowed in Accessibility while the permission still belongs to the old copy. If ⌥Tab shows no windows, remove Flick from the list and add it again.

Couldn't move Flick to ApplicationsIf the copy fails, Flick says so with the reason and removes its unfinished copy. Drag Flick into Applications in Finder instead, as above. If the copy worked but Flick couldn't open it, you see Flick is in Applications now and Finder shows the copy: quit this one, then open Flick from Applications.

Questions

I chose Not Now. Can I get the question back?

No, Flick asks only once. Moving it yourself is four short steps: see Move it yourself.

Does moving Flick change my settings or license?

No. Your settings and license file are stored in your user Library, not inside the app, so the copy in Applications picks them up as they are. Moving uses no extra license seat.

I keep my apps on an external drive. Why does Flick ask?

Flick treats any app opened from another volume like one opened from a disk image, so it offers the move once, and the message mentions a disk image. Choose Not Now to leave it there; it won't ask again.

Still stuck?Email [email protected] with your macOS version, your Mac and what you've tried, or visit the Support page.

Install once. Stay current.

From Applications, Flick tells you when a new version is ready and installs it when you say so.

The free version never expires and switches between your 5 most recent windows. A one-time license, from $9.49, unlocks every window and browser tabs.