As an Issuer, I can quickly identify which information will be stored on-chain, on-browser and centrally - Wireframing

matthewwoo-zz / bot_2

0 stars 0 forks source link

As an Issuer, I can quickly identify which information will be stored on-chain, on-browser and centrally - Wireframing #36

Open matthewwoo-zz opened 6 years ago

matthewwoo-zz commented 6 years ago

Issuers launching their first STOs are not expected to be blockchain savvy, and as such may not be clear on where the information they are entering is stored.

As it stands today, the dApp will be capturing information that will be stored in:

Blockchain, OR
Local storage, OR
IPFS (aka Decentralized File System), OR
Centrally (for engagement purposes), OR
Shared over email with the selected providers.

Whenever entering information, the issuer should instantly identify where the information will be stored.

matthewwoo-zz commented 6 years ago

➤ Thomas Borrel commented:

Icons created are here: https://www.dropbox.com/s/1pevkprfmhnzddk/icons_v3.ai?dl=0

matthewwoo-zz commented 6 years ago

➤ Stanislav Timofeev commented:

Thomas Borrel The Icons are pretty nice. But if we want to make/save UI Consistency we need to create the set of icons in one style.

matthewwoo-zz commented 6 years ago

➤ Thomas Borrel commented:

Stanislav Timofeev - let's break this into two tasks. One for design and one for implementation. Use of these icons will require documentation and we also should write an article inventing others to use them. These icons should be available to all dApps.

matthewwoo-zz commented 6 years ago

➤ Stanislav Timofeev commented:

Thomas Borrel Do you mean our dapps? Or third-party dapps?

matthewwoo-zz commented 6 years ago

➤ Thomas Borrel commented:

Stanislav Timofeev - All of the above. Third-party dapps and our dapps. We would want everyone to use these icons, so they are as recognized as the lock on your browser.