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

feat: feed settings survey #3174

Merged
merged 22 commits into from
Jun 5, 2024
Merged

feat: feed settings survey #3174

merged 22 commits into from
Jun 5, 2024

Conversation

sshanzel
Copy link
Member

@sshanzel sshanzel commented Jun 3, 2024

Changes

  • Feed feedback loops experiment with the key: feed_settings_feedback and a boolean value.
  • Based on the new alerts property, we will check whether we should display the survey.
  • Add a new type of card for the Feed. The card should be able to handle different forms of survey with little adjustment when the time comes.

TODO:

  • list mode UI.
  • immediately hide the card after clicking hide survey.
  • Some changes mentioned in this thread.

Preview:

Screen.Recording.2024-06-03.at.2.22.42.PM.mov

Screenshot 2024-06-03 at 9 19 31 PM
Screenshot 2024-06-03 at 9 19 19 PM
Screenshot 2024-06-03 at 9 19 12 PM
Screenshot 2024-06-03 at 9 19 07 PM
Screenshot 2024-06-03 at 8 43 54 PM

Events

Did you introduce any new tracking events?
Don't forget to update the Analytics Taxonomy sheet

Log the new/changed events below:

Type event_name value
Change/New event name extra: { ... }

Please make sure existing components are not breaking/affected by this PR

Manual Testing

On those affected packages:

  • Have you done sanity checks in the webapp?
  • Have you done sanity checks in the extension?
  • Does this not break anything in companion?

Did you test the modified components media queries?

  • MobileL (420px)
  • Tablet (656px)
  • Laptop (1020px)

Did you test on actual mobile devices?

  • iOS (Chrome and Safari)
  • Android

MI-355 #done

Preview domain

https://mi-355.preview.app.daily.dev

Copy link

vercel bot commented Jun 3, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
daily-webapp ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 5, 2024 6:58am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
storybook ⬜️ Ignored (Inspect) Jun 5, 2024 6:58am

@omBratteng omBratteng marked this pull request as draft June 3, 2024 13:51
@omBratteng omBratteng marked this pull request as ready for review June 3, 2024 13:51
@omBratteng
Copy link
Contributor

I re-triggered the domain assignment, hence mark as draft and back.

Comment on lines 1 to 9
// this file was created to contain all custom temporary colors (outside the guideline)
// and it is ideal to have this file to contain fewer colors as possible
// we should eventually convert the custom colors to be part of the guideline once it is deemed to be used frequently

export const feedSurveyBg =
'linear-gradient(180deg, rgba(255, 233, 35, 0.08) 0%, rgba(252, 83, 141, 0.08) 50%, rgba(113, 71, 237, 0.08) 100%)';

export const feedSurveyBorder =
'linear-gradient(180deg, rgba(255, 233, 35, 1) 0%, rgba(252, 83, 141, 1) 50%, rgba(113, 71, 237, 1) 100%)';
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To make it easier to track all custom colors, I created this file and added some notes.

@omBratteng
Copy link
Contributor

omBratteng commented Jun 4, 2024

Is the list view supposed to have this much top padding?
image

Edit: looking at the design, it's supposed to be different

@sshanzel
Copy link
Member Author

sshanzel commented Jun 4, 2024

Is the list view supposed to have this much top padding?

We have now rolled out the new list mode, it should look like below. Wdyt?

We really did not have any design for this, was more of an engineering decision.

Screenshot 2024-06-04 at 9 51 38 PM

@sshanzel
Copy link
Member Author

sshanzel commented Jun 4, 2024

Edit: looking at the design, it's supposed to be different

You are maybe looking at tablet mode.

@sshanzel sshanzel requested a review from idoshamun June 4, 2024 13:53
@sshanzel
Copy link
Member Author

sshanzel commented Jun 4, 2024

@idoshamun as we are now almost at the end of this PR. Feel free to review the analytics events for this experiment.

@omBratteng
Copy link
Contributor

Edit: looking at the design, it's supposed to be different

You are maybe looking at tablet mode.

I forgot which one I was looking at 🙈

@idoshamun
Copy link
Member

@sshanzel i surfaced product concern, once it gets resolved i'll review again. Thanks!

@@ -169,6 +170,7 @@ export enum FeedItemTitle {
}

export enum TargetType {
PromotionCard = 'promotion_card',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have this field already MarketingCtaCard

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I noticed it was available but the name for the enum was quite specific to the case of marketing, so I thought of separating them. Though I can unify them to avoid duplicates by renaming the original one.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's better to reuse. They need to match

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated here: 98359be 🥳

Copy link
Member

@idoshamun idoshamun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from analytics perspective. Thanks for checking!

@sshanzel
Copy link
Member Author

sshanzel commented Jun 5, 2024

Did some final end-to-end testing and we should be good. Functionality works as intended.

The last push was to fix the borders on touch devices.

Before:
Screenshot 2024-06-05 at 2 54 42 PM

After:

Screenshot 2024-06-05 at 2 54 31 PM

@sshanzel sshanzel merged commit 0147b25 into main Jun 5, 2024
10 checks passed
@sshanzel sshanzel deleted the MI-355 branch June 5, 2024 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants