I develop Folito, a free watchOS app for reading EPUB books on Apple Watch. We added an auto-scroll mode: the text scrolls continuously at a speed the user sets with the Digital Crown, so they can read hands-free with their wrist raised.
The display dims after the wake timeout because auto-scroll isn't user interaction, so the text becomes hard to read after 15–70 seconds while the user is still reading.
What we've considered
- Pausing on
isLuminanceReducedand resuming on tap. This works, but it needs a touch every minute. - Continuing in Always On (luminance reduced) with ~1 Hz line-by-line updates. This is our current plan, but the text is dimmed and SE models have no Always On.
WKExtendedRuntimeSession. None of the session types (self care, mindfulness, physical therapy, smart alarm, workout) describes reading, and we don't want to misuse one.HKWorkoutSession. Not appropriate, because it would record fake workouts.
Questions
- Is there a supported way for a frontmost app to keep the display at normal brightness while showing continuously changing content the user is reading, without touch input?
- Would a
WKExtendedRuntimeSessionstarted only while auto-scroll runs (and ended as soon as it pauses or stops) be acceptable for this, and if so, which type? - In Always On, what's the recommended way to keep text content advancing (for example, updating a
ScrollViewposition viaScrollViewReaderabout once per second)?
I found thread 720495 (iOS, isIdleTimerDisabled) and thread 122753 (Always On, 2019), but neither covers a watchOS app that needs the display awake while content advances on its own.
Deployment target: watchOS 10, SwiftUI. Thanks!