Please check out the 76 pages of discussion on this topic here.There was supposed to be an update by the end of the year that would include Android Auto.
5785 ends at sunset on September 22, 2025Please check out the 76 pages of discussion on this topic here.
Seen it all. What's your point?Please check out the 76 pages of discussion on this topic here.
The point is it’s delayed and are waiting on Google certification before roll out. Hopefully, we are closer for AA as there was a beta mobile app for Android posted by someone here.Seen it all. What's your point?
Always and forever the calming and soothing voice (or written word) of reason on here, joec! Always putting things in perspective!Think of a software engineering team as a boat, not a car. It doesn't stop or turn on a dime. And the bigger the boat, the longer it takes to do either.
I'd argue the team has had a lot on its plate and has actually produced quite a bit of software in the past six months. The entire Gravity platform, for one.
It just feels slow to us because we want everything now, now, now.
But that's just not reality.
I'm sure the changes that were made back when Peter made that announcement about dedicating more attention to software will pay off in dividends throughout this year. But it was always going to take a while before that decision started bearing fruit.
It depends on the task, but often one team will be responsible for a certain functionality across all products - a team for Android Auto for both Air and Gravity, for example, or navigation, or media apps, or drivetrain/traction control/etc, battery management, audio, HVAC, ADAS, UX.I’m not in software and I’m completely ignorant to what it takes to get a polished product to market. Honest question… would auto manufacturers like Lucid have multiple teams working the different software packages? Like one for Gravity, one for Air and one for App development? Or would one team share the workload?
There is probably some overlap, but there’s more than one way to run this kind of team, and multiple of them “work.” I’m not sure where they share responsibility or how they’ve split it. It’s a good question, though not necessarily indicative of level of competence or anything like that.It depends on the task, but often one team will be responsible for a certain functionality across all products - a team for Android Auto for both Air and Gravity, for example, or navigation, or media apps, or drivetrain/traction control/etc, battery management, audio, HVAC, ADAS, UX.
There are different engineering teams responsible for each necessary platform. So there are engineers responsible for the HMI software, a team for each computer within the vehicle, of which there are many, like the TCU, ACM, BCM, etc. There is a mobile team for both main mobile platforms. There are Cloud engineers handling an extremely broad range of communications from and between those different platforms.It depends on the task, but often one team will be responsible for a certain functionality across all products - a team for Android Auto for both Air and Gravity, for example, or navigation, or media apps, or drivetrain/traction control/etc, battery management, audio, HVAC, ADAS, UX.
Having managed engineering for my career - discount by 14 days for the holiday season.Tomorrow we tie the most prolonged period between non-feature OTA updates. Hope that means a big feature update is coming as our next OTA update.
How much slower do you want them to go!? They already did it your way with a snails pace of OTAs over 2024. And it's still riddled with instability. I'll take more frequent updates at this point!I'll take a slower pace of OTA's over more frequent updates that need patches to regain all the functionality I had before the update. For the love of all things holy, introduce more robustness, all the robustnesses!!!
Yes, Lucid please don't drag this things further. Your delays are making the competition catchup on the driving dynamics and it will be too late to fix the consumer sentiment by then.I mean they did it your way with a snails pace of OTAs over 2024. And it's still riddled with instability. I'll take more frequent updates at this point!
Yea ive given up on that ever happening. The fact that they completely changed the orientation and everything. It’s not going to happen. Just like when Tesla released the model 3/Y, all their investment went into landscape UI enhancements. The portrait UI of the legacy S/X became second fiddle. Even though they still get some of the updates, it’s very obviously the unloved child of the software team lolWe need update to gravity UX
We’ll see. I disagree with your assumption. I think the coming update is taking longer BECAUSE it’s going to incorporate most of the features in Gravity. We’ll see. Respectfully, I hope you are wrong. I am basing my assumption on several interviews with Peter Rawlinson in which he indicated as much…Yea ive given up on that ever happening. The fact that they completely changed the orientation and everything. It’s not going to happen. Just like when Tesla released the model 3/Y, all their investment went into landscape UI enhancements. The portrait UI of the legacy S/X became second fiddle. Even though they still get some of the updates, it’s very obviously the unloved child of the software team lol