You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
If so, any success?
Historically, Tesla doesn't do a "rollback".
What it could do is to tell you to apply the next update to get what you lost currently.
That happened to Model S and X that used to have +12/-12db equalizer sliders.
That's when someone was really smart and noticed that Model 3 owners only had a maximum of +8/-8 equalizer sliders and none of Model 3 owners complained!
Ah hah! Satisfaction guaranteed: Tesla then matched that Model 3 feature to S and X and all equally got +8/-8 equalizer sliders.
A few of us then complained that we ain't no Model 3 so +12/-12db equalizer sliders feature was then restored to S and X at the next update.
Thus, Tesla has a history of takeaways for Model S and X if you don't watch them and don't complain of the loss.
So, please write to Tesla if there's any features were taken away (such as top-half/bottom-half independently user configuration).
It's not going to happen. Primary reason why it won't is that if they were to do so, they'd have to fork the software and maintain multiple copies forever. You may say that you can live without any new features, but that's not the problem. If there are any safety issues, they have to be fixed and having to maintain multiple versions is hugely expensive.
By the way, are you still running Windows 95?
No, I didn't have enough memory in my Commodore 64 for that upgrade.By the way, are you still running Windows 95?
No matter how you modularize, supporting older versions of software always creates a for which has to be maintained by fixing all found vulnerabilities and running each fork through a full release test. Then there is the fact that the old fork is no longer supported by open source of whoever sold you the libraries, so you either have to port the old software to use new kernel or libraries, or have to sift through vulnerability reports and have security experts try to assess whether the new found vulnerabilities affect the older, no longer supported by community, software.If you do software design right, that doesn't have to be a huge task. You may unify the code base in the backend code, but have different GUI. You separate the logic and backend stuff from UI. This is not anything new. There's zillions of manufacturers etc that mantain different products with different looks.
For the premium you pay for a premium car you should have more bells and whistles.
And on a screen that has a completely different layout (portrait vs landscape) and a different position (low vs high), you HAVE to have different designs. Microsoft tried to force the tablet paradigm onto the desktop in Windows 8 and it failed miserably, and they had to backtrack and add a proper start menu again. Model S is not Model 3. A desktop PC is not a tablet.
No matter how you modularize, supporting older versions of software always creates a for which has to be maintained by fixing all found vulnerabilities and running each fork through a full release test. Then there is the fact that the old fork is no longer supported by open source of whoever sold you the libraries, so you either have to port the old software to use new kernel or libraries, or have to sift through vulnerability reports and have security experts try to assess whether the new found vulnerabilities affect the older, no longer supported by community, software.