The smart part in the Mapillary software is SfM, I am doing some preliminary testing with 360 images I took with my LG360 and am working on an implementation for my village, but I want/need a good workflow before I realy go to work on creating the imagery. In those testes I “stumbled” upon SfM (structure from motion). They use that tech to create the cool transitions between your images. With that tech they also perfect the GPS Position in the placing and animation structure.
The question/bug I wrote here is linked to your question. the SfM software essentially corrects the yaw! They just don’t show that on the map!
They also don’t use the corrected GPS postion in the API data (my bug report).
Now if they are able to correct the GPS position I expect they could correct the pitch and roll as well… if they would/could, that would be perfect!
Then the paths would not go up in the sky (the next and previous image are OK, must have tilted the camera because I heard that horse 
)
(I am hoping they can share the corrected GPS data in the API calls, that would make things a lot better for me)