A Libby desktop app: library loans on a Mac without the phone

A search for a Libby desktop app usually starts with a small annoyance rather than a technical question. A hold came through, the phone is charging in another room, and reading a borrowed ebook on a laptop should not require hunting through a browser window with eighteen tabs in it. The results that come back are a mix of catalogue sites offering something called Libby for Mac, forum threads where someone discovers the website, and OverDrive's own help pages, which are the only ones worth reading closely. Those pages answer the question directly, and the answer changes what the next step should be.

What OverDrive publishes, and where a Mac fits

OverDrive's help documentation lists the platforms it ships an installable app for, and the list is short.

If you have a Windows computer, Mac computer, or a Chromebook, you can use Libby in your web browser at libbyapp.com. We suggest using the latest version of Chrome, Safari, Firefox, or Edge. Source: help.libbyapp.com

The installable versions named on the same page are iOS 10 and later, Android 7.1 and later, and newer Fire tablets. There is no macOS build, and the browser is not presented as a fallback for people who could not find the download. It is the supported route for every desktop operating system, which means the website is the product on a Mac rather than a reduced version of it.

The rest of that documentation is worth knowing because it removes a common worry. The app is free to install, every title borrowed through it is free with a valid library card, and there are no subscription costs, no in-app purchases and no late fees, because digital loans return themselves on their due date. A browser window does not change any of that. Nothing about reaching the service through libbyapp.com instead of an icon costs money or limits a collection.

What the catalogue sites are offering, then, is not an official application. It is a wrapper that someone else built around the same website, packaged and listed as though it were a download from OverDrive. That is a legitimate category of software, but it is worth understanding it for what it is: a window around a site, made by a third party, on a release schedule nobody in particular controls.

Why a browser tab is a poor container for a reading app

Reading is a long-dwell activity in a browser built for short visits, and the friction shows up in specific places rather than as a general feeling.

The first is vertical space. Libby's own interface already carries navigation in a footer, with Search, Library, Menu, Shelf and Tags sitting along the bottom of the screen. Above that sits a browser's tab strip, its address bar and often a bookmark bar. Two sets of application furniture wrap the same page, and the part that loses the space is the column of text. On a 13 inch laptop that is the difference between a comfortable page and one that needs scrolling every few seconds.

The second is the accidental close. Cmd+W is muscle memory for clearing a tab, and it does not care that the tab in question is a half-finished chapter. The position is recoverable, since progress syncs to the account, but the interruption is not free, and it repeats.

The third is that a Shelf is checked on a rhythm rather than on demand. Holds arrive without warning, due dates approach, and a magazine issue lands on a schedule. That is a page somebody wants to glance at daily, and a daily glance through a window holding twenty work tabs means finding a favicon first. The number of steps between wanting to check and having checked is the thing that decides whether the checking actually happens.

The fourth is context. A browser window at work holds the things being worked on. Opening a novel in it puts a leisure activity inside the same frame as everything else, and the two compete for the same window and the same attention.

The two free routes on macOS

Before installing anything at all, macOS and its browsers already offer a way to put a site in its own window. Both are free, both take under a minute, and both land on an engine OverDrive names as supported.

Route	Where it comes from	What it produces
Add to Dock	Safari, File menu	An icon in the Dock and in Spotlight, a simplified toolbar, the signed in state usually carried over
Install page as app	Chrome or Edge, browser menu	A window with no tab strip, its own Dock icon, and browser level features such as notifications

Apple documents Add to Dock as turning a website into an app with its own icon and a stripped down toolbar. Google documents the Chromium equivalent in its web apps help page, reached through Install page as app, and notes that installed web apps can gain notifications and offline storage.

One detail is worth getting right at this stage. The window should be built while the useful page is on screen, not from the home address, because the address in the bar is what the window remembers. Somebody who checks holds and due dates every morning wants the window to open on the Shelf rather than on a library landing page. That saves two taps every single day, which over a year is the entire value of the exercise.

For one reader with one set of library cards, this is the whole answer. Either route produces an icon that opens the reading interface in a clean window, and nothing further needs buying or installing.

Where the free routes stop, and where they do not

It is worth being precise here, because the usual argument for a per-app tool does not apply to this service in the way it applies to most.

Libby handles multiple library cards inside one session by design. Cards are added and switched from the Menu, and the Shelf shows loans, holds and magazines from all of the libraries attached to the account at once. Anyone with a city card, a county card and a card from a university system does not need three windows. One window covers them, and building three would make the situation worse rather than better.

The real limit is people, not cards. A Safari web app inherits Safari's session and a Chromium web app inherits the profile it was installed from, so two windows built that way hold the same sign in. On a Mac shared by a household, that means one person's Shelf, one person's tags and one person's reading position, no matter which icon gets clicked. Two readers on one machine who do not want to share a macOS user account are stuck.

This is where a tool that turns a website into a standalone Mac app has something to offer, because the useful ones give each generated app its own isolated storage. Two icons, two cards, two Shelves, with no switching and nothing to log out of. The features page sets out which controls tend to be exposed per app, and the supported services list shows which sites arrive already configured. The cost is one sign in per app on first launch, since a fresh profile starts with no cookies.

The other case: reading and everything else

A second, quieter reason to want more than one window has nothing to do with sharing. Somebody who reads professionally, checking out reference titles for work alongside novels for the evening, gets value from two windows on the same service for the same reason people keep separate bookshelves. One opens on the Shelf, one opens on a tag. The service supports tags natively, so the split can live inside a single account and simply be pointed at from two different starting addresses.

What a reading window should be set to

A window built for reading wants different settings from a window built for work, and most of them are decided once.

Size comes first. A reading window does not want to be maximised, because a full width line of text on a wide display is uncomfortable to read. It wants to be roughly the width of a page, and macOS remembers the size a window was last left at, so this is a one time adjustment rather than a habit.

Placement comes second. A dedicated application can be dropped into its own macOS space, which turns switching to it into a swipe rather than a search. That matters more for reading than for most activities, because the point is to leave whatever else was on screen behind rather than to sit next to it.

Notifications are the one setting worth turning down rather than up. A Chromium based window can carry a notification permission, which is useful for a dashboard and counterproductive for a book. The same applies to the badge on the Dock icon.

Finally there is the engine. A Chromium based window renders the site the way Chrome does, and a Safari based web app renders it the way Safari does. Both are on OverDrive's supported list, so this is a question of preference rather than compatibility, but it is worth knowing that the choice exists where a tool exposes it per app.

Magazines change the calculation

Magazines are worth treating as a separate case, for a reason that has nothing to do with layout. OverDrive's documentation on borrowing limits states that ebook and audiobook loans count toward the limit, but magazines and Extras do not. That makes magazines the one part of the collection with no queue pressure and no reason to ration, so for anyone who reads them the Shelf is consulted more often rather than less.

The practical effect on a window is about size. A window sized comfortably for a column of novel text is not the same window that suits a magazine page, and the size macOS remembers is whichever was set last. Anyone who reads both regularly has a real case for two windows on the same account, one opening on the Shelf at reading width and one kept wider, which is the kind of split that per app settings exist to handle.

What a separate window does not change

A window is presentation. It leaves the service underneath exactly as it was, and being clear about the boundary saves disappointment later.

Borrowing limits are unchanged. How many titles can be out at once, and how many holds can be placed, are set by each library and shown on the card in Menu. No window alters them.

The catalogue is unchanged. Each library chooses which titles and formats to offer, so two people with different cards see different collections, and a wait for a popular title is a queue rather than a technical problem.

Availability is unchanged. A hold arrives when it arrives.

Kindle delivery still depends on the library. At US libraries most ebooks show an option to send the title to a Kindle rather than reading in Libby, and that option belongs to the library and the title rather than to the container the site runs in.

Offline behaviour deserves care rather than a promise. OverDrive's documentation describes automatic download of loans over Wi-Fi as a default of the mobile app, and the desktop route it names is the browser. Anyone whose main requirement is reading on a plane should test that specific case before rearranging anything else.

What to change first

Open the Shelf in Safari, use Add to Dock while that page is on screen, and give the icon a week of ordinary use. If the only thing still wrong at the end of that week is that two people share the Mac and cannot share a Shelf, a tool such as Kagemusha can produce separate applications with separate storage so each reader gets an icon of their own.