Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IGAPP-1171: New events are highlighted in color. #2112

Open
jira-to-github-migrator bot opened this issue Aug 12, 2023 · 19 comments
Open

IGAPP-1171: New events are highlighted in color. #2112

jira-to-github-migrator bot opened this issue Aug 12, 2023 · 19 comments
Labels
blocked Native Affects the native project Task waiting-for-cms Web Affects the web project

Comments

@jira-to-github-migrator
Copy link

jira-to-github-migrator bot commented Aug 12, 2023

Description

New events should be highlighted as new to show users that there is new content.

An event counts as new if

  • the event has not been opened yet by the user AND
  • the event is less then 5 days old

Additional information:

Desgin

Related issues
#2986, #2935, #2707, #2808

@jira-to-github-migrator jira-to-github-migrator bot added Native Affects the native project Task to-be-discussed Web Affects the web project labels Aug 12, 2023
@jira-to-github-migrator
Copy link
Author

Martin Lehmann - 6.12.2022, 10:57:57

<~vijay.karthik> What is the definition of "new"? and what kind of objects are in focus?

Vijay Karthik - 6.12.2022, 13:00:45

<~martin.lehmann> 
Looks like it has to be discussed....
See here:

https://chat.tuerantuer.org/digitalfabrik/pl/4ofjo8iumfdodgmbx4usgufbec

@LeandraH
Copy link
Contributor

LeandraH commented Jan 8, 2024

It looks like there has been quite some discussion on this on Mattermost, and the latest state there was to add a question about this to the JPAL survey. @clarabracklo do we already have some feedback on that question?

@clarabracklo
Copy link

@LeandraH There is no feedback from JPAL on this so far but I will check with the researchers. We can also spread this question to our Integreat-Community and get feedback this way. Would that be helpful as well?

@LeandraH
Copy link
Contributor

LeandraH commented Jan 8, 2024

That would be great!

@clarabracklo
Copy link

@LeandraH Update von JPAL: Aktuell steht eine neue Befragungsrunde mit neuen Teilnehmenden an. Die Frage wird in die Folgebefragung in ein paar Monaten aufgenommen, wenn die Befragten schon ein bisschen Erfahrung mit Integreat gesammelt haben. Es dauert also noch bis wir hier Rückmeldungen durch JPAL haben werden. Wir machen uns in der Zwischenzeit mal Gedanken wie wir euch schon früher durch die Community einen Eindruck geben können :)

@clarabracklo
Copy link

@LeandraH @juliawohlhueter Will put the question forward in our community and get some insights from them. We plan to give you feedback in the first week of February :)

@LeandraH
Copy link
Contributor

It would be easier to ask the community with a design of how this should look.
The question of when exactly an event is new can be discussed later.

@LeandraH
Copy link
Contributor

Here's another Mattermost thread about this: https://chat.tuerantuer.org/digitalfabrik/pl/byjiez1j3tgs8ja39tsnm4i7ky

@LeonieKillian
Copy link

We asked our Integreat-Facebook-Community if highlighting new events would be helpful for them.

We got 9 votes for "yes, it would be helpful" and 2 for "no I don't need that". In the Facebook-Community, 12 votes is a pretty high participation, usually we get around 3-5 votes.
Is that already helpful for you or do you need something else/ more answers?

Our ideas for the next steps are:

  • we could write direct messages to the voters -> ask them further questions
  • we could ask the Community-Members to choose between two designs
  • we could ask another more specific question
  • we could also take a more specific question or a design-question to our target group workshop in Dortmund

What would be helpful for you? What would be the best next step for you?

@LeandraH
Copy link
Contributor

Honestly, I think that is already pretty much all we need. What do you think @hauf-toni ?

@hauf-toni
Copy link

I agree with @LeandraH. Also, a user testing with a design proposal (possibly an A/B-Test) would be a good idea.

@clarabracklo
Copy link

@LeandraH @hauf-toni Thank you! Let us know if we can be of help with any further steps :)

@hauf-toni hauf-toni assigned hauf-toni and IsabellaTG and unassigned hauf-toni Mar 11, 2024
@IsabellaTG IsabellaTG moved this to Next Up in team-app Mar 18, 2024
@IsabellaTG IsabellaTG moved this from Next Up to In Progress in team-app Mar 18, 2024
@IsabellaTG
Copy link

@IsabellaTG IsabellaTG moved this from In Progress to In Review in team-app Mar 21, 2024
@IsabellaTG
Copy link

IsabellaTG commented Mar 27, 2024

@IsabellaTG IsabellaTG moved this from In Review to Done in team-app Mar 27, 2024
@hauf-toni hauf-toni moved this to Done in team-uiux 🎨 Sep 9, 2024
@steffenkleinle steffenkleinle moved this from Done to Next Up in team-app Oct 14, 2024
@steffenkleinle steffenkleinle removed the status in team-app Oct 14, 2024
@hauf-toni
Copy link

I would suggest including this issue in our next roadmap @steffenkleinle

@steffenkleinle
Copy link
Member

steffenkleinle commented Nov 4, 2024

Sure, sounds good. I think it still needs a little bit of clarification though, in what case do news count as new? As long as the event detail is opened? One time until the event overview is opened again? For one week?

Also, should the label neu/new be translated to all languages?

@steffenkleinle steffenkleinle added this to the Roadmapping T36K milestone Nov 4, 2024
@hauf-toni
Copy link

@steffenkleinle fair point. I would recommend an interaction and duration-based approach: The "new" label should stay on the event for 5 days or until the user opens the event page—whichever comes first. This balances time relevance + user interaction, ensuring the label remains helpful without overstaying its welcome ( 😺 ).

@steffenkleinle
Copy link
Member

Thanks @hauf-toni! I guess the duration-based approach should only be dependent on the date of the event creation/publishing, not on further updates of the event later on like fixing a typo, right? If so, we need this exposed in the API by the cms team.

@hauf-toni
Copy link

as discussed today with @osmers and @steffenkleinle we’re sticking with the duration + interaction-based approach mentioned above. The "new" label will stay on the event for 5 days or disappear once the user opens the event page—whichever comes first. Additionally, there should be an option to filter events by "newly added." I’ll update the design accordingly and take the other planned changes (time period filter, category filter) into account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Native Affects the native project Task waiting-for-cms Web Affects the web project
Projects
Status: No status
Status: Done
Development

No branches or pull requests

8 participants