Poor UX around credit binding on publish, esp. for new users #528

New issue

Closed

opened 2017-09-04 14:12:30 +02:00 by kauffj · 9 comments

kauffj commented

2017-09-04 14:12:30 +02:00

(Migrated from github.com)

New users who know nothing about LBC are going to be confused about how to use their credits to both claim a channel and make a publish.

See this Twitter thread as an example: https://twitter.com/JoshStrobl/status/904615412712734720

New users who know nothing about LBC are going to be confused about how to use their credits to both claim a channel and make a publish. See this Twitter thread as an example: https://twitter.com/JoshStrobl/status/904615412712734720

tzarebczan commented

2017-09-04 14:34:27 +02:00

(Migrated from github.com)

JoshStrobl commented

2017-09-04 18:20:17 +02:00

(Migrated from github.com)

Copying what I said in my DM (thanks @kauffj for reaching out), just my personal opinion / recommendations, excluding what is or isn't technically feasible at this moment in time:

Yea so I had created a channel using the 5 LBC you can see in that screenshot. I thought it'd act more like an account, since I didn't really understand any other reason you'd put LBC into it. So I did that, then put 1 in (it doesn't make it clear if there is a minimum either). Went to publish, got that. Restarted my client and it no longer had the account name under the Publish section, so I opted to put 1 LBC in for account creation, 1 in for publishing the initial video, and it worked.

My recommendation would be to separate out channel creation and publishing. Once you're validated (or when / if a validation process stops occurring, during the first time to launch LBRY or click Publish), you'd be prompted (like with a modal dialog / fancy overlay) to create an account before you can even start the upload process.

Furthermore, explain the claims system a bit in the channel and URL setting (during video publication), like why you need to essentially pay LBC (I know you can get it back, although I didn't see anywhere in the UI to do that, nor what happens if you do request to get it back) for the URL.

Copying what I said in my DM (thanks @kauffj for reaching out), just my personal opinion / recommendations, excluding what is or isn't technically feasible at this moment in time: > Yea so I had created a channel using the 5 LBC you can see in that screenshot. I thought it'd act more like an account, since I didn't really understand any other reason you'd put LBC into it. So I did that, then put 1 in (it doesn't make it clear if there is a minimum either). Went to publish, got that. Restarted my client and it no longer had the account name under the Publish section, so I opted to put 1 LBC in for account creation, 1 in for publishing the initial video, and it worked. > > My recommendation would be to separate out channel creation and publishing. Once you're validated (_or when / if a validation process stops occurring, during the first time to launch LBRY or click Publish_), you'd be prompted (_like with a modal dialog / fancy overlay_) to create an account before you can even start the upload process. > > Furthermore, explain the claims system a bit in the channel and URL setting (during video publication), like why you need to essentially pay LBC (I know you can get it back, although I didn't see anywhere in the UI to do that, nor what happens if you do request to get it back) for the URL.

👍 1

MSFTserver commented

2017-09-04 18:39:11 +02:00

(Migrated from github.com)

would this work?
https://github.com/lbryio/lbry-app/pull/527

would this work? https://github.com/lbryio/lbry-app/pull/527

JoshStrobl commented

2017-09-04 18:49:30 +02:00

(Migrated from github.com)

@MSFTserver I think that explains in a clearer manner in the current UX what the deposit is for, yes, however doesn't resolve the UX issues itself obviously.

@MSFTserver I think that explains in a clearer manner in the current UX what the deposit is for, yes, however doesn't resolve the UX issues itself _obviously_.

MSFTserver commented

2017-09-04 18:54:41 +02:00

(Migrated from github.com)

yea i wasnt gonna touch the whole UX yet as that is another issue #373 Thomas posted earlier

👍 1

btzr-io commented

2017-09-05 06:26:20 +02:00

(Migrated from github.com)

My recommendation would be to separate out channel creation and publishing.

Also separate editing claims from this ^^ 😛

> My recommendation would be to separate out channel creation and publishing. Also separate editing claims from this ^^ :stuck_out_tongue:

jsigwart commented

2017-09-06 17:10:27 +02:00

(Migrated from github.com)

Another small UX related thing would be to change the default deposit from 10 LBC to 1 LBC to be more user friendly.

👍 2

neb-b commented

2018-08-21 19:50:28 +02:00

(Migrated from github.com)

@JoshStrobl I think we have improved on this experience a little bit but could still certainly improve more. Could you try this again and let us know your thoughts?

alyssaoc commented

2018-10-09 19:04:38 +02:00

(Migrated from github.com)

quick publish epic