> What do you think about moving tick to the view? 

I think the View doesn't tick, the Timer does.

>  it kind of makes sense from a code organization standpoint. You might say that the Timer model only needs to track its internal state that and in some ways, the "tick" event is more of a view concern anyway.

I disagree and this change will require non-trivial refactoring. Unfortunately, I also don't have time to spare for work that isn't directly related to the Messages up (until after sprint 6).