User reviews paint a picture of an app that has accumulated significant technical debt. The frequent failures, slow performance, and login issues suggest that the underlying codebase is not being properly maintained. Customer support, when contacted, often gives generic advice like "check if your doors are locked" — a response that insults users' intelligence and does nothing to solve the problem. The app's developers seem to be in a reactive mode, releasing generic "optimization" updates without addressing the root causes of the failures. The app's Android 8.1+ requirement and 114.61 MB file size are standard, but they don't excuse the poor performance. The app's integration with WearOS is a nice addition, but it's a secondary feature that doesn't compensate for the primary function failures. The app's user interface, when it works, is clean and functional. But the consistent unreliability overshadows any design positives. The real kicker is that the app's remote start function requires the vehicle to have a cellular signal, and in many parts of Canada, especially rural areas, that signal is weak or non-existent. This means the app can fail simply because the car cannot communicate with the server. Users have reported that the app frequently displays a "Vehicle is in use" error even when the car is parked and locked, which prevents remote start. This error is not explained by any official documentation, and support agents typically ask users to check if the doors are closed. The app also lacks a proper offline mode, so if you have no internet connection, you are locked out of all functions, including checking your tire pressure or odometer reading. This dependency on constant connectivity makes the app useless in situations where you need it most — like when you are in a parking garage with no signal. The app's reliance on cloud services introduces latency; a simple lock or unlock command can take up to 15 seconds to execute. This might not sound like much, but when you are standing in the rain, waiting for your car to unlock, 15 seconds feels like an eternity. The app does not provide any feedback on why a command fails. You get a generic "Failed" message, with no indication whether it's a network issue, a car-side problem, or a server-side outage. This lack of transparency makes troubleshooting impossible. The app has remained in this state for years, with each update bringing only vague promises of improvements that never materialize. The final technical detail is this: the app version 9.9.91, released on June 16, 2026, still suffers from the same reliability issues that were reported years ago, and the changelog's "optimizations and improvements" have done nothing to fix the core problem of remote commands failing to execute.
