Research methodology

[iteles]

We need to have some consistency of methodology when carrying out general research on apps (e.g. #9) so that:

• We are comparing more or less like-for-like which will yield greater insights
• Anyone who has an interest in a particular app can carry out a little research in a useful way

This issue will be for capturing the required points to research in the comments and creating a starting point list in this OP before it can be transferred to a readme.

Note: I am keen to not make this particular list exhaustive, but rather an accessible list that would allow someone to perform the research in the course of 2 pomodoros max. It's a first pass with specifics (e.g. #6) to be researched further in separate issues.

List of items to research

• Homepage screenshot
• List of key functionality (e.g. to-do list, categorisation, timers, documentation, etc)
• Watch video of product (if one exists) and note contents
• What does the sales website focus on
• Number of users (individuals vs enterprise?)
• Screenshot of pricing

[nelsonic]

@iteles ideally we need to test the UX/UI of the App and record a screencast on both Desktop and iOS.
If we can do this really well for one App, then we can make it a "Virtual Assistant" task.
We need a VA with a really good sense of design/aesthetic to critique the UX/UI of the products we are researching. Ideally we are looking for the areas/gaps where we can make improvements.