How to rrquest for adding to testflight?
1 Like
@o1x I’ll put up a public invite link on the forum here once it’s ready 
1 Like
True. And also true for most new iPhone models even if not Pro Max. As long as the battery is relatively young and it’s a new-ish phone, 10% can still be some reasonable time.
Though the map updating will turn that “reasonable time” into possibly less reasonable surprisingly quickly. The Lower Power UI is helping you. If it weren’t there, you’d see that 10% disappearing much faster than you are now.
But yeah, the “no choice” setting could be nudged down to 5% perhaps.
oh I thought it’s already post the TF. Hope we can get to test asap. Like thr Exist beta, we want to provide bug and help to let the developing moving faster and easier.
Yep, I’m keen to get a TestFlight build out very soon!
The import from the old LocoKit / Arc Timeline app database is working smoothly. It takes about 25-35 minutes on my database with 9 years of data.
I’m just doing some more work to make sure nothing is breaking after all that data is imported. I’m noticing some slowdowns, and maybe some other subtle weird things. So I’ve got to do some testing to make sure it’s all good.
If it checks out fine, then basically the current state of the app is what will be the first public TestFlight beta 
Will see how today’s testing goes…
1 Like
I still think it is MY iphone and I should be in control of the usage even in low battery situations.
My use case: when I go to bed I cleanup my timeline. I don’t care the battery is almost empty, it will be on the charger when I go to sleep.
2 Likes
Apps make 1000 decisions for you before leaving you with the remaining 10 for you to decide. UX design is a balance of deciding which decisions the user should be bothered with, while the app takes care of deciding the remaining 99% itself (mostly without you ever being aware).
When Arc was designed to remove that choice (when battery is below 10% or thermal state is “critical”) iPhones had much less battery power, so that 10% could disappear in a handful of minutes if the full UI was visible and then used intensively. That situation is a bit different now, so 5% would make more sense.
I’m not totally against changing it so that it’s always optional. Although it is one of the many cases where most of the time “the app knows best”, I’ll concede that there are cases where the user does have legit reasons to override it.
Anyway, all of this will get redone in Arc Editor when I rebuild Low Power UI there. I’m definitely going to keep all of this in mind when I come to that work! And yeah, most likely you’ll get your way and I’ll concede 
2 Likes
That is really great news. 
1 Like