Don’t remind them, please. 🤪
Don’t remind them, please. 🤪
This Chipotle blog entry describes things the best as far as I know: https://chipolo.net/en/blogs/chipolo-point-delay-and-google-find-my-device-app-update
Basically, in December, Google and Apple (and others?) came up with a standard on discovering trackers that are being used to stalk people. Because of the large iOS install base, Google has elected to wait for Apple to roll out that feature on iPhones before enabling the tracking device support on Android.
I mostly have the same experience. I did a Xamarin.Mac app to port some windows code to the Mac. In some senses, it was amazing, because most of the business logic just worked and that saved a bunch of time. The UI was app kit, but with c# to obj-c bindings. That also mostly worked, however, when something broke, it really broke and was incredibly difficult to debug.
There are some use cases I’d recommend Xamarin for still, but the majority of cases are probably best solved by writing native code directly. (Or at least using a portable language such as C, C++ or Rust for cross platform business logic)
There is a bit of trickiness to the NACS announcements. They are using the NACS physical connector with CCS signaling. So if EA or EvGo or ever release a NACS connector, you’ll need that CCS module to get electricity
I just want to be able to buy a CCS retrofit for my model 3. Hopefully that gets released soon
It feels a bit different to me. Tesla hugely invested in their own charging network, while everyone else let EA do it for them. Tesla could have kept their network private to sell more vehicles. As for the exclusive Rivian chargers…I’ve never seen one, but the nearest one to me is about 300 miles away.