What would you like to see from the Lucid mobile app?

[borski]

The nav input is nice.
I have tire pressure on the EQS phone app but no nav.

You can do navigation input on the Lucid app as well.

 

[Charlie9008]

Ability to trigger battery conditioning. I don’t like having to turn off radio every time I enter the car, why can’t this be part of my profile? Ability to open and close garage door as I approach and depart the garage. Thanks!

 

[EVCar]

You can do navigation input on the Lucid app as well.

I’m clueless on how to do this.

 

[Negan1000]

You can do navigation input on the Lucid app as well.

It does not work on iOS mobile app. I use google maps to sent nav address to my car.

 

[Bobby]

It does not work on iOS mobile app. I use google maps to sent nav address to my car.

I’ve used it on the iOS app multiple times. I haven’t had an issue with it working. What happens when you try?

 

[Tim-in-CA]

I’ve used it on the iOS app multiple times. I haven’t had an issue with it working. What happens when you try?

I can concur. Spinner just gets stuck. Only way to send an address to the car for me is via Google or Apple Maps

 

[Bus Driver]

It does not work on iOS mobile app. I use google maps to sent nav address to my car.

I use the the map function on my iphone and ipad all the time. Never had any problems sending their directions to my Lucid.

 

[lsbuffs]

I can concur. Spinner just gets stuck. Only way to send an address to the car for me is via Google or Apple Maps

Same, spinner as soon as I try. Recent update didn't resolve. Not sure why many people have this issue and others do not.

 

[Lucken]

Same, spinner as soon as I try. Recent update didn't resolve. Not sure why many people have this issue and others do not.

Does everyone with the issue have the same iOS version? I could see different iOS versions impacting results.

 

[borski]

Works perfectly fine for me from the Lucid app. I know that @HariK was having issues with it previously so perhaps it is buggy for some.

 

[GMan]

Does everyone with the issue have the same iOS version? I could see different iOS versions impacting results.

I get the spinning as well, and that's on Android. So, I don't think iOS version specific. I have to kill the app and restart it to use the app but sending nav to the car from the app has never worked for me.

Instead, I just use Google maps and bluetooth the audio. Not quite Android Auto but it gets me there.

 

[HariK]

I get the spinning as well, and that's on Android. So, I don't think iOS version specific. I have to kill the app and restart it to use the app but sending nav to the car from the app has never worked for me.

Instead, I just use Google maps and bluetooth the audio. Not quite Android Auto but it gets me there.

Also finding a location on Google maps and sharing it to lucid works every single time. So no real advantage using the lucid app to find a place to navigate. Also Alexa did not navigate to a name in my contact list but Google does.

 

[Tesla2.0]

IMO, Lucid Mobile app with iOS widget option is ahead of competitors. However, I like to see Lucid succeed and have useful features of other EV mobile apps, such as the following in Rivian.

Wish List:
Mobile app shows charging curve in minute increments.

Even Level-2 charging shows charging curve.

 

[Tex_Lucid]

It does not work on iOS mobile app. I use google maps to sent nav address to my car.

Never worked for me either

 

[Adnillien]

Has anyone noticed that there is difference between the charging rate shown in the App and in the widget. See below where the app show 6kW and widget shows 5kW. It looks to me like the app is showing the power into the car and the widget is showing the power into the battery. The app shows a charge rate of 22mph and at the EPA standard 4.2mi/kWhr, gives 5.2kW. My question is why are they different and I would like the app to show both the power into the car and the power into the battery so we could see what was lost in conversion and battery management.

 

[Tesla2.0]

Has anyone noticed that there is difference between the charging rate shown in the App and in the widget. See below where the app show 6kW and widget shows 5kW. It looks to me like the app is showing the power into the car and the widget is showing the power into the battery. The app shows a charge rate of 22mph and at the EPA standard 4.2mi/kWhr, gives 5.2kW. My question is why are they different and I would like the app to show both the power into the car and the power into the battery so we could see what was lost in conversion and battery management.

View attachment 9551View attachment 9552

I think it may be just programming issue. One may be using accounting library of RoundUp(X), the other one is doing Truncate(X). I wouldn’t be too concerned.

 

[njg-agt]

I think it may be just programming issue. One may be using accounting library of RoundUp(X), the other one is doing Truncate(X). I wouldn’t be too concerned.

When you wear two watches, you know not what time it is...

 

[joec]

Widgets can only be updated every so often. They are not "live" data. (The timer appears to be constantly updating, but what it gets from the app is a "start" time, and then the count up is happening via the system. Could be as simple as the widget is showing what the charging status was ten minutes ago.

Also wouldn't be surprised if they are calculating it two different ways, as suggested as well.

 

[Tesla2.0]

When you wear two watches, you know not what time it is...

When I wear 2 watches, it’s about fashion statement, not about time.

 

[Tesla2.0]

Widgets can only be updated every so often. They are not "live" data. (The timer appears to be constantly updating, but what it gets from the app is a "start" time, and then the count up is happening via the system. Could be as simple as the widget is showing what the charging status was ten minutes ago.

Also wouldn't be surprised if they are calculating it two different ways, as suggested as well.

Which I suggested in software suggestion thread like in Rivian mobile app, plot charging rate at minute interval for charging curve.