No, you no longer need the Mac app if you upgrade to premium - the notifications are now handled by the phone/watch, since the complications in watchOS 3 allow the app to run in the background and check the weather throughout the day.
Got a tip for us?
Let us know
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
- Thread starter MakerOfCARROT
- Start date
- Sort by reaction score
No, you no longer need the Mac app if you upgrade to premium - the notifications are now handled by the phone/watch, since the complications in watchOS 3 allow the app to run in the background and check the weather throughout the day.
Thanks. And your scary fast response time alone deserves an IAP! Seriously good support!
Thanks!
These past couple updates have really improved the sync with the Watch. Now when I launch the app on the watch, I have confidence that it's the most up-to-date condition, and don't have to wait or force a refresh.
I just bought Carrot a few minutes ago. Mostly due to the good reviews, and I recently purchase an Apple watch. Dark Sky wasn't working out well with the watch, so thought I'd make a change. Can you tell me what the $2.49 yearly fee enhances for the complication? Thank you.
The subscription adds more frequent data updates (every 30 minutes), notifications (precipitation, severe weather alert, and morning and evening reports), and the ability to customize your complications with lots of different data points.
There's a lot more detail here if you're interested: http://support.meetcarrot.com/weather/subscription-mobile.html
Hope you enjoy the app!
@MakerOfCARROT
Just wanted to drop in and say that I've been using this app on the iPhone and Watch with the IAP for the past few days and must say that I am very pleased. The complication updates regularly and you have a force-touch Update option in the app itself - I love this! I also like the customizable complications.
No rain in my area yet so I can't test that although I did get a rain notification and there was a very light sun drizzle when I took out the garbage, so it does seem good at predictors.
Just wanted to drop in and say that I've been using this app on the iPhone and Watch with the IAP for the past few days and must say that I am very pleased. The complication updates regularly and you have a force-touch Update option in the app itself - I love this! I also like the customizable complications.
No rain in my area yet so I can't test that although I did get a rain notification and there was a very light sun drizzle when I took out the garbage, so it does seem good at predictors.
Just realised that my Premium version of the app expires today. I'm assuming that it will auto-renew?
No, the version you purchased last year was a non-renewing subscription. Apple changed their policies this year to allow more apps to use auto-renewing subscriptions, so I switched to that in version 3.0. So that means you'll have to renew your subscription manually this time, but *next time* it will renew automatically.
Can't see how to do this within the app. Redownload the app and pay there? I'm in the beta test programme.
Ah yeah, you do need to download the official version from the App Store. You can renew by going to the premium section at the top of the settings screen - once the subscription expires, you'll get an option to purchase the auto-renewing one.
Got it thanks, and presumably I then go to TestFlight for the latest beta, or do I have to reapply?
You'll be able to redownload from TestFlight without reapplying, but the beta isn't currently active since I just put the latest version live on the App Store last week. You'll get an email the next time I start up the beta, probably sometime next week.
I have a question/comment, but I'm afraid it might seem nitpicky... feel free to ignore me.
As we move in to the time of year where I'm more interested in the lows than the highs, I noticed that CARROT presents its information a little differently than other weather apps. Specifically, when CARROT lists the HI/LO for each day, it is presenting the range of temperatures for that day, regardless of when each extreme occurs, rather than showing the high for the day and the following overnight low, which is conventional.
In other words, let's say the temperature ranges for the next few days look like this assuming the lowest temperature is at 7am and the highest temperature is at 4pm:
Th: 49 to 78
Fr: 51 to 84
Sa: 54 to 83
Su: 55 to 78
So an app that presents the temps as a daily range (like Dark Sky) would use those numbers as-is. However, other apps and sources (like your local 6 o'clock news) that use a HI/LO format would list the highest temp for the day and then the following overnight low (even though that technically occurs on the next day), like this:
Th: 78/51
Fr: 84/54
Sa: 83/55
However, CARROT still uses the ranges even though it presents the information in HI/LO format, so it looks like this:
Th: 78/49
Fr: 84/51
Sa: 83/54
So I'm just wondering if that was intentional, or an oversight, somewhere in between, or maybe I just poked CARROT's ocular sensor too many times and now she's messing with me...
As we move in to the time of year where I'm more interested in the lows than the highs, I noticed that CARROT presents its information a little differently than other weather apps. Specifically, when CARROT lists the HI/LO for each day, it is presenting the range of temperatures for that day, regardless of when each extreme occurs, rather than showing the high for the day and the following overnight low, which is conventional.
In other words, let's say the temperature ranges for the next few days look like this assuming the lowest temperature is at 7am and the highest temperature is at 4pm:
Th: 49 to 78
Fr: 51 to 84
Sa: 54 to 83
Su: 55 to 78
So an app that presents the temps as a daily range (like Dark Sky) would use those numbers as-is. However, other apps and sources (like your local 6 o'clock news) that use a HI/LO format would list the highest temp for the day and then the following overnight low (even though that technically occurs on the next day), like this:
Th: 78/51
Fr: 84/54
Sa: 83/55
However, CARROT still uses the ranges even though it presents the information in HI/LO format, so it looks like this:
Th: 78/49
Fr: 84/51
Sa: 83/54
So I'm just wondering if that was intentional, or an oversight, somewhere in between, or maybe I just poked CARROT's ocular sensor too many times and now she's messing with me...
Someone actually just brought that up this past week with me - weird that no one mentioned it before! I agree and will be changing that for the next update.
I have a question/comment, but I'm afraid it might seem nitpicky... feel free to ignore me.
As we move in to the time of year where I'm more interested in the lows than the highs, I noticed that CARROT presents its information a little differently than other weather apps. Specifically, when CARROT lists the HI/LO for each day, it is presenting the range of temperatures for that day, regardless of when each extreme occurs, rather than showing the high for the day and the following overnight low, which is conventional.
In other words, let's say the temperature ranges for the next few days look like this assuming the lowest temperature is at 7am and the highest temperature is at 4pm:
Th: 49 to 78
Fr: 51 to 84
Sa: 54 to 83
Su: 55 to 78
So an app that presents the temps as a daily range (like Dark Sky) would use those numbers as-is. However, other apps and sources (like your local 6 o'clock news) that use a HI/LO format would list the highest temp for the day and then the following overnight low (even though that technically occurs on the next day), like this:
Th: 78/51
Fr: 84/54
Sa: 83/55
However, CARROT still uses the ranges even though it presents the information in HI/LO format, so it looks like this:
Th: 78/49
Fr: 84/51
Sa: 83/54
So I'm just wondering if that was intentional, or an oversight, somewhere in between, or maybe I just poked CARROT's ocular sensor too many times and now she's messing with me...
i'm not sure if i'm misunderstanding this as i'm not used to checking the weather on the 6 o clock news (too young for that) but in the extreme lets say there was a massive cold snap from 11pm friday to 7am saturday with temps of 40.
Carrot would then show
Th: 78/51
Fr: 84/40
Sa: 83/40
when it should disregard that temperature on the saturday "low", right?
It's an interesting point that's been raised. I've never been completely sure that the low for a particular day referred to the temperature from early morning that day, or late evening of the same day.
One point of confusion on this is that the daily low usually occurs first in the day (usually the hour of sunrise). So, if you were doing it temporally, you'd go with the low first, then the high. But that's not how we (at least here in the US) are accustomed to thinking about it: we think of hitting a high for the day and then sliding down to the low temp somewhere in the hours when we are asleep. So, for practical purposes, its not the "next day" its just the end of the cycle of high/low. And then the cycle begins anew, coinciding with our wake/sleep cycle. That is why I think it is customarily listed this way.
I support the change to this format.
I don't understand the pricing scheme. It's 3.99 for the iPhone app, then an additional 1.99/year for the watch complications. Then there is a premium upgrade for 2.49, what is that? Is the original 3.99 per year, or just once and includes all future updates?
I agree. If I get up at 7am, I can determine the current temperature immediately. I'm more likely to be interested in the conditions for the remainder of the day, and, at this time of year, if a frost is likely in the evening hours.
$3.99 to buy and then $2.49 per year. you can't buy the $1.99 one anymore, it's the old pricing.
Bleh I hate in app gouging subscriptions. I know it's a small amount of money, but I don't buy them on principle. I'd prefer just to have a lifetime price, even if it ends up being more expensive.
I'd honestly rather not have a subscription, but I really didn't have a choice here. Each request to my weather data provider costs a small amount of money, and it quickly adds up with the Apple Watch complication updating every half hour of every day. It was either include a subscription to offset this cost or not offer an Apple Watch app at all. I think all my users would agree that I made the right choice