The app now supports watchOS 4 and can potentially have a complication, however in testing the complications have a very small CPU and network budget, so it can only update a few times per hour, then it gets stuck on the last update. This makes it show the wrong prediction for a while. I’m looking into ways around it to reduce the CPU and network, but it is a fundamental issue with the way complications work in watchOS.Anonymous commented
Would be great. Especially with the new Series 4 faces, so much potential.Anonymous shared this idea ·
I have considered adding additional sounds – I’ll keep it in mind for a future update.
I’ll look into it if I get time