MetaMask / Design

All things design related
7 stars 4 forks source link

Final Dapp Homepage #77

Closed bdresser closed 5 years ago

bdresser commented 5 years ago

Feature brief is here

Dev issue & background discussion https://github.com/MetaMask/MetaMask/issues/539

omnat commented 5 years ago

Insight from private beta & onboarding wizard (what makes you come back to Metamask and use it continually?)

dapp browser is key for driving usage!

easier token management

bdresser commented 5 years ago

Apple doesn't like the "native app store experience" -- but as long as it's a webpage we should be fine.

omnat commented 5 years ago

From design sync:

bdresser commented 5 years ago

on implementation side - could even store a copy of the page so it doesn't have to actually load when the user hits it

bdresser commented 5 years ago

next steps: add visuals to design brief and @omnat jam with @cjeria

omnat commented 5 years ago

quick form to see if these dapp list categories seem understandable by crypto-new people https://docs.google.com/forms/d/13N_1xDdiEkHeGXoaGKrvBIYnaXJWrHyTqud8ZZDHdFI/edit

bdresser commented 5 years ago

Mural here

bdresser commented 5 years ago

https://dap.ps/

bdresser commented 5 years ago

For when we actually have to select dapps, here are the top tx initators from Matomo:

Rinkeby

Screen Shot 2019-06-05 at 2 27 08 PM

Ropsten

Screen Shot 2019-06-05 at 2 26 58 PM

Mainnet

Screen Shot 2019-06-05 at 2 26 52 PM
cjeria commented 5 years ago

Prototype https://www.figma.com/proto/ZjvqFYvSwB90oC81N0PMHjE1/Mobile-Browser?node-id=44%3A439&viewport=43%2C831%2C1.234328031539917&scaling=scale-down

bdresser commented 5 years ago

Looks solid @cjeria!

cjeria commented 5 years ago

Here's an updated iteration of the mobile browser per all the feedback received on Figma.

Feedback welcome!

brunobar79 commented 5 years ago
estebanmino commented 5 years ago

I guess this is because this is not a high fidelity design but on the second level screens (ex. my favorites) the view has 2 navigation bars, the browser bar and the specific section bar, I couldn't find any other part of the app where we do that.

bdresser commented 5 years ago

We should use a graphic motif that the illustrator creates.

@cjeria should we add this to his scope of work, or are you anticipating being able to re-use one of the other illustrations we've requested? pointing out that the onboarading screen designs will be tight by EOM so we may want to have another placeholder that's not blocked on his timeline.

Not a big fan of the Play with Fake ETH

Agree, how bout "Request some test ETH" and for public beta we can link out to the faucet and highlight some dapps on test networks?

@cjeria what are you thinking for the "Customize Experience" button? If this is a valuable path, it could be a project for V1, but for this stage we may want something that doesn't require a new flow / more design & dev effort. Could link to the wallet? or maybe have the "Give Feedback" button front and center since we really want to be gathering insights from this Beta?

brunobar79 commented 5 years ago

@bdresser I agree with everything you said.

Let’s just make sure there are some dapps on test networks that are worth it (Personally I don’t know any)

cjeria commented 5 years ago

should we add this to his scope of work, or are you anticipating being able to re-use one of the other illustrations we've requested?

Aiming to reuse a graphic motif the illustrator creates however, I can find us a different stock placeholder or create one in the meantime.

what are you thinking for the "Customize Experience" button?

@omnat and I had discussed designing a survey-like experience where we ask the user a series of questions about their interests and we in return customize the landing page as a result. So for e.g. if the user answers in a way that indicates they like games, we suggest game dapps. That was the basic idea, but it may be a bit ambitious for the time being. We should revisit this later.

@bdresser

bdresser commented 5 years ago

love that idea @cjeria! but think it'd be best as part of V1. would be a lot to add to the milestone at this point.

for public beta, can we replace with one of the ideas above (wallet, or "give feedback"), or something else, or should we remove entirely?

estebanmino commented 5 years ago

About Strong consideration for adding a bottom bar in the browser for Android (for general consistency between platforms): I already mentioned this through slack but I just got a "it all makes sense now" moment, I guess other Android browsers don't have a bottom bar because Android has a bottom bar already built in the device and it looks like this

image

Something similar happens with cake browser

Just wanted to mention it since I didn't see that before because in latest Android versions you can remove it.

omnat commented 5 years ago

From design sync:

Next things to figure out in this one:

bdresser commented 5 years ago

Play with fake ETH feature: push it to later

I think this is easy to include - we can just link to the faucet, no?

What about a "give feedback" link?

bdresser commented 5 years ago

Newest prototype from Christian here

bdresser commented 5 years ago

bobby to come up with list of dapps for each category!

omnat commented 5 years ago

Sorry for bringing these browser nav related stuff late. I didn't have enough reason to back this up earlier..

1st one more important than the 2nd, if we had to pick...

cjeria commented 5 years ago

Great suggestions @omnat. I also stumble with getting back home so I think having a button on the bottom bar is a good call.

Also, I agree that switching networks should be made secondary action, although perhaps it also lives somewhere in the side nav drawer for quick access?

brunobar79 commented 5 years ago

Agree about point number 2.

@cjeria @omnat Thought exercise: Open your most used mobile browser (Chrome / Safari or whatever you use). See how many TABS open do you have open...

In my own research everyone I asked about that (around 8 people) they NEVER go back to the homepage to "start again". They either change the current url or they just open a new tab, which is by default opened in the "dapp homepage", that's why I disagree with point number 1 .

To me that looks like enough options

@estebanmino @ibrahimtaveras00 Please share your thoughts if you want.

I guess the challenge for me is to understand why do people need to "go back to home" to continue using the app.

Note: I am an iOS user and I'm probably very biased so just take this as simple feedback.

RE: Android, we decided to introduce the bottom bar too so that would make my point "more valid" then, but we have enough room there if you wanna add a "house" icon like other browsers have on Android (brave)

ibrahimtaveras00 commented 5 years ago

I'm an Android user, and in my normal day to day usage, I hardly ever go to home page (mainly use Chrome, and maybe 10% of time use Samsung native browser and Firefox here and there).

If I did go to homepage, it's most likely to see the news feed on Chrome, but to do this, I always just open a new tab which is just 2 taps away similar to how we currently have it in our browser.

FYI I have so many tabs open on chrome it doesn't even show the number anymore lol: image

I wouldn't totally be against putting a home button on the nav bar (I know Chrome and Samsung do this on Android) and maybe it's "comfortable" for other users since they would be use to it. I guess one way of thinking about it is that if more users are unfamiliar with DApps they most likely would go back to homepage often to see what's there and try other DApps out.

So I'm not totally for or against having a sticky home button on the nav bar (I'm perfectly fine with two taps as that's how I've been doing it for the longest).

In terms of being cluttered, look how many things are on the bottom nav bar on Samsungs native browser:

image

bdresser commented 5 years ago

I guess the challenge for me is to understand why do people need to "go back to home" to continue using the app.

Since we're a dapp browser, and because dapps & ethereum are in their infancy, I think we have a higher obligation to help users understand what they can do with the app. A huge part of that is achieved through the home screen.

I also think the fact that it's come up in numerous interviews & repeated anecdotal feedback means that people do want to go back to the home screen, regardless of how you or I use other (non-dapp) browsers.

I'm in favor! On iOS I could see it going right next to the search icon (or even replacing the search icon, since you can also focus on the nav by tapping the URL up top - although maybe this isn't obvious enough to warrant removing the icon)

omnat commented 5 years ago

Super valid points Bruno, Ibrahim on how people use other browsers. With Chrome for instance, homepage is mainly a search bar, which people can access without going to homepage.

I guess the challenge for me is to understand why do people need to "go back to home" to continue using the app.

Reiterating Bobby, Ibrahim points.. We have a different case of browser here. Here, our homepage is helping people learn what are their options. Faster way to access apps they've seen previously in featured or favorited (which could be made easier to do too - but that's a different topic).

I had hoped this feedback would stop after tabs implementation, but it's continued + observing people stumble multiple times is a clearer sign than actual verbal feedback. So, also in favor of having a home button..

cjeria commented 5 years ago

Also, what do you think about adding descriptions to the "Featured dapps" side scrolling list? We could reuse the dapp list item component, just make it less wide.

Like so:

bdresser commented 5 years ago

@cjeria i prefer the smaller tile -- the description on each of those will be so short that it would be nearly useless, and greeting the user with a bunch of half-complete sentences might be a little messy. also think it looks simpler overall with the square icons

cjeria commented 5 years ago

Okidoke then, let's leave it as is for now.

omnat commented 5 years ago

Dev-handoff done. Ongoing Design QA, will focus on it next sprint a lot before public beta