Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Landing pages flow & content #564

Closed
fsdiogo opened this issue Sep 4, 2018 · 3 comments
Closed

Landing pages flow & content #564

fsdiogo opened this issue Sep 4, 2018 · 3 comments
Labels
exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up

Comments

@fsdiogo
Copy link
Contributor

fsdiogo commented Sep 4, 2018

Hey @ipfs-shipyard/gui!

As we talked in the GUI & In Web Browsers Sync, we need to define the flow and content of the landing pages for Companion.

Welcome Page

After the extension is installed, the user would be presented with a page that showed something like a thank you message for installing Companion, and also checked if a node is already running, giving simple instructions how to run one if not. We could have some links about the dweb and some IPFS resources.

I think a split screen layout would work great for this:
welcome

In the left side we would have the Companion related thank you message and node checks, in the right side we would have the links to resources or other apps.

The content is key and it will help with the design, so I'm asking you for some feedback about what should be present here.

References

@fsdiogo fsdiogo added UX exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up labels Sep 4, 2018
@lidel
Copy link
Member

lidel commented Sep 5, 2018

I like the split screen idea, looks different than usual landing page and keeps user engaged. 👍

Some Ideas for left pane

  • Key feature: provide immediate feedback about connectivity status
    • If online, make it more engaging by displaying "Connected to N Peers" and the heartbeat animation
    • If offline, display two options: "Install go-ipfs" (in future we will replace this with "Install IPFS Desktop") or "Start Embedded JS-IPFS Node".
      • We may even automate it further so it automatically switches to embedded node if HTTP API is down
    • IPFS API (after init) can be accessed like this (we can expose other methods/plumbing this way as well):
      const ipfs = (await browser.runtime.getBackgroundPage()).ipfsCompanion.ipfs
  • I wonder if we could re-use animation from https://ipfs.io 🤔 Thoughts?

Unsure where to put

  • (Highlight) a button/link to "Share files via IPFS"
    • It is a good tool to play with after install, if we make it smooth experience it will get user hooked
  • Other "killer apps": IPFS Files from new WebUI (IPFS Drive :P), PeerPad etc

Some ideas for content for the right pane

@fsdiogo
Copy link
Contributor Author

fsdiogo commented Sep 5, 2018

The ideas for the left pane sound pretty good. I think the animation from ipfs.io is far too soft, I bet it gets unnoticed by most of the people. I think if the IPFS logo gets the heartbeat animation it will be sufficient, I'll probably add that and see how it goes.

The right pane looks good too, I'll try find a way to make that look clean but attention drawing. As you said in another thread, less is more, we want to keep this page uncluttered but draw the user to learn more and follow some links.

Thanks for the feedback @lidel!

@lidel
Copy link
Member

lidel commented Sep 19, 2018

Released to beta channel v2.5.0.11550 🎊 🚀
Thanks @fsdiogo !

@lidel lidel closed this as completed Sep 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

No branches or pull requests

2 participants