Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

[META] Platform Product Page #442

Closed
9 of 10 tasks
jepstein opened this issue Nov 1, 2022 · 4 comments
Closed
9 of 10 tasks

[META] Platform Product Page #442

jepstein opened this issue Nov 1, 2022 · 4 comments
Assignees

Comments

@jepstein
Copy link
Contributor

jepstein commented Nov 1, 2022

As a Rally user, I want to see the user impacts of my data contribution, so that I can feel the benefits of participating.

Figma with wireframes

DECISION: Visualization: Number of trackers collected; this could continue to grow; we can update the stats as needed. Also shows a sense of community through ongoing collective action. Could break down by type/brand/platform of tracker.
Visualization will take up the bulk of the entire top “card” area.

Schedule

  • Monday, November 7: What data are available? Casey, Bruce, Ashwin
  • Tuesday, November 8: How do we display that data? Casey
  • Tuesday, November 8: Reconvene and make decision on data display. Casey, Bruce, Ashwin
  • Tuesday, November 8: Decide on content associated with data display. Three graphics to start, copy still needed, legends on images, including .
  • Thursday, November 10: Layout of the page defined
  • Monday, Nov 14, implementation begins
  • Product Page: Impact Section #474
  • Final copy edits: @KimBMozilla
  • No “current projects” section for the shortened timeframe
  • Demographics, toasts, contribution status (attention stream, need to live in a different view than previously)

#453

@jepstein
Copy link
Contributor Author

jepstein commented Nov 1, 2022

Next step is a meeting to decide on initial iteration of the product page among the following options --

  • Highlight wins/accomplishments/past studies
  • Highlight the community you’d be joining
  • Giveback for unlocking final step in onboarding
  • Sharing studies, results, my impact
    • What types of things do people want to share?
  • Stanford’s tidbits; need to be repackaged (currently slanted towards data folks).
  • Highlight real folks on site: what impact have we had on specific people’s lives

@marniepw
Copy link
Contributor

marniepw commented Nov 2, 2022

11/2 discussion: recording link

  • Constraints: think about what data we have available for the first version of this page: content box where some kind of aggregate lives.
    • Data type requirements:
      • Legal requirement: Has to be in the privacy policy.
      • Product requirement: Has to be somewhere the user can find it and review it. Ted’s reply from slack
  • What’s most important to the user?
    • Value
      • Insights:
        • Aggregate level: Going with this currently (Nov 2, 2022). Possible options:
        • Number of Rally users across U.S. states: community building
        • Impact links
        • Insight
        • Community (X users have contributed Y rows of data, or found N pixels)
        • Number of lawsuits
      • Research participants group level
      • Individual level
        • A lot of data to choose from but do not know what is most valuable for end user
          • Need UR
      • Empowerment through action
        • Contribute data

@marniepw
Copy link
Contributor

marniepw commented Nov 2, 2022

11/3 meeting: recording
11/4 meeting: recording

@marniepw
Copy link
Contributor

Closing in favor of the newly created #495

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants