Files: 7543d68eba5d350b4be3b83fd7f98d40d81da89f / patchwork-onboarding.md
Summary
This is a rough scrap for us to start to condense our ideas around Patchwork Onboarding. What does it look like? (Animations, a Simple Getting Started Screen? Modal Prompts?) What should it include? We can reconfigure this as our ideas expand and refine themselves.
Getting Started Page
The following is quoted from @Cinnamon's post "Patchwork user experience improvement brainstorm list" found at: %ORS73asFbxUC4Ck/kn95zPRar9NXxac676Vpn86ZVwQ=.sha256
Getting started page - Consider starting with a splash screen or help screenwith a few illustrated and digestible points like... Welcome! Things work a bit differently here. 1. Think of this as "offline facebook that syncs directly between friends". There are no central servers or people in charge- everything is up to you. 2. There are "Pub" servers that help messages sync, but they don't have power over you and they're optional. If you're on the same wifi as someone, you will sync directly with them. 3. Each device gets its own account, but you can link the accounts together so they look like one person. 4. The first time you connect, it's gonna download a bunch of stuff so you can be offline. Just give it a minute and don't be surprised.
Other Ideas
- It could be helpful to point out the literal buttons in Patchwork, how to join a pub and why, how to see your public feed, a list of channels, your private messages etc.
- Glossary: Perhaps a page accessed through the More button that defines terms for Patchwork. How does this client approach Channels, Likes, Pubs, etc. and a Markdown style guide (how to publish a picture, for example)
- Opening animation or video: Instead of a getting started page, a short video that plays that similarly details the bare essentials for geteting started within Patchwork.
Built with git-ssb-web