@luke I've been playing with factui, its great! I'm curious why you use nested atoms (`app-state-holder`) in factui.rum/initialize? I had some trouble with figwheel because I was transacting on the returned atom for client routing and it becomes stale after refreshing. I ended up with my own app-state-holder atom that I reset! every time onload is called with the new app-state. From looking at the source it looks to me like you could take away the holder and not create a new atom without changing behavior.