How does this solution prevent rage clicking? Users may still be frustrated that the app is not responding (until the hydration). Hmmm... If you think about it, wouldn't this be worse? because, once hydration completes, the user will see a flurry of changes or actions in the UI, some of which not intentional and only done because of this so-called "rage clicking". Thoughts?