@SebastianRoehl@andraskindler@HabitKit IOS has still been decent, but last minor update on Android was 14 days. I’d be happy if I could get 5 at this point. Hope it gets better.
@seanallen_dev My update this week took 3 days in waiting. Approval only took a few minutes once it went into review, which was good. The similar update on Google Play is on day 5 and still waiting.
@builtbyjoao@seanallen_dev Good point. Getting accelerometer simulation would be helpful too. I still need physical device testing, but some kind of simulation movement would help first.
@RobCarpenter Very likely the pavement was adverse crown with respect to the left radius. At the 45 mph advisory speed for construction shift, those curves should be 6480 ft radius or flatter if pavement isn’t superelevated. Not saying it was entirely the roads fault.
@adamlyttleapps Kinda bummed SceneKit was deprecated. It was useful for more than just games. I haven’t converted to RealityKit yet, but hopefully it supports a lot of the same features.
@seanallen_dev Same time learning for me, summer 2014. My first Mac. Had no idea what wwdc even was. Took a fall college class on iOS dev. Prof rewrote the entire curriculum in Swift, which in itself was impressive. I probably would’ve spent the year learning ObjC.
@theguardrailguy@VanHollenForMD Good points. We have a lot of procedures/checks to verify installation in AZ, but it certainly helps if manufacturers design them such that they “fit” in only one direction. This is something we can question when they apply to be on the APL.
@vcrvft@theguardrailguy@FlockSafety Depends on that state, but he’s pretty close. We (AZ) have a standard that no fixed objects should be within 59 inches from the front face of the rail with wood post systems and 50 inches for steel post systems.