Hmm. I like it!

Will need some careful thinking, to design such a mode well. But I can definitely see the benefits of it. Could even have Arc drop into this UI mode when battery is low, or thermal state is too high.

To clarify, I think you’ve struck on exactly the right point of optimisation: the UI.

Most people come at energy saving suggestions by talking about reduced accuracy or detail in the recording, but doing that wouldn’t achieve any energy savings, because LocoKit is already recording at near peak efficiency. It really is the UI where the energy gets chewed up. So am optional “low power UI” is something. that does make sense.

That would be amazing! What about showing in this tab some sort of animation of the transport mode arc thinks you’re at in addition to some stats such as speed, altitude etc?

I really like this idea. I like hiking, but when get home I enjoy having a look at where and when I was at different places, but before that as “cheap” as absolutely possible on the bat would be great.

I’ve started work on this one! I want to get it into 3.0, because 3.0’s UI is much more data heavy than 2.3’s, so there’s much more risk of browsing through data that can cause significant battery drain.

I’ll also be switching the app to this low power UI automatically when the battery is low, and when Low Power Mode is turned on.

Might be a bit late to ask, but is there a way to manually enable this mode (without the battery being low)?

Yep! Turn on your phone’s Low Power Mode, and that will also turn on Arc’s Low Power UI.