2 pointsby paweljanda6 hours ago1 comment
  • paweljanda5 hours ago
    A bit more context on the “why” / design:

    We wanted a single facade with streams as the primary integration surface (so UI/state layers can stay thin).

    We intentionally avoid forcing any state management library; you can use BLoC/Riverpod/etc. on top.

    The package focuses on the common audio app workflows (queue-first), rather than exposing every low-level knob.

    If you’ve shipped audio in Flutter: what were your biggest pain points (background quirks, interruptions, lock screen controls, queue sync, etc.)?