Map: iOS app that plays the narration track
Chưa có ai nhận issue này.
Đánh giá
- Độ khó
- 5/5
- Thời gian dự kiến
- Hơn một tuần
- Mức phù hợp với người mới
- 35/100
- Loại issue
- Tính năng
- Độ rõ ràng
- Khá rõ ràng
- Mức độ hoạt động
- Sôi nổi
- Công nghệ
- ios, typescript
- Lĩnh vực
- audio-video-rtc, mobile
Hướng nghiên cứu
Read the glossary, conversion and authentication architecture pages, apps/mobile-app/README.md, and qa/mobile-e2e/README.md; review ADR 0011 and the simulator probe in issue 374. The map calls for a physical iPad probe to resolve playback, controls, headphone, call, and save behavior before writing the spec. Done means one spec ready for /to-tickets that covers CUP-81’s acceptance check, testing, and documentation changes.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Mô tả
Destination
A spec ready for /to-tickets that makes Cup's iOS app play an audiobook's narration track reliably. It names the playback engine and any native pieces the shell gets, and how system media controls, headphone disconnects, calls and listening-position saves behave. It says how the result is tested on the simulator and on a physical device, and which ADRs, architecture pages and READMEs change. Its acceptance check is CUP-81's: with the device locked, playback continues through a whole audiobook on the operator's iPad Air 2022 (latest iPadOS), which stands in for an iPhone; system media controls show title, cover image, whole duration and position, and their play, pause and seek actions work; playback pauses when headphones disconnect; and the saved listening position follows the same rules as the web player. Releasing the app is out of this map's scope (see Out of scope).
Notes
- Origin: CUP-81 iOS app that plays the narration track (Linear, stays in Backlog while this map is open). On 2026-11-16 it was split, with this map, from CUP-41 and Map: Native Android media player, which keep Android.
- Starting point: the shell plays through the web player's single
<audio>in itsWKWebView, best effort (ADR 0011), and keepsUIBackgroundModesaudio. The web player sets onlynavigator.mediaSession.metadata. The removed per-segmentNarration*Swift components are in git history at0fb4e71d; they played one MP3 per segment, so none of them applies unchanged. - Evidence so far: Narration track playback in the Capacitor WebView (2026-10-27, from source: WebKit keeps audio-only media playing in the background and publishes Now Playing by default) and the simulator probe under Decisions so far. None of it comes from a physical device.
- Settled while charting (2026-11-14, carried over from the shared map).
- The map ends in one spec; it plans only and carries no build.
- The engine is an open decision: WebView
<audio>with WebKit's Now Playing and any minimal native pieces (keeps ADR 0011), or a native player (supersedes its "native players removed"). - Probes run AFK on the simulator wherever it can show the behavior. HITL probes on the operator's iPad cover only what it cannot, such as a real locked listen, headphone routing and calls.
- Settled at the split (2026-11-16). The web player's
navigator.mediaSessionaction handlers and position state, for every platform, belong to Map: Native Android media player. This map builds on that decision and only checks how WebKit's Now Playing reacts to it. - Skills:
grillinganddomain-modelingfor grilling tickets,researchfor research tickets. Read the glossary, the conversion architecture (Playback; Delivery, positions and lifecycle), the signed media URL,apps/mobile-app/README.mdand the mobile E2E suite first.
Decisions so far
- Can the Capacitor WebView's audio element play a narration track with the device locked? (from the narration-track map): likely yes on iOS with the existing configuration; device behavior unverified.
- How do iOS Safari and Android Chrome fetch and play one long MP3 while locked? (from the narration-track map): the engine keeps issuing range requests through a locked listen without page JavaScript, so media authorization must stay valid from Play to the end.
- How is the narration track authorized over a long listening session? (from the narration-track map): a signed track URL valid for the whole session.
- Which native configuration stays in the Capacitor shells? (from the narration-track map): the shell got removals only and keeps the
audiobackground mode; everything that makes it play moved to this increment. - Which plugins or players could give Cup's Android and iOS apps a media-playback foreground service and system controls under Capacitor 8? (from the Android map): for iOS, a WebView engine needs no native code for Now Playing;
@capgo/capacitor-media-sessionwritesMPNowPlayingInfoCenternatively, which may compete with WebKit's own (unverified); native players (Capawesome Audio Player, hand-written AVPlayer) are viable but add a second engine behind the web player, and AVPlayer pauses on headphone disconnect; from source and docs, not run. - How does Cup's WebView audio behave on the iOS simulator?: with WebKit's defaults the lock screen shows title, scrubber, Play/Pause and 10-second skips that drive the
<audio>, artwork unconfirmed;navigator.mediaSessionhandlers receive those commands andsetPositionStatetakes over the shown position; signed-URL range requests fromcapacitor://localhostreturn206through seeks and a locked listen; audio, timers andCapacitorHttpsaves kept running while locked only because the simulator ignores RunningBoard's suspension of Cup's app, page and network processes after about 30 s, so a device may stop page scripts and saves while audio plays.
Not yet specified
- Listening-position saves while locked. Depends on what the iPad probe shows: if iOS suspends the page, how saves happen during a locked listen (natively, on unlock, or not at all), and whether "the same rules as the web player" still hold.
- System controls. Whether WebKit's Now Playing, with the handlers and position state the Android map decides, is enough, or whether Cup writes Now Playing natively.
- Headphones, calls and other apps. What Cup does when each happens, once the iPad probe shows what WebKit does by itself.
UIBackgroundModesaudio. Whether it stays, from the probe's variant run.- Testing. What the mobile E2E suite can cover on the simulator, and the physical-device protocol.
- Documentation. Which ADRs, architecture pages, glossary terms and READMEs the build changes.
Out of scope
- Releasing the app: CUP-79 Publish the iOS app to the App Store. CUP-81's "the iOS app is released" criterion is met through it.
- The Android app and the web player's media-session handlers and position state: Map: Native Android media player.
- Testing the app's other native functionality on physical devices: CUP-44, which CUP-81 blocks.
- A player queue (CUP-57) and the transcript view (CUP-9).
- Ngôn ngữ chính
- TypeScript
- Star
- 1
- Fork
- 0
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Chuẩn bị môi trường
Dự án này không cung cấp dev container, Dockerfile hay hướng dẫn đóng góp, nên bạn cần tự thiết lập môi trường: hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.
Bắt đầu từ đâu
- Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
- Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
- Fork repository và làm thay đổi trên một nhánh.
- Mở pull request có tham chiếu số hiệu của issue.
Issue khác của patricktree/cup
-
wayfinder:grilling
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 72/100
patricktree/cup#484 ·
-
wayfinder:grilling
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 48/100
patricktree/cup#487 ·
-
wayfinder:grilling
Độ khó 5/5 Hơn một tuần Mức phù hợp với người mới 25/100
patricktree/cup#486 ·
-
wayfinder:grilling
Độ khó 5/5 Hơn một tuần Mức phù hợp với người mới 25/100
patricktree/cup#485 ·
-
wayfinder:grilling
Độ khó 5/5 Hơn một tuần Mức phù hợp với người mới 25/100
patricktree/cup#483 ·
Tất cả issue của patricktree/cup
Issue tương tự
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 72/100
Maintainer thường phản hồi trong vòng 1 ngày
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 78/100
vercel-labs/ui#865 ·
Maintainer thường phản hồi trong vòng 1 ngày
-
bug
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 63/100
outline/outline#14638 · 1 bình luận ·
Maintainer thường phản hồi trong vòng 1 ngày
-
bot:ai-assisted component:platform-js status:untriaged
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 78/100
midnightntwrk/platform-js#69 ·
Maintainer thường phản hồi trong vòng 1 ngày
-
bug
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 67/100
Maintainer thường phản hồi trong vòng 1 ngày