Biblio

The audiobook player that stops when the screen goes dark

Open an audiobook in Biblio, press play, and turn off your screen. Fifty seconds later, the audio stops. This is not a battery-saving feature. It is a bug that has persisted across multiple versions, and it forces users to keep their screens on or constantly wake the device just to finish a chapter. The official help center does not list this as a known issue, but user forums are full of workarounds involving changing system-level battery settings. For a library app that competes with Libby and BookBites, this is a glaring weakness. The audiobook player itself has the expected tools: speed control from 0.5x to 2.0x, 15-second skip buttons, a sleep timer, and casting support. But none of that matters if the playback stops every time the device locks. The sleep timer is supposed to stop playback after a set time. Instead, the screen-off behavior stops it immediately. This is not a feature; it is a failure in how the app handles background audio.

Biblio's text-to-speech function, on the other hand, works differently. It reads e-books aloud using the device's built-in TTS engine, and it can read anything from a single word to an entire page. The user can adjust the voice and speed through system settings, not within the app itself. This creates a strange split: the audiobook player has granular controls, but the TTS feature relies on the operating system. For users who switch between listening to a professionally narrated audiobook and having the app read an e-book aloud, the experience is inconsistent. The audiobook player remembers your speed preference; the TTS engine does not. You have to set it separately in Android's accessibility menu. This is not documented anywhere in the app's help section.

Comparing the loan systems: Biblio versus Libby

In several Norwegian counties, Biblio has replaced both BookBites and Libby as the primary digital lending platform. This is a forced migration, not a user choice. Libraries in Akershus, Buskerud, and Østfold have told patrons that access to Libby will end after May 19. The new app uses the same library card and PIN, but the catalog is different. Biblio offers both Norwegian and English e-books and audiobooks, while Libby had a broader international catalog. The search filters in Biblio are less accurate, according to multiple user reviews. Users have described the usability as "horrendous compared to Libby". The loan limits also differ. In Trøndelag, Biblio allows 5 simultaneous e-book loans and 2 audiobook loans, with a 28-day lending period and one renewal if no one is waiting. Libby's limits varied by library but were generally more generous. The automatic return feature works the same way: books disappear from your device when the loan expires. But Biblio adds a feature that Libby does not have: you can manually return books early from the loan list. This is a small but practical advantage.

The biggest difference is the business model. Biblio is free for libraries to use; they pay only for the content that patrons actually borrow. Libby charges libraries a service fee on top of content costs. This is why many Nordic libraries are switching. The platform itself is a "pure European solution" with data hosting in Frankfurt. For patrons, this means nothing changes on the surface. But behind the scenes, the library has more budget control. The downside is that the catalog may be smaller because libraries are buying content on a pay-per-use model rather than bulk licenses.

What the changelog does not tell you

Biblio's Play Store listing shows no "What's New" section for the current version. This is not an oversight; it is a pattern. The developer, WeDoBooks, has not published a detailed changelog for months. The only way to know what changed is to check APK mirror sites, which show version 5.1.24 as the latest build. Older versions like 4.4.1 are still available on some sites, but they lack the new features and the updated catalog integration. The jump from version 4.x to 5.x suggests a major rewrite, which may explain the persistent bugs that users continue to report. Crashes, loading failures, and navigation issues are common complaints across multiple review platforms. The app's permission list includes camera access, network state, foreground service, and wake lock. The camera permission is surprising for a reading app, and it is not clear why the app needs it. The Exodus privacy report confirms these permissions, but the developer has not explained their purpose.

The lack of a changelog matters because users cannot tell whether a crash they experience is a known issue or a new bug. The official help center advises deleting all downloaded material and re-downloading the book as the primary fix for loading problems. This is a blunt instrument. It works, but it forces users to re-download every book they have saved for offline reading. The help center also suggests restarting the device and clearing the app's cache. These are generic troubleshooting steps that apply to almost any app. They do not address the underlying problems. The developer's silence on what has actually been fixed in each update erodes trust.

How offline downloads interact with the infinite spinning wheel

Biblio allows users to download e-books and audiobooks for offline reading and listening. This is a core feature, especially for users who commute or travel. The process is simple: open the book, tap the download button, and wait for it to finish. The problem starts when you try to open a downloaded book later. The app shows a spinning wheel and never loads the content. The official fix is to delete all downloaded material from the settings menu and re-download the book. This works, but it defeats the purpose of offline reading. If you are on a plane or in an area with no signal, you cannot re-download the book. The app also does not provide a clear error message. It simply spins indefinitely. This behavior suggests a problem with how the app caches downloaded files or how it verifies the license for offline access. The app uses DRM protection, which is common for library e-books, but the implementation appears to be fragile. Users have also reported that the app sometimes loses the place they were reading, forcing them to scroll back through pages to find their spot. The sync feature should prevent this, but it does not always work across devices.

The offline download feature also has a data usage problem. One user reported that the app uses a "ridiculous amount of data" even when not actively downloading books. This suggests that the app may be re-downloading content in the background or failing to cache properly. The help center confirms that audiobooks are streamed by default to save space, but users have the option to download them. The issue is that the app does not clearly communicate which mode it is using. A user who thinks they are streaming may actually be downloading, and vice versa. This lack of transparency leads to unexpected data bills, especially for users with limited mobile data plans.