LUC4N3X · independent developer
Android apps, audio pipelines, and small Linux tools, mostly in Kotlin and Python. The part I enjoy is what comes after it works: the odd edge cases, the bug that only shows up on one phone, and stripping out whatever is in the way.
Software developer, Linux user, and the person behind Levyra.
I build software for myself and keep at it until it works the way I want. Most of my time goes into Android apps, backend APIs and small self-hosted tools.
Getting a feature to run the first time is usually the easy part. What I enjoy is everything after that: chasing the weird edge cases, fixing a bug that only shows up on one obscure phone, and cutting complexity until the code reads plainly.
A lot of my ideas end up in Levyra, my open-source music player. When I'm not working on it, I'm usually tinkering with local-first setups, audio pipelines or small Linux utilities.
An open-source music player for Android and Windows built with Kotlin, Jetpack Compose, AndroidX Media3, and libVLC. Streaming and local library playback with synced lyrics, Enhanced Audio DSP, offline downloads, and zero telemetry.
Adaptive ring buffering to eliminate OEM background service terminations.
Direct TLS 1.3 streams. All listening history stays in on-device Room SQLite.
Real-time line-by-line synced lyrics via LRCLIB with offline caching.
Technical notes on Android internals, audio DSP pipelines, Windows native builds, and open-source maintenance.
How Levyra detects brickwall codec cutoffs in lower-bitrate streams, restores missing high frequencies with an IIR Hilbert pair, and leaves true 320 kbps AAC and lossless files untouched.
Why the Windows build of Levyra skips Electron and WebView wrappers in favor of Compose Multiplatform on JVM 21, native libVLC C bindings, and hardware-accelerated Skia rendering.
Android · Windows
Levyra
Levyra started because I wanted to save playlists and stream tracks without signing up for anything. I also wanted the music I stream and the files I already have to live in the same library.
It runs on Android and Windows and plays local and remote audio through native engines: Media3 on Android, libvlc on Windows. Downloads are real M4A files in your storage, synced lyrics come from LRCLIB, and your listening data stays on your device.
As I kept using it, I added the things I missed in other players: lyrics with timing controls, Queue Spaces, AutoEQ, Android Auto, song recognition, live radio, backups and a Windows version.
My daily setup runs entirely on Linux. I pick tools that keep behaving the same way when a project gets complicated.
Kotlin · Jetpack Compose · AndroidX Media3 · ExoPlayer
Media3 and ExoPlayer keep background playback running without dropping audio.
Python · FastAPI · AsyncIO · Node.js
Python for APIs and background jobs, Node.js for smaller scrapers and web utilities.
SQLite · Room · Redis
SQLite and Room for offline storage, Redis when caching speed matters.
Docker · Cloudflare · GitHub Actions
Everything runs in containers behind Cloudflare and deploys through GitHub Actions.
Everything I ship runs on Arch Linux first and on my own phone second. These are the habits that survived.
Ship the smallest version that does the job, then live with it for a while. Most of what I thought I needed turns out to be noise.
Emulators never reproduce an OEM battery manager killing a playback service at 2am. The phone in my pocket is the test device.
Chase the root, not the symptom. A narrow fix I can verify beats a rewrite I can only hope about.
Listening history lives in Room SQLite on your phone. No account, no telemetry, nothing to opt out of.
