I’ll look into it if I get time
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.
I like the idea of this, but there are so few iPad users and also it would be quite a lot of work as the layout is quite different.Anonymous commented
Definitely want this!
I don’t have an Apple watch at the moment to test this on, but I’ll look into it when I can.Anonymous commented
Maybe even just force press and an option to refresh?