Auri music-aware posts: one media type without hijacking the feed

Auri supports music-aware posts in a creator-first social app Brent Haskins co-founded—audio complements text and images without autoplaying across the entire feed. The engineering goal is expressive posts with predictable playback and accessibility settings respected.

Autoplay in a social feed trains users to mute your app permanently.

Auri targets creators who want expression without the chaos of mainstream feeds. Music features must fit that promise.

Design constraints

  • No feed-wide autoplay by default
  • Visible control to play/stop per post
  • Respect silent mode and reduced motion where applicable
  • Do not steal focus from VoiceOver order on post text

Apple’s audio HIG and WCAG audio-control guidance are the reference—not competitor parity.

Same roadmap as trust features

Music posts share engineering attention with encrypted messaging and accessibility—one release train, one TestFlight feedback channel.

Beta signal

Testers cited calmer experience versus incumbents. Music that violates calm UX should ship behind explicit creator choice, not algorithmic insertion.

Author

Brent Haskins/projects/auri. Ship media features only when they respect the feed’s emotional contract.

Questions people ask about this topic.

What are music-aware posts in Auri?

Posts can attach music context so creators share tracks or audio-related content alongside visual and text elements—designed for expression, not autoplay noise. Playback should respect user settings and not surprise listeners in public environments. Exact catalog and licensing constraints are product decisions outside this engineering note.

Who co-founded Auri?

Brent Haskins as co-founder and product engineer, shipping native Swift/SwiftUI with encrypted messaging and accessibility on the same roadmap. Beta feedback emphasized calm UX. Case study: /projects/auri.

Referenced sources