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

Display a Landing Page on New Installs / Big Updates #324

Closed
lidel opened this issue Dec 2, 2017 · 11 comments
Closed

Display a Landing Page on New Installs / Big Updates #324

lidel opened this issue Dec 2, 2017 · 11 comments
Labels
exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P3 Low: Not priority right now status/in-progress In progress
Milestone

Comments

@lidel
Copy link
Member

lidel commented Dec 2, 2017

As @diasdavid noted in ipfs/ipfs-desktop#516 (comment):

Also, @lidel pretty soon you can start recommending users to install an IPFS node through station so that they can use ipfs-companion with go-ipfs.

Exciting times! In parallel to js-ipfs effort, good old go-ipfs will become a lot more user-friendly thanks to ipfs-station's refresh happening there right now.

While we could and probably will recommend it in store listing and on preferences screen,
there is an opportunity here for better communication between extension and its users.

(I'm parking this issue here so we have a game plan when Station is ready)

Here's an Idea: display a landing page to greet new users

tl;dr Detect new install/upgrade via browser.runtime.onInstalled API and OnInstalledReason and display a landing page when certain conditions are met.

New Installs

  • Open a new tab with byte-size information and links about distributed web
    It is crucial to keep this short, sweet and engaging. Less is more.
  • Detect if they are already running IPFS API on default port and preconfigure extension (read and set local HTTP gateway address, like suggested in Ask ipfs.config for gateway address where possible #309) to work out-of-the-box 🚀 ✨
  • If IPFS API is offline, inform the user that extension requires a working node to be fully functional and kindly suggest one-click installation of ipfs-station with go-ipfs (think "big green button that says install IPFS Station, and there is a yarn-like kitten asking user to click on it" 🙃 )

Updates

  • While we have landing page logic in place, we could inform users about new features in just installed update (think "animated GIF demo of a new feature")
  • Much lower priority than "on-new-install"
    This should be non-invasive, so we probably want to do it manually, only on MAJOR and MINOR updates (http://semver.org/) and only when a new feature is worth taking user's time.
@lidel lidel added exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P3 Low: Not priority right now UX labels Dec 2, 2017
@daviddias
Copy link
Member

👏🏽👏🏽👏🏽👏🏽👏🏽👏🏽 💯% on board!

PS: I love how you always create very thorough issues for proposals! Thank you ❤️

@lidel lidel added this to the 2018-Q1 milestone Dec 2, 2017
@nunofmn
Copy link
Member

nunofmn commented Dec 3, 2017

I would like to give a go at this issue.

Maybe I could start by building some mockups of the landing and update pages, in order to discuss content and appearance of the pages?

@lidel
Copy link
Member Author

lidel commented Dec 3, 2017

@nunofmn Sounds like a plan! 👍

ps. I think it will be a static web page, probably not shipped with extension itself, but loaded from public gateway (extension will only have IPFS address embedded, just like go-ipfs does with WebUI).

@nunofmn
Copy link
Member

nunofmn commented Dec 3, 2017

New Install page mockup

ipfs-companion-landing

I tried to keep an appearance similar to the IPFS website.

I would suggested to sub-divide the content of the page in three different sections:

Learn more

  • Just some minimal text talking about the main ideas of the project and the distributed web concept, and then present 2-4 links redirecting the user to videos/articles/FAQs about IPFS.

Applications

  • Link to 2-4 applications/demos/examples using IPFS.
  • We could also add a link at the end of the section redirecting the user to tutorials on how to develop applications using IPFS. Something similar to: "Developer? Learn how you can use IPFS to build distributed web applications.".

Contribute (not shown in the image)

  • A simple call to contributions button, redirecting the user to some page explaining how could help the project.

@ghost
Copy link

ghost commented Dec 3, 2017

ps. I think it will be a static web page, probably not shipped with extension itself, but loaded from public gateway (extension will only have IPFS address embedded, just like go-ipfs does with WebUI).

There's use cases where we're offline, though. Not saying it has to ship with the extension, just take it into account :)

(As for the WebUI, we're actually planning to eventually have different packages of go-ipfs that include various tools and datasets.)

@nunofmn
Copy link
Member

nunofmn commented Dec 3, 2017

New Install page (missing IPFS client)

after install missing ipfs

@lidel
Copy link
Member Author

lidel commented Dec 5, 2017

Neat! LGTM 👍

I think it makes sense to keep and maintain these static pages in this repo (at least for now).
Perhaps in a directory named landing-pages (on the same level as add-on and tests)?

@nunofmn
Copy link
Member

nunofmn commented Dec 5, 2017

Ok 👍
I will open a WIP PR soon with the static pages.

@lidel
Copy link
Member Author

lidel commented Jan 12, 2018

Quick update: we have two new repositories dedicated to IPFS GUI / UX:

I imagine there will be heavy cross-pollination between this issue and eg. style guide.
Be sure to watch that repo.

tl;dr check my short summary at ipfs/ipfs-gui#27.

@lidel
Copy link
Member Author

lidel commented Jul 16, 2018

In Q3 we have a related OKR:

There is a smooth 3-step user onboarding flow (offer, install, welcome) for companion and desktop

CCing @fsdiogo to check this issue (#324) and an initial stab in PR #326 – both are relevant "prior art" and include some initial discussions about the "welcome" step :)

@lidel
Copy link
Member Author

lidel commented Sep 4, 2018

Continued in #564

@lidel lidel closed this as completed Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P3 Low: Not priority right now status/in-progress In progress
Projects
None yet
Development

No branches or pull requests

3 participants