Agenda Next Meeting Deep Dive
Revision as of 04:52, 13 June 2014 by LegacyKing (talk | contribs) (Created page with " Topic Suggestions for the next meeting: * "Selection User Experience" ** Please add "Selection User Experience" as a deep dive topic for a future meeting. I'd like to have ...")
Topic Suggestions for the next meeting:
- "Selection User Experience"
- Please add "Selection User Experience" as a deep dive topic for a future meeting.
I'd like to have a discussion about what the "appropriate" user experience is for selections.
While I'd like to keep the discussion away from data constructs, it's probably appropriate to point out that right now we have multiple methods of driving a selection (CHOOSE, ADD, Ability Pools, and a few others).
I'd like to discuss how a user selection - of ANY form - "should" be done. Topics include:
- What types of choices are there (e.g. Archetypes, selecting a skill for Skill Focus, etc - this is a RULES question not a data token question) and do they justify different behavior?
- Should the data EVER be able to enforce a popup?
- Should data be able to provide a default choice if no other choice is made?
- How can selections be done efficiently without forcing popups?
- What specifically is the best user experience for a selection?