People Liked Bloox. Then They Asked How to Get Their Audible Books Into It

When I released Bloox, I started getting a version of the same message from several people.

Sometimes it came through Reddit. Sometimes through a direct message. Sometimes through the feedback button inside the app.

The details changed, but the basic shape was:

This looks great. I would like to try it. But I already have a giant Audible library. How do I get those books into Bloox?

This is a very reasonable question.

It is also the kind of question that reveals the difference between a feature technically existing and a feature being meaningfully usable.

Bloox has always supported standard audiobook files. M4B, MP3, folders full of chapters, Google Drive, iCloud. If you have the files, importing them is simple.

But most audiobook listeners do not begin with a tastefully organized folder of DRM-free M4B files. They begin with years of purchases inside Audible.

So my first answer was usually: use Libation.

That answer was correct.

It was also not good enough.

The original path worked, if you were sufficiently motivated

Libation is a free, open-source desktop tool for downloading audiobooks from your Audible library and converting them into standard files. I use it myself. It is excellent.

Once you have those files, Bloox can import them from iCloud, from your phone, from Google Drive, or directly from your computer over Wi-Fi.

For someone already comfortable managing an audiobook library, this is a perfectly reasonable setup. It gives you control over your files. It works across apps. It is not tied to a single device.

For someone who downloaded Bloox because they wanted to read along with an audiobook and ask what they missed, it can feel like an unexpected side quest.

Install a desktop app. Connect your Audible account. Download the book. Find the exported file. Move it somewhere your phone can reach. Import it into Bloox.

None of those steps is individually outrageous.

Together, they create friction.

And friction is very good at killing curiosity. A person can be interested in a new app and still decide they do not want to spend their evening learning the surprisingly rich ecosystem of audiobook file conversion.

People were telling me exactly where the product was losing them.

So I started looking for a simpler path.

The obvious solution has an obvious trust problem

The simple product experience is easy to describe:

1. Tap Import from Audible.
2. Sign in.
3. Choose a book.
4. Wait for it to download.
5. Listen.

There is one fairly large problem hiding inside step two.

Why should you trust an indie developer with your Amazon password?

You should not.

I am an indie developer, and I would not type my Amazon password into a random indie app either. That account may contain purchases, addresses, payment methods, order history, and enough personal detail to reconstruct a modest documentary about your household.

It would be strange to ask users to ignore that concern because I added a nice headphones icon and wrote a reassuring sentence underneath it.

The goal was not merely to make Audible import easy. It was to make it easy without asking users for a level of trust the feature did not need.

Your password never touches Bloox

When you choose Import from Audible, Bloox opens an Amazon sign-in page inside a non-persistent web view.

The important part is that it is Amazon’s page. Bloox does not display its own username and password form. It does not receive your password. It does not store your password. It does not send your password anywhere.

If Amazon asks for multifactor authentication or another verification step, that also happens on Amazon’s side of the sign-in flow.

After you finish signing in, Amazon provides device credentials that allow the app to access the library. Those credentials are saved locally in the iOS Keychain using a this-device-only setting. They do not sync through iCloud.

If you sign out inside Bloox, the local credentials are cleared.

This is still a connected feature. Bloox needs to talk to Audible to list your library and download the book you choose. But it does not need to know the password you used to authenticate with Amazon.

The privacy checklist I wanted

Before building the feature, I tried to write down the version I would personally be willing to use.

Not the version I could explain with a lot of hand waving. Not the version where the app says “trust me” and then quietly does something complicated in the background. The version I would install on my own phone if someone else had built it.

For me, that meant a few rules:

• The app should never ask for my Amazon password in its own UI.
• The sign-in page should be Amazon’s page, not a recreated form.
• The browser session should not persist like a normal Safari session.
• The long-lived credentials should live in the local iOS Keychain.
• The audio file should be processed on the device, not on a server I control.

This does not make the feature magic. You are still choosing to connect Bloox to your Audible account so it can list and download books. But it removes the part that would make me immediately close the app: handing my Amazon password to a stranger’s password field and hoping the stranger is nice.

I may be the stranger in this case, technically. Still not a good product strategy.

How to import an Audible book into Bloox

The actual user flow is intentionally boring. This is a compliment.

1. Open the import sheet

In your Bloox Library, tap the Add button. You will see the available import sources. Import from Audible appears at the top.

2. Sign in with Audible

Tap Import from Audible, then Sign in with Audible. Complete the Amazon sign-in flow. Again, your password is entered on Amazon’s page and never touches Bloox.

3. Browse your Audible library

Once you are signed in, Bloox shows your Audible library. You can pull to refresh the list and tap a title to see its cover, author, narrator, length, description, and other metadata.

4. Choose Download & Import

Tap Download & Import. Bloox requests the selected book, starts the download, and returns you to your Library.

5. Follow progress in your Library

A temporary Audible Imports section appears above your book list. You can see download progress there. Downloads continue in the background if you switch apps or turn off the screen.

The final conversion step happens on-device. If a download finishes while Bloox is in the background, the app resumes that work the next time you open it.

There is no special Audible player after that. The book lands in Bloox as a normal local audiobook. That was important to me because otherwise the feature becomes a little island: Audible books over here, regular files over there, and now the user has to remember which features apply to which books.

I wanted the import source to disappear after the import was done.

Once the book is in your library, it is just your book.

What happens to the audiobook file?

Audible books are not normally delivered as ordinary audio files that any player can open. The downloaded book needs to be converted into a standard M4B file.

Bloox does that work locally on your iPhone.

The audiobook is downloaded from Audible to your device. The conversion runs on your device. The resulting M4B is imported into the same local Bloox library used for your other books.

Your audiobook audio is not uploaded to Bloox servers for processing.

Once the book is inside your library, it behaves like the other books in Bloox. It can have chapter navigation, metadata, playback progress, transcription, spoken “What did I miss?” recaps, character help, and Book Chat.

This was one reason the feature was worth building carefully. Audible import is not a separate player bolted onto the side of the app. It is an easier front door into everything Bloox already does.

A few honest limitations

The first version is deliberately narrow.

• US Audible accounts only. Audible has different regional marketplaces. The current flow targets the US marketplace.
• One book at a time. You browse your library and choose individual books to import. This is not a bulk-migration tool.
• This is not an official Audible integration. It relies on Audible behavior that may change. If Audible changes that behavior, the feature may need maintenance.
• Some subscription-only titles may not import. Purchased books are the intended path. Catalog licensing can differ for titles available only through a subscription.

I would rather be clear about those limits than pretend every Audible edge case has been solved forever. Software has a way of objecting to that sort of confidence.

Why not bulk import everything?

This is the obvious follow-up question.

If someone has a huge Audible library, why not let them import the entire thing in one button?

Because the first version should be boringly reliable before it becomes ambitious. Audiobook files can be large. Downloads can be interrupted. Conversion uses real CPU and memory. Some titles may have licensing differences. A bulk importer multiplies all of that and then asks the user to understand a queue of failures, retries, partial successes, and possibly a very warm phone.

One-at-a-time import is less impressive in a demo. It is also much easier to understand when something goes wrong.

Pick the book you want to listen to next. Import that book. Confirm the experience works. Then import another.

That is not the final form forever. It is the right first step.

Why keep the Libation path?

Direct import makes the common case easier. It does not replace the value of owning and managing your own files.

If you want a full backup of your Audible library on your computer, want to organize files exactly as you like, or use multiple audiobook players, Libation is still a great tool.

Bloox supports both approaches.

You can take the direct route when you want to add one book and start listening. You can take the file-management route when you want a larger personal library workflow.

The point is not to force everyone into the same hobby.

The point is to remove the unnecessary steps between “I have an audiobook” and “I am listening to it in the app I want to use.”

This feature came from listening to users

I built Bloox because I wanted a better audiobook experience for myself. But releasing an app changes the nature of the project.

People bring their own habits. Their own libraries. Their own assumptions. Their own entirely reasonable unwillingness to install three things before trying the first thing.

The repeated Audible question was useful because it was not asking for a random extra feature. It was identifying a barrier to the features already there.

Transcription is only helpful after a book is imported.

Recaps are only helpful after a book is imported.

Book Chat is only helpful after a book is imported.

Sometimes the highest-leverage product work is not inventing another clever thing. It is making the clever things easier to reach.