[Epic] Autocomplete > A Comprehensive List of Tags

[nelsonic]

Story

As a person wanting to Categorise my life/data so I can be more effective with how I spend my time,
I need a list of common tags that will auto-suggest/complete as I'm typing
So that I don't waste time describing the task when I could be Completing it!

Hopefully this story is self-explanatory,
but if it's not please leave a comment below with the specific part that is unclear.

Todo

• Create a list of popular tags that people will use to Categorise their data:
  • task
  • note
  • reminder

Our plan is to start off with only a handful of commonly used tags.
and gradually build up a comprehensive list by crowd-sourcing it.
(some editorial may be required to avoid spam but hopefully people will not waste our time)

[iteles]

Next level: Auto-complete from existing activities particular to only that user 💪

[iteles]

@nelsonic I have added a priority-4 label here and added issue #248 to capture the UX of auto-completion of tags in general (without a pre-populated list).

We'll definitely need to A/B test these features and as I suspect some people will love a starting point of common/most popular tags and others will hate it.

Personally I would love to see what other people use most as inspiration but I definitely don't want tags that aren't part of my personal organisation system 'polluting' my auto-complete.

I hypothesise that we'll end up somewhere in the middle, either:
a) We give people the choice one way or the other (full list of most popular tags or none)
b) We give people a small starting list (e.g. to be tested but for example only contextual tags like @home, @office, @travel, @phone) which they can fully edit and delete from, allow them to build their own lists and then have a blog post with the most popular tags for inspiration.

[nelsonic]

@iteles you've included quite a lot of ideas/features in the prose above. 👍
priority-4 seems low considering how much we expect people to use the Tagging feature when they are categorising/organising their data. We want the process to be as effortless/fast as possible, and that means auto-completion/suggestion of previously used and popular tags. I've built auto-completion several times before in various contexts e.g: https://github.com/nelsonic/ac and it doesn't have to be complex;
I think if we can capture the desired MVP UI/UX in Figma, we can ship it in a few days.

[iteles]

@nelsonic I think I'm not communicating the difference between this issue and #248 adequately.

In my mind, #248 is the 'MVP' of tagging with auto-completion by creating your own as you go along (higher priority and 'next' after this sprint's issues) and this issue is the evolution of the feature, about providing a comprehensive/crowd-sourced starting list of tags, but have I misunderstood your original proposition?

[nelsonic]

@iteles you are communicating a lot more than you think by applying priority-4 to an issue.
You're basically saying this feature is "low priority" for the people using the App and we don't need to think about it ... whereas I feel it should be worked on pretty soon (e.g: Sprint 3) and we need to capture the ideal UI/UX ASAP (before the sprint starts).

I get the feeling that we are creating duplicate/overlapping issues/stories instead of focussing our efforts on clarifying and then prototyping the issues we already have. If we aren't moving the idea towards a wireframe, code and then towards an implementation that can be used by people,
e.g: by asking a clarifying question, then we are simply adding to the cognitive load (forcing people to scroll through "meta" comments) of this thread without any progress. 😞

[iteles]

Removing the priority label altogether based on our team discussion about this #239 (comment)