swarmcity / SwarmCityConcept

This is the high level description of what needs to be built
9 stars 1 forks source link

As a user, I see the detail-view of a request/deal so I can verify all the details of this request/deal. #9

Closed kikipluche closed 6 years ago

kikipluche commented 6 years ago

Abstract:

In Swarm City, hashtags are marketplaces. A hashtag gives context to a SWT token transfer.

Users (Seekers) can post new requests in a hashtag, inviting other users (Providers) to reply to their requests.

How it could work:

A hashtag has a chronological list of hashtag items. When the user taps the item, a detailed view is displayed.

The client gets real-time updates on the detail state. The client subscribes to the item.

There are 2 types of detail views:

Shareable link

In both views a user sees a shareable link to the detail view of the item.

This link can be shared on social platforms to advertise it.

The detail view contains the appropriate meta tags to render a preview on most social media and content platforms.

It could look like this: https://swarm.city/hashtag/[contractaddress]/[dealhash]


What it looks like:

Userflow: https://invis.io/ABGM89SX3V5#/293478690_-Hashtag--contractadress---dealhash-_MYITEM ( > in Invision, hold shift to see clickable areas)


route: /hashtag/[hashtagadress]/[itemhash]

The item's appearance changes depending on the user's role:

Detail view - myItem (A): When the user is the Seeker, the item consists of:

Detail view - Item (B): When the user is not the Seeker:

When the user taps the detail close-button (x-mark), the view changes to the page /hashtag/[contractaddress].


Desktop view:


Invisionlinks with login (for inspect mode!): mobile: https://projects.invisionapp.com/d/main#/console/13838256/293478690/inspect desktop: https://projects.invisionapp.com/d/main#/console/14147648/294446445/inspect

Documentation / references

Detail-view meta for shareable link:

<!-- For Google -->
<meta name="description" content="" />
<meta name="keywords" content="" />

<meta name="author" content="" />
<meta name="copyright" content="" />
<meta name="application-name" content="" />

<!-- For Facebook -->
<meta property="og:title" content="" />
<meta property="og:type" content="article" />
<meta property="og:image" content="" />
<meta property="og:url" content="" />
<meta property="og:description" content="" />

<!-- For Twitter -->
<meta name="twitter:card" content="summary" />
<meta name="twitter:title" content="" />
<meta name="twitter:description" content="" />
<meta name="twitter:image" content="" />

kikipluche commented 6 years ago

in the API will have a subscription on 1 item and it will emit updates

xardass commented 6 years ago

When landing on an item detail page, the client will start a new subscription to the API with real-time updates on this item.

When closing the detail view, route to the corresponding hashtag page (which can be found within the item detail direct URL)