Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apps CARROT Weather's customizable complications

MakerOfCARROT said:
Hmm, that's strange. The temperature and condition on the complication should always update when you open the main app. (Of course, you have to wait for the main app to reload its data before the complication will update - when you first open the main app, it'll be showing old data if the app was already open in the background.)
Click to expand...

Once in awhile the complication will update after opening the main Apple Watch app, but the data doesn't match up.

The data in the main Apple Watch app never matches the data in the iPhone app
 
MakerOfCARROT said:
They're never going to match exactly unless you happen to open the iPhone app right after the Apple Watch app updates itself - they're just on different refresh schedules. See my reply to your post on the last page for a full explanation.
Click to expand...

I have tried opening the iPhone app after the Apple Watch updates and the data doesn't match. I also tried the iPhone app first and then the Watch, still doesn't match. It's like each device is retrieving entirely different data even though both have the same location name.
 
mrwilly25 said:
I have tried opening the iPhone app after the Apple Watch updates and the data doesn't match. I also tried the iPhone app first and then the Watch, still doesn't match. It's like each device is retrieving entirely different data even though both have the same location name.
Click to expand...

Is it actually "entirely different", or is it a difference of a few degrees?

Like I said above a couple times, you're not going to catch the apps with the exact same data set because they're all on different caches. When you see the main Apple Watch app update when you open it, it's not necessarily updating its data - it might just be refreshing from data already downloaded via the complication.

The main Apple Watch app also uses a complex algorithm to forecast weather data in between data refreshes to speed up load times instead of finding your GPS coordinates, downloading data from the network, then updating the UI every time, which can sometimes be very slow on the Apple Watch. So, as a simple example, if it's 70 degrees at 10am and it's forecasted to be 80 degrees at 11am, it won't continue showing 70 degrees for that entire hour - it'll be 73 degrees at 10:15, 75 degrees at 10:30, etc. It's still using the same data set as the complication, it's just forecasting out. It's so much faster doing it this way in terms of load speeds, it's ridiculous - and you get much more timely data than you would normally. And it took a ridiculous amount of time to implement on my end. (You can always do a direct refresh of the weather data using Force Touch.)

The main iPhone app doesn't use this algorithm because it doesn't have any delay in finding your GPS coordinates, downloading data, and updating its UI like the Apple Watch does - it's all instant. But for that reason, it's never going to match exactly what the main Apple Watch says.

If you're obsessively checking all 3 displays, then there will always be differences between them. The iPhone will be the most up to date, followed by the main Apple Watch app, followed by the Apple Watch complication. They'll always be within 30 minutes of each other.

In any event, if you're having technical issues please feel free to email at support at meetcarrot dot com.
 
  • Like
Reactions: dictoresno, soulsteelgray, nicho and 3 others
MakerOfCARROT said:
Is it actually "entirely different", or is it a difference of a few degrees?

Like I said above a couple times, you're not going to catch the apps with the exact same data set because they're all on different caches. When you see the main Apple Watch app update when you open it, it's not necessarily updating its data - it might just be refreshing from data already downloaded via the complication.

The main Apple Watch app also uses a complex algorithm to forecast weather data in between data refreshes to speed up load times instead of finding your GPS coordinates, downloading data from the network, then updating the UI every time, which can sometimes be very slow on the Apple Watch. So, as a simple example, if it's 70 degrees at 10am and it's forecasted to be 80 degrees at 11am, it won't continue showing 70 degrees for that entire hour - it'll be 73 degrees at 10:15, 75 degrees at 10:30, etc. It's still using the same data set as the complication, it's just forecasting out. It's so much faster doing it this way in terms of load speeds, it's ridiculous - and you get much more timely data than you would normally. And it took a ridiculous amount of time to implement on my end. (You can always do a direct refresh of the weather data using Force Touch.)

The main iPhone app doesn't use this algorithm because it doesn't have any delay in finding your GPS coordinates, downloading data, and updating its UI like the Apple Watch does - it's all instant. But for that reason, it's never going to match exactly what the main Apple Watch says.

If you're obsessively checking all 3 displays, then there will always be differences between them. The iPhone will be the most up to date, followed by the main Apple Watch app, followed by the Apple Watch complication. They'll always be within 30 minutes of each other.

In any event, if you're having technical issues please feel free to email at support at meetcarrot dot com.
Click to expand...

Thank you for the detailed explanation on how everything works with the Apple Watch app and Complication.
 
  • Like
Reactions: MakerOfCARROT
MakerOfCARROT said:
Is it actually "entirely different", or is it a difference of a few degrees?

Like I said above a couple times, you're not going to catch the apps with the exact same data set because they're all on different caches. When you see the main Apple Watch app update when you open it, it's not necessarily updating its data - it might just be refreshing from data already downloaded via the complication.

The main Apple Watch app also uses a complex algorithm to forecast weather data in between data refreshes to speed up load times instead of finding your GPS coordinates, downloading data from the network, then updating the UI every time, which can sometimes be very slow on the Apple Watch. So, as a simple example, if it's 70 degrees at 10am and it's forecasted to be 80 degrees at 11am, it won't continue showing 70 degrees for that entire hour - it'll be 73 degrees at 10:15, 75 degrees at 10:30, etc. It's still using the same data set as the complication, it's just forecasting out. It's so much faster doing it this way in terms of load speeds, it's ridiculous - and you get much more timely data than you would normally. And it took a ridiculous amount of time to implement on my end. (You can always do a direct refresh of the weather data using Force Touch.)

The main iPhone app doesn't use this algorithm because it doesn't have any delay in finding your GPS coordinates, downloading data, and updating its UI like the Apple Watch does - it's all instant. But for that reason, it's never going to match exactly what the main Apple Watch says.

If you're obsessively checking all 3 displays, then there will always be differences between them. The iPhone will be the most up to date, followed by the main Apple Watch app, followed by the Apple Watch complication. They'll always be within 30 minutes of each other.

In any event, if you're having technical issues please feel free to email at support at meetcarrot dot com.
Click to expand...

i second what mrwilly said, this makes a lot more sense to me now! thank you
 
  • Like
Reactions: MakerOfCARROT
MakerOfCARROT said:
Is it actually "entirely different", or is it a difference of a few degrees?

Like I said above a couple times, you're not going to catch the apps with the exact same data set because they're all on different caches. When you see the main Apple Watch app update when you open it, it's not necessarily updating its data - it might just be refreshing from data already downloaded via the complication.

The main Apple Watch app also uses a complex algorithm to forecast weather data in between data refreshes to speed up load times instead of finding your GPS coordinates, downloading data from the network, then updating the UI every time, which can sometimes be very slow on the Apple Watch. So, as a simple example, if it's 70 degrees at 10am and it's forecasted to be 80 degrees at 11am, it won't continue showing 70 degrees for that entire hour - it'll be 73 degrees at 10:15, 75 degrees at 10:30, etc. It's still using the same data set as the complication, it's just forecasting out. It's so much faster doing it this way in terms of load speeds, it's ridiculous - and you get much more timely data than you would normally. And it took a ridiculous amount of time to implement on my end. (You can always do a direct refresh of the weather data using Force Touch.)

The main iPhone app doesn't use this algorithm because it doesn't have any delay in finding your GPS coordinates, downloading data, and updating its UI like the Apple Watch does - it's all instant. But for that reason, it's never going to match exactly what the main Apple Watch says.

If you're obsessively checking all 3 displays, then there will always be differences between them. The iPhone will be the most up to date, followed by the main Apple Watch app, followed by the Apple Watch complication. They'll always be within 30 minutes of each other.

In any event, if you're having technical issues please feel free to email at support at meetcarrot dot com.
Click to expand...


Thanks for taking the time to understand the platform and how to effectively give it usability. I think that most developers are just throwing something on the watch that they can put together quickly without asking themselves if it even has practical use, and bothering to dig under the covers and understand how to make it usable. Maybe you could teach classes to other developers!

And by the way, this is why I paid for your app, and haven't paid for any other apps with AW support.
 
  • Like
Reactions: ladytonya and MakerOfCARROT
Hey MakerOfCARROT, I purchased your Mac app today as well. Just one question, if I don't want the sounds in the app do I just turn all notifications off? Also, is there a way maybe in the future you can make different themes for the iOS app? Love the app, but would prefer it without the cartoonish look and would like a more basic streamlined view.
 
dictoresno said:
Hey MakerOfCARROT, I purchased your Mac app today as well. Just one question, if I don't want the sounds in the app do I just turn all notifications off? Also, is there a way maybe in the future you can make different themes for the iOS app? Love the app, but would prefer it without the cartoonish look and would like a more basic streamlined view.
Click to expand...

Awesome! There's actually a setting for sound effects on the "General" preferences tab down at the bottom, you can change that to "notifications only" so you can still get the little sound effect that plays when a severe weather or rain alert come in. And I am indeed hoping to add different themes in the future - the Mini Window is probably your best bet until then, it doesn't have any of the little comic scenes, it just focuses on the weather.
 
MakerOfCARROT said:
Awesome! There's actually a setting for sound effects on the "General" preferences tab down at the bottom, you can change that to "notifications only" so you can still get the little sound effect that plays when a severe weather or rain alert come in. And I am indeed hoping to add different themes in the future - the Mini Window is probably your best bet until then, it doesn't have any of the little comic scenes, it just focuses on the weather.
Click to expand...

Perfect!!!!!!!! I'll switch to the mini window, when I find the setting and I switched it to notifications only. And I can't wait for the themes. The comics part of the app, as amusing and funny, just isn't my style. But it's by far the most accurately updating app I have for my watch and that was my #1 need. I'll hopefully look forward to themes in the beta testing!
 
  • Like
Reactions: MakerOfCARROT
I have purchased BOTH the Mac and iOS version and I love the passion you have given the apps and the complications! now saying that I had to give up using the complications! temperature was off (+- 8 degrees) I am using the complication for weather underground (no where near as cool!) but the temp is correct.

:(
 
It could be the "feels like" versus the actual temp. Where are you located, ZebraDude?
 
05661d7599a522ee55742dd9ac81462c.jpg
fdc495d0422c8621322836bdd759cbce.jpg


So, why don't I get the rain starts and stops message?
 
Minarets said:
Why don't I get the rain starts and stops message?
Click to expand...

It depends when you look at your watch. You'd have to look at it before the rain actually starts in order to see a "rain starting in XXX minutes" message. The first screenshot you posted shows that rain has already started (and that it'll be raining for more than 1 hour). The second screenshot shows that there's a good chance of rain for the current hour, but that no actual precipitation has been detected in the area yet - if you were to open the app and look at the short-term graph, it'd be empty.
 
I think the weather provider must be having glitches. Hi today in the uk stated 24 degrees Celsius and 22 degrees on the phone app. We are lucky to get that I the summer - it's now winter! This has happened over the last few days.
 
ardsar said:
I think the weather provider must be having glitches. Hi today in the uk stated 24 degrees Celsius and 22 degrees on the phone app. We are lucky to get that I the summer - it's now winter! This has happened over the last few days.
Click to expand...

Hmm, where in the UK are you seeing this? Are you seeing the same temperatures when you go to www.forecast.io?
 
ardsar said:
Plymouth uk. Website also reporting 70 degrees F - way to high
Click to expand...

Very strange! Yeah, must be a glitch with the high for this one day, as the other days of the week look like they have the correct high/low. The hourly data suggests the high will be in the low 50s Fahrenheit. The highs/lows look fine in other cities in the UK. I'll reach out to the Forecast.io team and see if this is something they're aware of. Thanks for the heads up!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back