This post now moved to a separate topic:
@Nick_M This is fantastic! I’ve given you editor powers in the figma (and removed mine for now as I’m not doing anything atm). Could you
- Break this out into a seperate topic in #platform:users-and-identity
- Implement this spec in the figma
Where might we capture City/regional data?
See address city and region above. Applies to members only.
Yes … sorry… booting up
Ok for this coming week @Nick_M Will focus on 0.4 Profile, what the users sees when they return to their profile to update details, change their subscriptions and / or delete their account.
@auggod and @Hakanto you guys don’t need to do anything on this front for this coming week. We’ll still want you at the next meeting, but I think it’s best if Nick stays focused on this and you guys focus on your other areas, for the next week at least.
We’ll return to the other quetsions we didn’t cover next week, as they’ll be more pertinent a bit further down the track here, namely these:
@Nick_M Just a note for both you and me (I forgot both of these for this weeks meeting). We should include these in our planning here:
@angus will confer with @Nick_M about including https://community.resonate.is/t/putting-down-the-free-listening-credit-to-an-hour-on-sign-up/1727 in the accounting epic
Should we be asking for city in user onboarding / profile?
City and country are useful metrics for artists - without invading privacy.
Without them, artists can’t reach out to fans in certain areas about shows.
Yes we could add that to the sign-up and ensure that marketing permission is requested and the purpose of artist outreach is added.
But as soon as the one hour of free listening credit has expired, for top up we ask them for address data including city as part of checkout, all secured in the stripe api. We can retrieve and use it when we need to.
At the moment, country is for rights and statistical purposes only, with a newsletter permission on the use of the email. We hold the absolute minimum about a listener until they buy credit and/or join as a member.
I guess the thinking was that listeners are serious supporters of the artist then they should join as a member and… and open up the permissioning for artist outreach as an active member using privacy-respecting tools like community credentials for safe P2P interactions.
We have ‘follows’ and ‘feeds’ on the profiles, opening up the prospect of a full on social graph thing, Facebook-style. I think we need to think more carefully about how we use that stuff.
Sorry guys, I can’t make it this time.
To recap: Nick took us over
0.4 Profile Update UX, and we came to a landing on a number of items, as reflected in the design. We’ve now completed
0.4 for the purposes of the epic. See
We also discussed the following
We’ll need an explanation of why we are asking for address information and credit card information in stripe itself. We’ll need to add this into the checkout page if possible. Perhaps also note this in the profile page help text the user sees prior to being linked to Stripe. In particular we need to note the following
- We use the information in our KYC process
- We comply with GDPR and other relevant regulatory regimes
- Information is kept entirely private and never shared
@boopboop questioned whether we could potentially connect artists with labels (interesting idea)
@Hakanto will review the help text on pages
0.3 Profile Info (onboarding)and
0.4 Profile info (updating)(i.e. text in the right hand column.
- What help text do we show to different user types (Artist / Listener / Label)
- What handbook topics do we link to?
@Nick_M will prepare
0.5 Profile Stripe Datashowing how we will
- Display a member’s data stored in Stripe
- Allow a member to update their billing details in Stripe
- How do we link to these pages from the main profile?
- Do the Artist Info screens need updating?
@boopboop will have a look / think about how we’re representing “Genres” in the Artist Info Pages. Does this make sense?
0.5 Profile Stripe Data(definite)
- Artist Info Screens (definite)
- Set a date for start of epic development (definite)
- User-facing profile (maybe)
I did some tidying up yesterday:
- added some notes on reduced free credits and pricing of credit packs
- added some notes on 0.4 update your profile, including what happens if folks switch type of profile
- added detail and logic for the Leaving Resonate page (0.43)
- added some placeholder text for the ID server verification / signup emails 0.2
…haven’t properly checked against the last approved set of website and sign-up copy…
There are three layouts in there for 0.4 ‘update your profile’, but it is essentially the SAME update profile screen, with dynamic prompts / content. The different layouts there are simply to help visualise what appears (and what doesn’t appear) for:
0.41 a listener who is not a member
0.42 a member (listener, artist/label)
0.43 anyone leaving
Hope that is OK! @Hakanto please work your magic and give the text and prompts a look over
Here is the updated logic and data x-references for the sign-up flow:
(Note that the message text displayed in that original post are indicative only and may have been overtaken by subsequent edits in the Figma)
Our Epic starts next week on our (almost) completed designs!
- Explicitly show user flow in design
- Resolve representation of shares / memberships (for Nick, Angus and Hakanto in tomorrow’s meeting)
- @Nick_M Am I missing any final todos here?
@developers Our next Development Epic formally starts next week with a kick-off meeting at 2021-10-11T14:00:00Z → 2021-10-11T15:00:00Z. A new Epic topic will be made for it with an event later in the week.
I’ll also be mapping out this Epic in Github issues later in the week and we’ll deal with assignments in next week’s meeting. If anyone wants to take a particular part of the work reply below.
@developers here we go!
This is now our current epic!
This topic will close in a few days
This topic was automatically closed after 4 days. New replies are no longer allowed.