Persistence test
The app will perform better for the actual Thunderstruck draft if picks are persisted.
It isn't strictly speaking necessary to reset picks when users are reallocated (for that particular use case)
Second pass at persistence
Removed improper use of _id
Announcement text alignment
Merge branch 'persistence-test'
Slight tweaks for small screens
Everything wired up for initial deploy except address and accounts