feat: use native slider for playback (#88)

[jsit]

Replacing our DIY slider for OS-native sliders from React Native library. Should feel more native, be easier to maintain, and better for accessibility.

I can't actually drag this on the Android emulator, so -- I don't know if that's the emulator's fault or the component's fault, but either way I'm opening this as draft.

This will require an npm i and pod install to work.

Closes #88

Screen.Recording.2025-11-15.at.12.55.18.PM.mov

[Copilot]

Pull Request Overview

This PR replaces the custom DIY slider implementation with the native @react-native-community/slider component to improve maintainability, accessibility, and provide a more native feel for playback controls.

Key changes:

• Introduces new PlaybackSlider component wrapping @react-native-community/slider
• Removes complex gesture handling code using react-native-reanimated and react-native-gesture-handler
• Simplifies the codebase by eliminating ~200 lines of custom slider logic

Reviewed Changes

Copilot reviewed 4 out of 6 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/components/PlaybackSlider.tsx	New component wrapping the native slider with TrackPlayer integration
src/app/Schedule/ShowDetailsPage.tsx	Replaces custom progress bar/gesture code with PlaybackSlider component
src/app/Schedule/ArchivedShowView.tsx	Replaces custom progress bar/gesture code with PlaybackSlider component
package.json	Adds @react-native-community/slider dependency (v5.1.1)
package-lock.json	Lock file update for new dependency
ios/Podfile.lock	iOS native dependency update for slider component

Comments suppressed due to low confidence (1)

src/app/Schedule/ShowDetailsPage.tsx:68

• The useMemo here is unnecessary and potentially problematic. The useProgress() hook already returns a stable object reference that updates when progress changes. Wrapping it in useMemo with progressHook as a dependency doesn't provide any benefit since the hook result already handles its own memoization. Additionally, progressHook will never be falsy/null in normal operation, so the fallback || { position: 0, duration: 0 } is unnecessary.

Consider simplifying to:

const progress = useProgress();

And remove the progressHook variable entirely.

  const progressHook = useProgress();
  const progress = useMemo(
    () => progressHook || { position: 0, duration: 0 },
    [progressHook],
  );

[Copilot]

Pull request overview

Copilot reviewed 4 out of 6 changed files in this pull request and generated 7 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 6 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 6 changed files in this pull request and generated 4 comments.