- disk storage: depends what you're doing, but seems to be about 150MB / hour. This is WAY too much in my book. I think we could get this way down. I'd love help here too :D
- Candidly, haven't done extensive testing in battery department, but someone posted an article in a sibling comment https://kevinchen.co/blog/rewind-ai-app-teardown/ and it said "Overall, running Rewind reduces my battery life by about 20–40 percent." - that's way too much imo. And I assume `rem` is in that ballpark, as based on this article, it's doing pretty similar stuff, though way fewer accesses to disk as I don't write screenshots to disk, just stream directly to mp4.
But - I built it in a few days and haven't spent time on optimization. This can be clearly seen in the binary size too. First build I released was 165MB, and after I took a step back, fixed the build process, and built a custom build of ffmpeg, it's now 3MB. Seeing as Rewind is a 211MB dmg, they aren't doing a ton of optimization either, so I think there's tons of room for improvement.
- how much disk storage does this use, say per hour of typical computer use
- how much CPU/battery life impact does it have