Lucid app update v1.49.0

The prior versions all used a “translation framework” (I’m oversimplifying here on purpose) called Flutter; the idea is that you write code once, and then can deploy it to both Android and iOS (and web, or other devices, or whatever).

The benefit is flexibility - no need to maintain multiple codebases, only have to build a feature once, fix a single bug, and so on.

The drawback is speed (because everything is a little slower due to it not using the “native” iOS APIs), consistency (because you are using neither Android nor iOS, really, but using a layer in between), and limits on how deep of the system you can use and access.

Basically, everything about a native app is superior, except that you have to maintain both it and an Android app separately.

I hate Flutter, because native apps just perform so much better; but for speed of development, I understand why people use Flutter. It lets you build both apps in “half the time” with “half the effort.”

But the technical debt you incur while doing that? That takes years to pay back. :)
This was oversimplified?!? 😂
 
Switching cars does not show correct color. GT is black (default color?) but the Pure is… orange?!? @hydbob lol
IMG_5367.jpeg
 
This was oversimplified?!? 😂
OK, let me try again:

old app bad. new app good; much better. such wow.
old app flutter like birds, but they've flown the coop.
new coop full of new, native birds, better suited for old land.
native birds live longer, fly faster and further, and require less food.

better?
 
OK, let me try again:

old app bad. new app good; much better. such wow.
old app flutter like birds, but they've flown the coop.
new coop full of new, native birds, better suited for old land.
native birds live longer, fly faster and further, and require less food.

better?
I understood all of those words!

In other news…. Both cars just woke up when I got close to them. Sooooo…. I think the new much gooder app fixed the problem of having to switch cars before it recognizes the phone. Waaayyyy better! Both our phones independently worked opening both cars no matter which care was selected in-app.

I’m ready for Gracity 🫡
 
I like the update. Need the correct wheels to show properly, at least the 20’s aren’t showing, instead shows 21” aero blades
 
You have to delete your old widgets, and reinstall them from this new version of the app. They should work flawlessly.
1.5hrs and the mid size widget still on 😀
 
I like the update. Need the correct wheels to show properly, at least the 20’s aren’t showing, instead shows 21” aero blades
Did your car originally get delivered with the 21” aero blades?

What wheels does it say you have when you check the details at https://testmycode.cc?

Look for either:
<class 'vehicle_state_service_pb2.Vehicle'>:

Field 8, wheels: WHEELS_DREAM (1)


In the gRPC API response, or:
"userVehicleData": [
{

"wheels": "DREAM",


In the JSON API response.
 
Last edited:
OK, let me try again:

old app bad. new app good; much better. such wow.
old app flutter like birds, but they've flown the coop.
new coop full of new, native birds, better suited for old land.
native birds live longer, fly faster and further, and require less food.

better?
How about in the form of a haiku?
 
How about in the form of a haiku?
Ask and ye shall receive.

Old app fluttered, gone,
New coop with native birds,
Longer life, faster flight.

Or, perhaps:

Flutter's tangled mesh,
Slows, restricts, native's finesse,
Debt accrues, progress less.

:)
 
Fantastic update. One my only gripes with Lucid was how the mobile app performed but it's silky smooth now.
 
Has anyone received this update for Android yet? I've been refreshing the app store to check but no dice for me so far...Pixel 8 Pro here
 
The prior versions all used a “translation framework” (I’m oversimplifying here on purpose) called Flutter; the idea is that you write code once, and then can deploy it to both Android and iOS (and web, or other devices, or whatever).

The benefit is flexibility - no need to maintain multiple codebases, only have to build a feature once, fix a single bug, and so on.

The drawback is speed (because everything is a little slower due to it not using the “native” iOS APIs), consistency (because you are using neither Android nor iOS, really, but using a layer in between), and limits on how deep of the system you can use and access.

Basically, everything about a native app is superior, except that you have to maintain both it and an Android app separately.

I hate Flutter, because native apps just perform so much better; but for speed of development, I understand why people use Flutter. It lets you build both apps in “half the time” with “half the effort.”

But the technical debt you incur while doing that? That takes years to pay back. :)
I will not stand for this Flutter slander!
(okay fair enough it's true, but still)
 
Back
Top