Let's Talk Resume
Portfolio / Case Studies / TuneBox

TuneBox

A cross-platform mobile audio streaming client featuring resilient offline playback, asynchronous audio buffer management, and decoupled Provider state architecture.

Role Mobile Software Engineer Intern
Category Mobile App Architecture & Audio Streaming
Timeline Svype Internship · 2026
Core Stack Flutter · Dart · Provider · REST APIs · SQLite

Problem & Challenge

Mobile audio applications encounter severe edge cases in real-world use: network transitions between Wi-Fi and mobile data trigger audio dropout, aggressive OS background execution limits terminate playback threads unexpectedly, and coupling audio playback logic directly into UI widgets creates tangled state bugs.

The engineering challenge was to architect a reusable, modular audio service in Flutter that handles background playback, lock screen media controls, playlist queues, and local-first offline caching while dramatically simplifying screen rendering code.

Technical Approach & Architecture

We restructured the application around an isolated state management pattern powered by Provider and Dart asynchronous streams:

  • Decoupled Audio Manager Service: Encapsulates player lifecycle events, headphone unplug events, audio focus loss (such as incoming telephone calls), and notification service synchronization.
  • Reactive State Management: Replaced scattered setState() calls across multiple player screens with a centralized AudioPlayerProvider, preventing unnecessary widget rebuilds during position updates.
  • Local-First Playlist Cache: Integrated an on-device key-value store to cache song metadata, album art bitmaps, and audio stream buffers for instantaneous offline resumption.
  • REST API Gateway Integration: Structured clean data contracts for catalog search, artist discography fetches, and personalized user library syncing.
TuneBox Audio Stream & State Architecture
Flutter UI Layer (Player Screen & Mini-Player)
Listens to Provider streams; dispatches play/pause/seek events via strict actions
↓
AudioPlayerProvider (Central State Store)
Coordinates playback state, track indices, shuffle algorithms, and volume normalization
↓
Native Audio Service Handler (Android/iOS)
Manages OS media sessions, lockscreen art, and audio focus interrupt logic
↓
Hybrid Audio Cache (Remote Stream vs. Local Disk)
Streams chunks via HTTP while spooling verified audio segments to local storage

Engineering Challenges & Solutions

1. Codebase Bloat & State Duplication

Initially, player logic, seekbar animation interpolation, and network request handling were duplicate-implemented across the full-screen player, the bottom persistent mini-player, and the lock screen service, spanning over 1,200 lines of brittle code.

Solution: Extracted an atomic AudioControlService singleton that exposed pure reactive streams. Both the full player and mini-player subscribe to the same underlying stream through a unified controller. This reduced UI logic from ~1,200 to ~720 lines, completely eliminating UI state drift between views.

2. Smooth Scrubbing on Uncached Streams

Rapid seekbar dragging on remote audio streams resulted in multiple overlapping HTTP range requests, causing audio stuttering and thread lock on lower-spec Android devices.

Solution: Implemented a 300ms Debounce Operator on seek gestures. The UI visual slider updates immediately at 60 FPS for responsive tactile feel, while network buffer repositioning requests are dispatched only once user touch interaction completes.

Key Features & Capabilities

  • Continuous Background Playback: Uninterrupted audio delivery with native lock screen controls and headphone button response.
  • 40% Codebase Optimization: Reduced architectural complexity through modular Provider state consolidation.
  • Offline Playlist Resiliency: Automatic fallback to cached audio files when cellular connectivity drops.
  • Cross-Platform Parity: Identical responsive design and fluid gesture ergonomics across iOS and Android.