In development · Open source · Android and web

From first chapter to fast asleep.

Connect the libraries you already have through add-ons, download for the flight, and keep listening with the screen off. Open source, no account, no app store, no lock-in.

  • Works fully offline
  • No account needed
  • Audio never passes through our servers
How it works

The app plays. Add-ons bring the library.

Lelap handles playback, downloads, progress and sync. What you browse, where the audio lives and where your progress is shared are add-ons you choose, made and run by whoever builds them.

1 · Add-ons answer
CatalogsTrending, new, your shelves
MetadataCovers, narrators, chapters
SourcesWhere the audio file lives
ScrobbleShare progress elsewhere
2 · Your device keeps it

Library, progress, downloads and playlists live on your phone first.

Add-ons can be slow, offline or gone tomorrow. What you downloaded keeps playing, and your progress never depends on someone else’s server.

3 · Install by URL
GET /manifest.json
{
  "id": "org.librivox",
  "resources": ["catalog", "meta", "stream"],
  "types": ["audiobook"]
}

Paste an add-on’s address and you’re done. Settings live on the add-on’s own page; the app only remembers the URL.

Ships with open sources:LibriVoxOpen LibraryPodcast IndexRSS feedsYour own filesOptional:AudiobookshelfWebDAVHardcovergPodder
Features

Built for long listens.

Lull, the sleep timer that fades

Minutes or end of chapter. Fades out over the last minute, rewinds a little so you can find your place, and a shake buys you ten more.

Offline first

Download books and episodes over Wi-Fi with the screen off. Airplane mode is a normal day, not an error state.

Plays in your pocket

Screen off, app closed. Lock screen, headphone buttons, Bluetooth and Android Auto all work.

Keeps going through calls

Lower the volume instead of stopping when a call comes in. Your choice, on Android.

Progress that follows you

Pick up on your laptop where you stopped on your phone. Pair devices with a code; sync is end-to-end encrypted.

Smart rewind, speed, chapters

Rewinds further the longer you paused. Speed per book with pitch correction, silence skipping and chapter-aware scrubbing.

Playlists, tags and Up Next

One queue for books and episodes, hand-made lists, and smart ones like “short and not started” or “for the flight”.

Cast to the living room

Chromecast and Sonos from Android, with your progress kept while it plays.

Bring your own files

Import m4b, mp3, opus and flac, or point it at a folder. Chapters come from the tags. OPML in and out for podcasts.

Get it

One codebase, three ways to listen.

All three arrive with version 1.0.

Web app

listen.lelap.app

Nothing to install. Add it to your home screen as a PWA. Best for your laptop, or any device that isn’t an Android phone.

Planned for v1.0

Android

.apk · no Play Store

The full experience: background playback, downloads with the screen off, casting and Android Auto. Small updates install themselves; new versions take one tap.

Planned for v1.0

Self-hosted

docker compose up

Run the web app, catalog, feed proxy and sync on your own machine, and point the Android app at it.

Self-hosting

No iOS app is planned. iPhone and iPad can use the web app, with streaming and in-app downloads.

Self-host

Run the whole thing yourself.

Everything behind listen.lelap.app is in the repository. Four small containers, no database server to babysit.

  • webThe PWA, served as static files.
  • catalogThe built-in catalog add-on: Open Library, LibriVox and Podcast Index, cached.
  • proxyFetches RSS feeds and cover images for the web app. Never audio.
  • syncStores encrypted progress and playlists. It can’t read them.

Images are published with the first release.

docker-compose.yml
services:
  web:
    image: ghcr.io/lelap-app/web
    ports: ["8080:80"]
  catalog:
    image: ghcr.io/lelap-app/catalog
    env_file: .env
  proxy:
    image: ghcr.io/lelap-app/proxy
  sync:
    image: ghcr.io/lelap-app/sync
    volumes: ["./data:/data"]
$ docker compose up -d

Nothing to look at, by design.

No account

Your library lives on your device. There is no profile to sign up for.

Encrypted sync

Devices pair with a code. The sync server only ever sees ciphertext, including your add-on list.

No audio through us

Your phone talks to add-ons and their sources directly. We never see what you play.

No ads, no tracking

Open source, so you can check every line of that claim.

Questions

When can I use it?

Lelap is in early development. Follow the repository on GitHub to see progress; the plan and the v1.0 scope are in the open.

Where does the audio come from?

From the add-ons you install. Out of the box that means public-domain audiobooks from LibriVox, podcast feeds and your own files. Add-ons are made and run by third parties. You are responsible for the add-ons you add and for only playing content you have the right to.

Does Lelap list or recommend third-party add-ons?

No. We publish our own add-ons for open sources and the SDK, nothing else. There is no add-on store, and we don’t link to, review or promote add-ons made by others.

Is it free?

Yes. The code is open source, and the hosted web app at listen.lelap.app will be free to use.

Do I need an account?

No. To continue on another device, pair it with a sync code. Skip that and everything stays on the one device.

Why isn’t it on Google Play?

We ship the .apk directly so releases don’t wait on store review. The app checks for updates itself, or you can follow releases with Obtainium.

Can I write my own add-on?

Yes. An add-on is a small HTTP service that returns JSON. The protocol and an SDK will be documented in the repository.

What does “Lelap” mean?

It’s Indonesian for deep, peaceful sleep. It’s how we think a good story should end your day.

For rights holders

Report copyright infringement

Lelap is a player. We don’t host, index or link to audio, and our servers never carry it. If you believe something on our websites, in our repositories or in one of our own add-ons infringes your rights, tell us and we’ll act on it.

Please include:

  • The work you hold rights to
  • Where you found the infringing material, with a link
  • How to reach you, and that you are authorised to act for the rights holder

Add-ons made by others run on their own servers. We can’t remove them, but we’ll tell you what we know about where one is hosted.