That said, as someone who spends nearly every waking hour coding for VR and AR, I find it hard to believe ARKit graphing applications are anything but throwaway gimmicks because the ARKit's lack of semantic knowledge about the local environment means there is no way for it to attach the graphs to contextually meaningful world points without significant user input.
Without contextual placement, ARKit graphs are just a way to force the user to expend metabolic energy moving their phone around to view things that can and have been presented as well or better on a traditional displays for decades. Sure, it's cool the first time you see one, but ARKit is not how you're going to want to view your SEO conversion data, regardless of how fun it was the first time you imagined it.
I recommend moving this library into Unity and starting to establish it as the way to do graphs on systems that can have semantic knowledge about the environment.
The HoloLens will likely be able to keep the chart over your car if you leave your garage and come back, but not if you move your car and probably not if you park your car outside in the sun (which swamps the spatial projectors and prevents proper environment scanning), and you still need to have manually placed it over your car in the first place.
It reminds me of the narrow visual field of the hololens I tried months ago. I spent half of the time turning around and moving my head up and down to look for objects. Then they were pleasantly steady once I found them but the experience doesn't compare with the visual field we're born with.
Those ARKit charts look very steady too. I assume that fixing a virtual object in space is a solved problem and it's not an easy one.
