WearOS app for Lucid Motors' vehicles

[Lucid_LI_NY]

I completely agree with that. Simple and clean is the way to go!

 

[DeaneG]

Right now, the only changes I'm planning are:

1) Change the door locked/unlocked state indication to make that button's appearance the same as the frunk and trunk buttons. All three middle buttons will show a yellow surrounding ring when the item is open/unlocked, and no ring when closed/locked.

2) Modify the charging power display line to show the battery discharge power when RangeXChange is actively charging another vehicle.

But I have to wait a couple of days until my AI tokens get refreshed.
FWIW I had a look at the app's code (generated by Gemini Argon 4), and it's quite clean and readable, almost inviting.

 

[chazglenn3]

Tested mine today. Works great!

 

[borski]

I just built on the work of others, with the help of a week's allocation of Google's Gemini 4 Argon AI credits

Argon is genuinely so good

 

[DeaneG]

Argon is genuinely so good

I hope I didn't burn too may Argon credits asking it dumb questions like "Can you put this on Github for me?

 

[borski]

I hope I didn't burn too may Argon credits asking it dumb questions like "Can you put this on Github for me?

I might know a guy…

 

[Lucid_LI_NY]

Feature suggestion: When the car is charging, user can stop the charging by clicking the charging icon. When the icon is clicked the user get a confirmation message asking if user wants to stop charging.

 

[Aka-none]

Feature suggestion: When the car is charging, user can stop the charging by clicking the charging icon. When the icon is clicked the user get a confirmation message asking if user wants to stop charging.

As a Unix guy (not much for Linux) I, personally, prefer the not MS Windows nagging. I said it and I meant it or I wouldn’t have said it. Very few things need a confirmation. Well ok, maybe, did you really want to start ww3? That can have a confirmation, but normal activity, not sure that would be a connivance.

Do you have a particular condition in mind? Like
When the driver stops charging by pressing the button
Ask the driver if they really wanted that action.

If the driver presses confirm,
Then stop charging
Else wait for the driver to press cancel

Or if the driver presses cancel
Then stop charging

If the driver pressed stop by mistake
Then the driver presses start charging.

Would the above represent the situation you are referring to.

 

[DeaneG]

I included confirmation dialogs with the three actions (doors/frunk/trunk) that could cause a serious problem or security issue if inadvertently triggered. Watches are bumped and touched often. I think most people have glanced at theirs and found that it was somehow placed into the middle of changing a setting or cancelling an alarm, etc.

 

[DeaneG]

Feature suggestion: When the car is charging, user can stop the charging by clicking the charging icon. When the icon is clicked the user get a confirmation message asking if user wants to stop charging.

Interesting, I hadn't included this because I'm driving a Gravity now, and it has a stop-charging button at the charge port. I'd forgotten that the Air does not, and what a bother that was to deal with. I'll add it to the list of possible changes.

 

[segbrk]

I'd forgotten that the Air does not, and what a bother that was to deal with

You push the stop charging button?
In three years I never once did that, I just unplugged the cable. The clicker on the cable is designed to stop charging before the cable can be removed.

 

[DeaneG]

You push the stop charging button?
In three years I never once did that, I just unplugged the cable. The clicker on the cable is designed to stop charging before the cable can be removed.

Maybe it was during DC fast charging that the bother occurred . It's been a while and I've forgotten!

 

[Genghis]

Thanks @DeaneG ! Installed on my Samsung Galaxy Watch 8 Classic. Install and layout is simple which is great for watch apps. Just the unlock doors, which has been my number one frustration on the daily owning this car, is an awesome feature!

Notes:
1. Works with just the Bluetooth connection on my phone. Had WiFi off and no LTE on my watch when testing.
2. Inputting the login information was challenging because the textbox wouldn't show me what I was inputting in real-time. I could only see what I entered only after I hit Enter. That's when I had to go fix my errors in my email blindly again until it was correct. Password was even harder because it was masked. (Might be just the default watch keyboard and input on my Galaxy watch.) I suggest an unmask password option when entering
3. When opening the frunk for the first time, the yellow outline to give the open state on the watch is correct . After you close, it shows the yellow state on the watch even though the frunk is closed. Repeated open/close just keeps the open state on the watch app.

Other than the notes above, great work and everything else works as intended. I would be happy to donate now or purchase the app once it goes into production!

 

[DeaneG]

Thanks @DeaneG ! Installed on my Samsung Galaxy Watch 8 Classic. Install and layout is simple which is great for watch apps. Just the unlock doors, which has been my number one frustration on the daily owning this car, is an awesome feature!

Notes:
1. Works with just the Bluetooth connection on my phone. Had WiFi off and no LTE on my watch when testing.
2. Inputting the login information was challenging because the textbox wouldn't show me what I was inputting in real-time. I could only see what I entered only after I hit Enter. That's when I had to go fix my errors in my email blindly again until it was correct. Password was even harder because it was masked. (Might be just the default watch keyboard and input on my Galaxy watch.) I suggest an unmask password option when entering
3. When opening the frunk for the first time, the yellow outline to give the open state on the watch is correct . After you close, it shows the yellow state on the watch even though the frunk is closed. Repeated open/close just keeps the open state on the watch app.

Other than the notes above, great work and everything else works as intended. I would be happy to donate now or purchase the app once it goes into production!

Thank you very much for the feedback! It's very helpful to know that the watch can indeed use Bluetooth to get to the Internet via its paired phone.

I'll have a look at the emulated login screen for your watch to understand the login issue you saw. On my Pixel watch, the email address textbox is clearly visible, and the password box is also visible and has a difficult to see unmask control to the right side.

There can be a good part of a minute's delay in the car updating it's status to Lucid's cloud, and then my app only polls the cloud every seven seconds most of the time. This may be why the frunk didn't show as closed for you. I'll have a look at it again.

I'm quite divided on whether I should follow through with publishing this app. It's super useful to me and I imagine many others, so it's easy and tempting to take steps down this slippery slope.

But to publish it to a wider group, the general public, I'd have to fulfill several requirements from Google - need to establish a business website listing a privacy policy, complete an extensive formal beta test, survey the respondents, and document the results, along with some other documentation and a car emulator for Google's testers. Reasonable enough. But to be comfortable with anything beyond a limited closed test, for liability reasons I'd want to publish the product through an LLC. Though tempting and rewarding to do all this, it's probably not the best use of my days.

The program I'm distributing the app through now is intended for a limited internal (alpha) test and has a 100 user cap. After that, I didn't know where to leave it. As an apk on GitHub, to be sideloaded by the intrepid? Hope that someone else takes it over? Follow through with establishing an LLC for a hobby business, and take on long-term support?

As an aside for those with careers in software, I was a bit shocked to be typing at a CLI in a terminal window to get simple things done while building this app. I first did that almost exactly 50 years ago and am surprised that's still the process. The terminal window I'm using doesn't even support cut or paste.

 

[MacBain00]

Thank you very much for the feedback! It's very helpful to know that the watch can indeed use Bluetooth to get to the Internet via its paired phone.

I'll have a look at the emulated login screen for your watch to understand the login issue you saw. On my Pixel watch, the email address textbox is clearly visible, and the password box is also visible and has a difficult to see unmask control to the right side.

There can be a good part of a minute's delay in the car updating it's status to Lucid's cloud, and then my app only polls the cloud every seven seconds most of the time. This may be why the frunk didn't show as closed for you. I'll have a look at it again.

I'm quite divided on whether I should follow through with publishing this app. It's super useful to me and I imagine many others, so it's easy and tempting to take steps down this slippery slope.

But to publish it to a wider group, the general public, I'd have to fulfill several requirements from Google - need to establish a business website listing a privacy policy, complete an extensive formal beta test, survey the respondents, and document the results, along with some other documentation and a car emulator for Google's testers. Reasonable enough. But to be comfortable with anything beyond a limited closed test, for liability reasons I'd want to publish the product through an LLC. Though tempting and rewarding to do all this, it's probably not the best use of my days.

The program I'm distributing the app through now is intended for a limited internal (alpha) test and has a 100 user cap. After that, I didn't know where to leave it. As an apk on GitHub, to be sideloaded by the intrepid? Hope that someone else takes it over? Follow through with establishing an LLC for a hobby business, and take on long-term support?

As an aside for those with careers in software, I was a bit shocked to be typing at a CLI in a terminal window to get simple things done while building this app. I first did that almost exactly 50 years ago and I'm surprised that's still the process.

Is there any risk from Lucid asking the app to be pulled? The saying "No good deeds something something"

I would say is to make an open-source GitHub repo with all the necessary legal jargin that Gemini or your AI of choice can spit out. Let people build on your work versus worrying about how to gatekeep it.

 

[DeaneG]

Is there any risk from Lucid asking the app to be pulled? The saying "No good deeds something something".
I would say is to make an open-source GitHub repo with all the necessary legal jargin that Gemini or your AI of choice can spit out. Let people build on your work versus worrying about how to gatekeep it.

Yes, certainly, though I suspect they have enough on their plate already.
If they do ask, I'll pull it from the internal-test play store and ask each tester to uninstall it.

I'm leaning toward the long-term approach you suggested.

 

[Lucid_LI_NY]

Interesting, I hadn't included this because I'm driving a Gravity now, and it has a stop-charging button at the charge port. I'd forgotten that the Air does not, and what a bother that was to deal with. I'll add it to the list of possible changes.

Yep, Lucid Air doesn't have that and the watch could be a good way to stop charging. Thanks!

 

[segbrk]

IANAL, but as long as you're clear that it's a third-party app for Lucid rather than a Lucid app, there's no reason they should ask to take it down. That includes using Lucid's logo(s) though. I suspect if you publish the source, someone here who's already comfortable with publishing to the Play Store would be willing and able to do the final bit.

 

[DeaneG]

IANAL, but as long as you're clear that it's a third-party app for Lucid rather than a Lucid app, there's no reason they should ask to take it down. That includes using Lucid's logo(s) though. I suspect if you publish the source, someone here who's already comfortable with publishing to the Play Store would be willing and able to do the final bit.

I wasn't sure about using the bear as the app's logo, but it's certainly not the first California bear to appear anywhere. Thought I'd change it to a car in a cloud graphic if it became an issue.

Google's Argon 4 gave me some unsolicited but helpful advice on these considerations when I asked it to make a release build.

 

[eelpout]

This demonstrates that Lucid is inadequate regarding software.

Tesla already has an iPhone Duo formatted version of their iOS app.

Folding Android phones on the other hand... what are those???