Theme
Sleeve Notes
An album-first listening room: artwork up front, notes beside it, and the next tracks within reach.
What makes this practical?
Uses artwork, library metadata and queue state already owned by the player.
A work in progress
A future purchase should be easy to understand: finish checkout, confirm access, and find what belongs to you. Try the different outcomes below while the real connection is being built.
Looking for the downloadable Listening Notes module? Visit the shop →
Example collection · Concepts, not products for sale
A theme brings together a layout and a visual language. Modules are useful pieces you can place inside a compatible theme: keep the ones you want, move them around, and leave the rest out.
Theme
An album-first listening room: artwork up front, notes beside it, and the next tracks within reach.
Uses artwork, library metadata and queue state already owned by the player.
Theme
A compact workspace for long sessions. Put the queue first and keep the album, notes and file details close by.
Uses the same pieces in a denser arrangement, with transport always reachable.
Module
A movable sleeve with album, artist and track identity. Give it room, or keep it small beside the queue.
Reads local artwork and metadata; a clear fallback handles missing covers.
Module
See what follows the current song. A narrow strip or a larger queue panel, placed where you naturally look.
Shares the player’s queue; it must not create a second playback state.
Module
Keep your own thoughts with an album: a favourite moment, a memory, or something to listen for next time.
Would need local note storage and stable album matching.
Module
A quiet readout for format, sample rate and bit depth. Show it when you care; move it away when you don’t.
Uses actual file metadata. Source quality must stay distinct from output quality.
This browser sketch uses fictional music. It does not play audio or install anything.
The Sunday Rooms · Fictional album
These are proposed directions, not shipped themes or installable modules. The sketch shows ordering and visibility; free placement, resizing and cross-theme compatibility still need app implementation and testing. Android would need its own compact layouts. No prices have been set.
Interactive concept · No charge
This is not RevenueCat Test Store. It makes no RevenueCat requests, collects no payment information, and grants no real access. Reloading clears the simulation.
Checking the website’s live commerce status…
Try the flow with Sleeve Notes, an example theme. No real product or price is configured. Choosing a different example resets this journey.
A successful checkout screen alone should not unlock a download. In the connected system, a trusted access check would establish what this account owns.
Try checking access after returning to the app, or after a refund. This only remembers the example receipt inside this tab.
In the connected version, RevenueCat will report purchase and entitlement information. Pixelody still needs to connect that information to the right account and authorize its downloads. It will not host your music or turn your local library into a subscription.
This interactive preview works in your browser. Android has an isolated RevenueCat debug integration, and the website has a guarded event-receiver foundation. The RevenueCat project, shared accounts, live purchase testing, and protected file delivery are not connected yet.
A real RevenueCat Test Store run is the next verification step. This concept demonstration is not evidence of a completed integration or hackathon eligibility.
About RevenueCat Test Store ↗