Under the surface

Find your way around.

Guides for listening, building and understanding what Pixelody does today. Each one separates working features from experiments and future plans, with links to the technical background when you want to go further. Reviewed September 30, 2026.

01 / USING PIXELODY

Start with the overview

Read what the Windows and Android apps do, which formats are supported, and where the current limits are.

READ ON THIS SITE →
02 / ADDING A MODULE

Start with Listening Notes

Check build compatibility, install the free notebook and understand where your notes are saved.

READ ON THIS SITE →
03 / THEMES AND MODULES

Understand the structure

See how Studio, development themes and the new module candidate fit together—and where they remain separate.

READ ON THIS SITE →

24 of 24 documents · searches full text

Users / REVIEWED GUIDE

Windows and Android overview

Pixelody is being built for people who want a music collection they can keep, understand and spend time with.

Reviewed September 30, 2026. Describes development status, not a guarantee for every installed build.

Written for this reader; repository records may contain older plans.Repository background ↗

Your music, on the device you are using

Pixelody is being built for people who want a music collection they can keep, understand and spend time with. Windows and Android share that purpose, but each has its own interface and playback implementation. They are related apps, not identical ones.

Windows

The desktop app manages a local library, playlists, metadata, queue and playback, with tuning controls and a mini-player. It can also act as the library host for supported trusted-device workflows.

Studio is the current built-in presentation. Older theme names in repository notes describe archived work or development experiments; they are not all selectable in the normal app.

Android

The native Android app includes local music playback as well as connections to a trusted desktop host. Music stored on your phone can be played locally; a desktop connection is needed for workflows that use the host library or session. Host browsing and shared-session actions still depend on the relevant host, permissions and network.

Files and audio

The desktop import path recognizes common formats including FLAC, WAV, AIFF, MP3, M4A/AAC, Ogg and Opus. Recognition does not guarantee that every codec variant will decode on every device. Check the exact build and file when something fails.

Windows shared-mode output may resample audio. A lossless source label is not proof of bit-perfect output.

Getting a build

Use the download page for the current distribution status. Listening Notes requires the new Module Shop test build; downloading its package will not upgrade an older app. The website, source tree and installed build can be at different stages. Check the build you actually have.

TECHNICAL BACKGROUND

Need the repository record?

These guides explain the project in plain language. The repository keeps the detailed contracts, experiments and build receipts; check their dates and status notes before treating a plan as a working feature.

Browse all documentation ↗