Worker proposal: Comprehensive UX/UI update by the ROSSUL and Graphene Lab team

[blockchained]

UPD:

Part 2 – Worker proposal: Comprehensive Bitshares UX/UI update by the ROSSUL and Graphene Lab team

[sschiessl]

Will there be a English version?

[blockchained]

Will there be a English version?

Thanks, edited

[sschiessl]

Can you please discuss the very issue of Stealth that is actually important, namely that it benefits mostly STEALTH holders, and not BTS holders?

I have pointed that out couple days after your proposal has been posted.

[blockchained]

Can you please discuss the very issue of Stealth that is actually important, namely that it benefits mostly STEALTH holders, and not BTS holders?

I have pointed that out couple days after your proposal has been posted.

this feature is not the main priority of UX/UI worker is an example of what can be implemented if community want so
if it doesn't, no drama

[sschiessl]

Can you please discuss the very issue of Stealth that is actually important, namely that it benefits mostly STEALTH holders, and not BTS holders?

I have pointed that out couple days after your proposal has been posted.

this feature is not the main priority of UX/UI worker is an example of what can be implemented if community want so
if it doesn't, no drama

Agreed, but for that a in-depth presentation of the background ongoings needs to be done, so the user actually is aware of the key aspects of the fee-backed stealth transfer. There are also BSIPs in the pipeline for Stealth Phase II.

[sschiessl]

@ xeroc
Thanks for your insterest!

* We are discussing escrow optoins. Will update you as soon as we have all the details.
* There shoud no be duplicated efforts of course. We offer to redesign and code a new UI. Once it is launched the current UI should be retired and the maintenece resourse should be directed toward the new UI. UX is a continious effort and. Good eamples are FB, Google, etc that push updates and tweeks to their products bi-weekly.
* We will research user types, their behavour, worflows and features they use. That woul allow us to design a product that serves well all user types, simple for casual users and yet powerful for the advanced and pro audience.

Best,
ROSSUL TEAM

Some short questions come to my mind:

• This proposal aims to launch the UI at the end of the proposal? Will it then already be feature-complete?
• Do you plan to continously maintain the codebase afterwards?
  

[Customminer]

This worker proposal looks great, but I hope this worker and the bitshares-ui worker proposal teams can collaborate rather than duplicate work efforts?

[abit]

* There shoud no be duplicated efforts of course. We offer to redesign and code a new UI. Once it is launched the current UI should be retired and the maintenece resourse should be directed toward the new UI. ...

Define "launch"? By saying "current UI should be retired", you mean the wallet.bitshares.org one? So your new product will contain all features included in "current UI"? I'm afraid it's too much work for you in such a short time. IMHO even if the new UI will replace the current UI in the future (to be hosted on wallet.bitshares.org), the two UI need to live simultaneously for a period (host the new UI in a new domain name), thus give us time to move features to new UI step by step. Not to mention that we probably need a way for users to migrate backups if the backup methods are different.

[ros]

@sschiessl

This proposal aims to launch the UI at the end of the proposal? Will it then already be feature-complete?
Do you plan to continuously maintain the codebase afterwards?

It should be "feature-complete". At least all features that are now present will make its way to the new UI + a few more mentioned by Graphene Lab

The current worker does not include continuous maintenance, however we are not going anywhere and will post a new worker to tweak, maintain and support the UI and UX

[ros]

* There shoud no be duplicated efforts of course. We offer to redesign and code a new UI. Once it is launched the current UI should be retired and the maintenece resourse should be directed toward the new UI. ...

Define "launch"? By saying "current UI should be retired", you mean the wallet.bitshares.org one? So your new product will contain all features included in "current UI"? I'm afraid it's too much work for you in such a short time. IMHO even if the new UI will replace the current UI in the future (to be hosted on wallet.bitshares.org), the two UI need to live simultaneously for a period (host the new UI in a new domain name), thus give us time to move features to new UI step by step. Not to mention that we probably need a way for users to migrate backups if the backup methods are different.

Launch - the UI and available for beta/public use.
I believe it would be great to let users toggle between the old and the new UI during the testing period. Similar to what Google does with new Gmail UI.
It then will be up to the community to decide when to retire (stop supporting) the current one.

[ros]

This worker proposal looks great, but I hope this worker and the bitshares-ui worker proposal teams can collaborate rather than duplicate work efforts?

This is not a duplicated effort. The current worker supports the current UI.
We propose to redesign it, make it much more user-friendly and intuitive.

When we launch the new UI users still should be able to toggle between them. Therefore we need to support both for some time.
When the old UI retired (stop being supported and updates) then we can join the effort on the support of the new one.

[abit]

@ xeroc
Thanks for your insterest!

* We are discussing escrow optoins. Will update you as soon as we have all the details.
* There shoud no be duplicated efforts of course. We offer to redesign and code a new UI. Once it is launched the current UI should be retired and the maintenece resourse should be directed toward the new UI. UX is a continious effort and. Good eamples are FB, Google, etc that push updates and tweeks to their products bi-weekly.
* We will research user types, their behavour, worflows and features they use. That woul allow us to design a product that serves well all user types, simple for casual users and yet powerful for the advanced and pro audience.

Best,
ROSSUL TEAM

Any update about the escrow, please?

[graphenelab]

Any update about the escrow, please?

Initially, we planned to work through the BLCKCHND team, but now we are discussing the possibility to launch a worker through the BBF. We already wrote them and are waiting for an answer to discuss possible cooperation options

[sschiessl]

Any update about the escrow, please?

Initially, we planned to work through the BLCKCHND team, but now we are discussing the possibility to launch a worker through the BBF. We already wrote them and are waiting for an answer to discuss possible cooperation options

BBF mustn't be the only choice, and also shouldn't be.
No one seeks to have only one centralized escrow. It is merely one (afaik the only one) that offers auditable bitUSD worker escrow and is the voted spokesperson, aka has the BTS holders trust.

Has BLCKCHND introduced themselves as an escrow? You can also consider asking trusted members of the community.