Thanks for sharing, I will give this a try today. What is the rationale for requiring the app to be open and leaving the screen on (draining battery)? Was this a technical limitation?
I tried a few different implementations (e.g. using background video/audio), but ultimately the device’s unpredictable management of background apps made it impossible to distinguish between navigating away from the app and locking the phone. I ended up going with the “dumb” solution.
It actually works quite nicely (especially as a PWA on iOS) because it makes the stretch feel more intentional, and it discourages “gaming” the system by recording long stretches while sleeping.
I’ve found the battery drain is also pretty negligible over 2-3 hour stretches, the dark screen / pixels seem to help a lot.
I tried a few different implementations (e.g. using background video/audio), but ultimately the device’s unpredictable management of background apps made it impossible to distinguish between navigating away from the app and locking the phone. I ended up going with the “dumb” solution.
It actually works quite nicely (especially as a PWA on iOS) because it makes the stretch feel more intentional, and it discourages “gaming” the system by recording long stretches while sleeping.
I’ve found the battery drain is also pretty negligible over 2-3 hour stretches, the dark screen / pixels seem to help a lot.