Design decisions - Schmed/teamwork GitHub Wiki

Here are a few of the decisions we've considered while developing the Teamwork system:

• Customize system for ATC - Our only hope of significant player participation is if we carefully tailor the system for the needs of our own team. For example, simply gaining access to the Pie Queens' Workout Wars system would likely have failed miserably.
• Simple development tools - Although a custom web application (let alone a custom smart phone app) would certainly increase the flexibility of our design, this would add at least an order of magnitude to the difficulty of that development. This is just not warranted given that we're unsure how successful any such system might be for our team. Although the Google form UI is fairly constrained, it seems to provide enough functionality (certainly for a prototype system).
• Avoid player accounts - We could have enforced the Teamwork to player link by requiring each player to log into a specific Google account before submitting Teamwork, but we didn't think the benefits of authentication outweighed the hassle it adds.
• Radio button category selection - The teamwork.gs Google Apps script is designed to automatically incorporate activity category descriptions into the actual choices presented on the form whenever the form is configured to use "radio button" (i.e., MultipleChoiceItem) controls for these selections (as it is presently). If the form is configured to use "drop down menus" (i.e., ListItem) controls instead, each choice would include only the category name and the point value (as there's no room for the descriptions). It would have been nice to include the descriptions as "hover text" in that case, but Google forms don't support that.
• Fix points awarded - Changing the category taxonomy or point values should not affect any points that have already been awarded.