Product purpose and design principles

Register

product

Users

Music listeners and self-hosters moving or creating personal playlists across streaming services. They need to understand provider compatibility, account state, selection scope, generated-track evidence, progress, and exceptions.

Product Purpose

Open Playlist Engine makes playlist migration and local-first generation understandable and trustworthy. Success means a user can connect services, choose what moves or describe what to build, review real provider matches before writing, monitor progress, and verify the result without learning provider-specific internals.

Brand Personality

Confident, precise, and music-native. The interface should feel technically dependable without resembling infrastructure software, and expressive without competing with the user's library.

Anti-references

Avoid generic SaaS dashboards, crypto-style neon gradients, glass-heavy streaming clones, ornamental waveform decoration, identical card grids, and interfaces that hide migration state behind clever visuals.

Design Principles

  • Make the source-to-target route unmistakable.
  • Keep generated suggestions visibly separate from provider-resolved tracks.
  • Use provider identity where it improves recognition and confidence.
  • Keep system state visible before, during, and after migration.
  • Turn errors and empty states into clear next actions.
  • Save delight for meaningful feedback rather than decoration.

Accessibility & Inclusion

Target WCAG 2.2 AA contrast and keyboard operation. Do not rely on provider color alone, preserve visible focus, support reduced motion, keep touch targets comfortable, and ensure status labels remain understandable to screen-reader users.