What to Include When Submitting SW Feedback

marqie

(they/them)
LUCID Team Member

LUCID Official
Joined
Nov 22, 2021
Messages
958
Reaction score
3,934
Location
Newark, CA
Thank you to everyone who has taken the time to share software feedback with us at [email protected]. Your insights play an important role in helping us enhance your ownership experience.

When submitting software feedback, please be sure to include the following details to help the team with their review:
  • VIN
  • Software version
  • Timestamp of the concern
  • Any additional context or relevant information
  • Pictures if available (can be super helpful)
We will reach out if additional information is needed. If your vehicle requires service, please contact your local Service Center directly. For other support, contact Lucid Customer Care at [email protected] or 1‑888‑995‑8243.

Thank you again for your continued partnership.

Software feature requests submitted to [email protected] are also welcome.
 
Last edited:
Thanks, @marqie !

One question -- is there any guidance on the sort of level of reports Lucid is interested in? There's a lot of little things that I assume are already known so I haven't considered reporting them (apps on the pilot panel "freeze", buttons not always drawn, HVAC greyed-out status is inconsistent, fob batteries still only last 3 months, etc). Maybe a list of "known bugs" so we can not waste time reporting them again?
 
Thanks, @marqie !

One question -- is there any guidance on the sort of level of reports Lucid is interested in? There's a lot of little things that I assume are already known so I haven't considered reporting them (apps on the pilot panel "freeze", buttons not always drawn, HVAC greyed-out status is inconsistent, fob batteries still only last 3 months, etc). Maybe a list of "known bugs" so we can not waste time reporting them again?
Reporting these issues is helpful. I would just ask to provide as much context (timestamp, pictures, etc.) as you are able to and indicate whether the issue can be replicated.
 
Would be easier to make this a feature in the app so information is automatically shared. Having all these parameters requires significant effort on the user side. Does this mean that if I have submitted issues without some of these parameters it's being ignored? Once I received acknowledgement of a submission but of the dozen or so submissions no response.
 
Would be easier to make this a feature in the app so information is automatically shared. Having all these parameters requires significant effort on the user side. Does this mean that if I have submitted issues without some of these parameters it's being ignored? Once I received acknowledgement of a submission but of the dozen or so submissions no response.
100% a feedback function in the phone app would be ideal, and if done right would make things so much easier for both the customer and the software engineers.

For the software team, the feedback would already be in an easily managed format (eg. JSON) with required information and metadata (eg. VIN, car firmware, app certain, user's email, etc) fields consistently included and formatted, which would make processing, collating, and prioritizing the feedback dead simple.

For the user, it could (and should) guide the user through providing useful information about their issue, which also ensures the feedback provided is actually useful to the engineers.

If they don't already have someone working on something like that, then they desperately need to hire someone who knows what they're doing.

Then again, at the show rooms, they're still tracking available sales inventory with a spreadsheet, so maybe I'm expecting too much from them at this stage.
 
100% a feedback function in the phone app would be ideal, and if done right would make things so much easier for both the customer and the software engineers.

...

If they don't already have someone working on something like that, then they desperately need to hire someone who knows what they're doing.

...
Someone will correct me if I am misremembering, but if I recall correctly, Nick Twork has publicly stated that Lucid is working on a button that would allow you to submit feedback or bug reports directly from the vehicle itself; something in the mobile app would be a natural companion to in-vehicle bug submission.
 
What about this idea?



Someone will correct me if I am misremembering, but if I recall correctly, Nick Twork has publicly stated that Lucid is working on a button that would allow you to submit feedback or bug reports directly from the vehicle itself; something in the mobile app would be a natural companion to in-vehicle bug submission.

A bug reporter from the phone...?
 
Tesla has had the ability for quite some time to submit a bug report directly from the car while you are driving. You just hit the microphone button and say "Bug report" and then add the appropriate description.
 
Tesla has had the ability for quite some time to submit a bug report directly from the car while you are driving. You just hit the microphone button and say "Bug report" and then add the appropriate description.

Hah, no idea how well that works in the end. The speech to text is horrible and the bug report often has nonsense attached to it because it doesn't understand anything I said. When the FSD beta was enabled on my car (I have since disabled it because v14 is unusable due to the lack of speed control) I was attempting to file a bug 2-3 times each drive and most of the time I gave up in frustration because it would even miss me saying bug report.

I much prefer the email method that Lucid is providing. I can note the time it happened mentally and send a quick email once I have a chance. It also allows me to go into deeper detail as to what the exact issue is, attach photos, etc. I just wish they would provide a bit more feedback on the status.
 
The advantage to a bug report sent from the vehicle itself is the reporter service could send data that's not necessarily available to the user (software logs and such) automatically as part of the bug report.
 
Ford has a really cool way to send suggestions built right into their car multimedia. Not just bug reports but also likes dislikes and feature suggestions it’s really intuitive and can even be done while driving.

Would be amazing if lucid could integrate this into their ai companion so that not only could it send recorded summarized feedback but also include diagnostic data from the car if the issue was a bug.
 

Attachments

  • IMG_6949.webp
    IMG_6949.webp
    929 KB · Views: 63
  • IMG_6950.webp
    IMG_6950.webp
    3.9 MB · Views: 74
I know that bug tracking is strictly internal to people who need to know but no one else. I wouldn’t want my issues available to my competitors.
And I do think it would b sweet if a confirmation of submissions were implemented. Maybe even with a bug number that could be referenced in the release notes?
Just thinking out loud
 
Good afternoon

May international owners contribute and send feedbacks/request as well?
 
I know that bug tracking is strictly internal to people who need to know but no one else. I wouldn’t want my issues available to my competitors.
And I do think it would b sweet if a confirmation of submissions were implemented. Maybe even with a bug number that could be referenced in the release notes?
Just thinking out loud
Thank you for this feedback. I will pass it along to the team.
 
Thank you to everyone who has taken the time to share software feedback with us at [email protected]. Your insights play an important role in helping us enhance your ownership experience.

When submitting software feedback, please be sure to include the following details to help the team with their review:
  • VIN
  • Software version
  • Timestamp of the concern
  • Any additional context or relevant information
  • Pictures if available (can be super helpful)
We will reach out if additional information is needed. If your vehicle requires service, please contact your local Service Center directly. For other support, contact Lucid Customer Care at [email protected] or 1‑888‑995‑8243.

Thank you again for your continued partnership.
So simply saying, “Zed, we have a bug“ Is insufficient, I guess. Seriously, bringing this up now is interesting timing. Between the lines, it seems to communicate that there is even more interest internally in getting things squared away software-wise. I take this as an encouraging sign. 2.9 and 2.10 in fairly rapid succession is encouraging to me as an Air owner.
 
Last edited:
Back
Top