POKEPEDIA

POKEPEDIA

1. CRITERIA

   • SELF DETERMINED
     • Application must be able to search by filters
       • SORT BY
         • ID
         • NAME
         • TYPE
         • STATISTICS
         • SPAWN LOCATION
         • RARITY
     • Colourful
       • Colour code poketypes
       • Colorful title block
       • Interface should be interesting
     • Interface should be minimalistic,
       • Should be easy to use
       • Not too much clutter
   • PRESCRIBED
     • Web application uses data from an external data source
       • Normalise data
     • Web application displays Pokémon data from an external data source
       • Normalise data
     • Web application allows a user to search the Pokémon statistics
       • Basic search filter

2. IMPACTS

   • SOCIAL
     • FRIENDS LIST
       • Linking Pokemon Go account links friends
         • App shows recent achievments, such as cataching a legendary Pokemon
   • PERSONAL
     • Enjoying Pokemon more
   • ECONOMIC
     • A subscription based system
     • The application showing pokemon card values

3. CONSTRAINTS AND LIMIATIONS

   • CODING ENVIRONMENT
     • No code is required, just pseudo code.
       • Limits the prototype
   • CODING LANGUAGES
     • FRONT END
       • CSS
       • PYTHON
     • BACK END
       • HTML
       • SQL

4. EXISTING SOLUTIONS

   • NEGATIVES
   • POSITIVES
   • INTERESTING
   • USER EXPERIENCE

5. User interface

   • Minimalistic
     • Simplistic, reduce clutter
       • Colourful
   • Filters
     • Search by:
       • Poketype
       • Name/ID
       • Spawn location
       • Rarity

6. Usability principles

   • Learnabilty
   • Safety
   • Effectiveness
   • Usability
   • Utility

7. EVALUATION

   • Refinements and reccomendations in evaluation
   • User iinterface prototype
   • Personal, social, and economic impacts
   • Prortyped digital solution