Ostrichsak
Well-known member
This thread was inspired by someone recently saying that there's an update for the iOS version of the app and hoping that it will fix this issue.
TBH, I'm not sure that an app update is the solution to the lack of notification problem at all.
The problem is most likely on the sever-end so a simple app update isn't going to solve a problem. The problem is that the app isn't getting access to data in the first place, not how the app processes said data once it has it. If it were the latter (rather than the former) an app update could potentially solve it. Based on what I'm seeing, it certainly feels like they're headend server assets aren't up to the job required during high-traffic times.
(WARNING: conjecture in this paragraph, skip to the next one if you can't handle hearing constructive criticism of RT based on the facts present) Regardless of what these resources look like (people always want to attack me for assuming it's 3rd party cloud-based virtual server providers like AWS and what their particular plan provides in term of server capabilities since it's the most common/likely) the answer in these instances is almost always more money will fix the problem. They either need to beef up whatever their virtual or physical service solution is, the bandwidth connecting to the world wide web or possibly a combination of the above. That's what's most frustrating about this is that RT doesn't see it as being enough of a problem (largely due to all of the white knights defending what's clearly a broken product anytime someone tries to publicize these shortcomings) to loosen the purse strings to meet the promises of features that brought in that revenue in the first place. Taken at face value this feels awfully greedy to me. In a complete vacuum of any official word from RT what are we supposed to do other than draw a conclusion based on the most likely scenario given what we know? Other than recognizing the issues exist and promising it will be dealt with before the next high-volume/holiday weekend which has been officially been over a year ago since the firs time this problem was noted wide-spread was on Super Bowl weekend 2021, what has RT done? These app updates are simple and inexpensive compared to what the real solution will likely cost but it also serves to make the general populace "feel" like they're putting effort forth when in reality they really aren't. A high school kid could update an app in their spare time but bolstering the solution necessary to support these features is a much different story. I mean, the only other option here after over a year is that it's not a money thing and they're just grossly incompetent. Try to keep those two options in mind whenever you defend RT by saying I'm wrong and attacking me personally on what I believe to be the issue.
They seem to not have their sever-end bolstered enough to process the bandwidth. Due to this, I'm not confident that an app update is going to resolve the heart of the issues. It's mostly just window dressing which is why we still have it well over a year later now.
About the ONLY app update that could potentially correct these symptoms we're seeing would be a wholesale change that fundamentally modifies how the app receives data in the first place which would mean a local-only based solution. So in other words, the smoker wouldn't "call home" to transmit data to the RT servers which then serve it back up to the app as needed. There are some negatives to this type of solution as well but, for me, I'd rather have the thing work at a basic level consistently than have it not work reliably but also have more advanced features that also don't work reliably.
Much of this is said at a basic level to try to engage all of those who are experiencing this issue so if you're more technical please don't bash me for over-simplification. This was done intentionally to include everyone who owns one of these smokers who is attempting to understand what the issues are and how they can be fixed.
Ultimately, I truly hope that I'm wrong and that they can simply fix this once and for all and make it 100% reliable through a simple front-end software adjustment via an app update. Nothing would make me happier as a RT-590 owner. I don't think that I'm wrong though and I believe that our problems will persist until RT actually wants to fix the problem, sadly.
TBH, I'm not sure that an app update is the solution to the lack of notification problem at all.
The problem is most likely on the sever-end so a simple app update isn't going to solve a problem. The problem is that the app isn't getting access to data in the first place, not how the app processes said data once it has it. If it were the latter (rather than the former) an app update could potentially solve it. Based on what I'm seeing, it certainly feels like they're headend server assets aren't up to the job required during high-traffic times.
(WARNING: conjecture in this paragraph, skip to the next one if you can't handle hearing constructive criticism of RT based on the facts present) Regardless of what these resources look like (people always want to attack me for assuming it's 3rd party cloud-based virtual server providers like AWS and what their particular plan provides in term of server capabilities since it's the most common/likely) the answer in these instances is almost always more money will fix the problem. They either need to beef up whatever their virtual or physical service solution is, the bandwidth connecting to the world wide web or possibly a combination of the above. That's what's most frustrating about this is that RT doesn't see it as being enough of a problem (largely due to all of the white knights defending what's clearly a broken product anytime someone tries to publicize these shortcomings) to loosen the purse strings to meet the promises of features that brought in that revenue in the first place. Taken at face value this feels awfully greedy to me. In a complete vacuum of any official word from RT what are we supposed to do other than draw a conclusion based on the most likely scenario given what we know? Other than recognizing the issues exist and promising it will be dealt with before the next high-volume/holiday weekend which has been officially been over a year ago since the firs time this problem was noted wide-spread was on Super Bowl weekend 2021, what has RT done? These app updates are simple and inexpensive compared to what the real solution will likely cost but it also serves to make the general populace "feel" like they're putting effort forth when in reality they really aren't. A high school kid could update an app in their spare time but bolstering the solution necessary to support these features is a much different story. I mean, the only other option here after over a year is that it's not a money thing and they're just grossly incompetent. Try to keep those two options in mind whenever you defend RT by saying I'm wrong and attacking me personally on what I believe to be the issue.
They seem to not have their sever-end bolstered enough to process the bandwidth. Due to this, I'm not confident that an app update is going to resolve the heart of the issues. It's mostly just window dressing which is why we still have it well over a year later now.
About the ONLY app update that could potentially correct these symptoms we're seeing would be a wholesale change that fundamentally modifies how the app receives data in the first place which would mean a local-only based solution. So in other words, the smoker wouldn't "call home" to transmit data to the RT servers which then serve it back up to the app as needed. There are some negatives to this type of solution as well but, for me, I'd rather have the thing work at a basic level consistently than have it not work reliably but also have more advanced features that also don't work reliably.
Much of this is said at a basic level to try to engage all of those who are experiencing this issue so if you're more technical please don't bash me for over-simplification. This was done intentionally to include everyone who owns one of these smokers who is attempting to understand what the issues are and how they can be fixed.
Ultimately, I truly hope that I'm wrong and that they can simply fix this once and for all and make it 100% reliable through a simple front-end software adjustment via an app update. Nothing would make me happier as a RT-590 owner. I don't think that I'm wrong though and I believe that our problems will persist until RT actually wants to fix the problem, sadly.
