Getting started
Getting in
Every way in is one button, Start free — on the front page, on a published work's page and on each language's page. It opens the sign-in page: sign in if you have an account, or follow New to Kuyun? Sign up to the sign-up page, where you give your email address and Kuyun emails you a link. When you came from a work's page, the sign-up page names the work and your account opens on it, whichever way you come in. The front page itself asks for nothing. The link confirms the address is yours and lets you set a password, and using it is what makes your account. It works once, and within seven days.
Kuyun lets a set number of new people in each day. While today has places, the link comes straight away. When today's places are taken, the email says you are in the queue instead, and your link comes when your turn does, in the order people signed up — usually within a day or two. Nobody who signs up later goes ahead of you. While Kuyun is full for now, the queue waits, keeping everyone's place, until more places open.
Or sign up with Google or Microsoft, where the sign-up page offers them (Microsoft: a personal account — Outlook, Hotmail, Live). The service tells Kuyun your address and that it is yours, so there is no email to wait for and no password to choose: while today has places, you accept the terms and you are in, signed in. When today's places are taken, you join the same queue, and the email says so; when your turn comes, sign in the same way again (or use the link it sends). Your account's address is the one that service gave. You can set a password later with forgot your password? on the sign-in page. A published work's sign-up page does not offer it, because that page's own form is what opens your account on the work.
One inbox signs up once: an address that reaches an inbox already on the list — a Gmail address with dots added, or with a +word — is sent nothing. A Gmail address with many dots in it is set aside for the people running Kuyun to look at before anything is sent to it. The form may also ask you to pass a quick check that you are a person (Cloudflare's, named in Terms of Service and Privacy Policy). A work whose owner has published it has a public page you can look at first — the sign-in page lists them under works to try — with its cover, who made it and the titles of what is inside, and the form on that page joins the signup queue with that work waiting for you (Studying with a project). Signed in, a published project's link is its page, open for you to view at once.
After that you sign in with your email address and your password. Where the sign-in page offers them, you can instead use sign in with Google, Apple or Microsoft — if that account's email address is the one you signed up with (Your account). Apple does not create an account: until your link has made one, it has nothing to sign you in to. Google and Microsoft do, as above.
If the link has expired, sign up again with the same address: a new link comes, and it takes no new place. The old one cannot be revived.
If you arrived from a link in an advertisement or a post, the sign-up keeps that link's short tag (for example tt-s1), so the people running Kuyun can see which links bring people and which of them stay. Nothing else about where you came from is kept — no page you were on, no other address.
A page made for one kind of learner has a single Start free button. It takes you to sign in, or to sign up, and the moment you are in, Kuyun opens the work that page is about — the library of courses, role-plays and books — so you never have to look for it. Your browser remembers which work it was for a week, so it still opens it after you confirm your address from the email, or come back from signing in with Google or Microsoft; it remembers nothing else, and once the work has opened it forgets it. Learners of Spanish have a door of their own at /c/spanish: the six courses, the six role-plays that go with them, the shelf of readers read aloud, and how a lesson goes. Chinese speakers learning American English have one at /zh/c/english-zh (in English at /c/english-zh): six courses explained in Chinese, six sets of role-plays, and a shelf of English books read aloud, from stories written for the courses to the American classics. Learners of Japanese have one at /c/japanese (in Chinese at /zh/c/japanese): five courses from N5 to N1 explained in English, a role-play for every lesson, stories for every lesson read aloud, and 21 Japanese classics with each word's reading above it when you want it. Spanish speakers learning American English have one at /es/c/english-es (in English at /c/english-es): six courses explained in Spanish, six sets of role-plays, and the same shelf of English books read aloud. English speakers learning French, German or Italian have one each, at /c/french, /c/german and /c/italian: six courses explained in English (Mary in Paris, Emma in Berlin, Jake in Bologna), six sets of role-plays, and a library that holds them with the books read aloud at each level. Chinese speakers learning Spanish, French, German or Italian have one each, in Chinese at /zh/c/spanish-zh, /zh/c/french-zh, /zh/c/german-zh and /zh/c/italian-zh (in English at /c/…): six courses explained in Chinese (陈雨 in Madrid, 王浩 in Lyon, 张敏 in Munich, 刘洋 in Milan), six sets of role-plays, and a library with the books read aloud at each level. English speakers learning Mandarin Chinese have one at /c/chinese: six courses from HSK 1 to HSK 6 explained in English (Lucy in Beijing, with the Wang family in a hutong courtyard), a role-play for every lesson, and five stories for every lesson read aloud, written only with the characters learned so far; every answer can be typed in pinyin, tone marks optional. People learning Python or preparing for coding interviews have one at /c/python: four courses from a first line of code to data structures and algorithms, 225 coding problems you write and run in the page with hints and feedback from a study partner, a short book on the coding interview, and mock coding interviews at three levels.
The first thing you see
Home is where the day starts, and its main channel is the conversation that carries it. The very first time, a welcome written by the Kuyun team is waiting there: what the channel is for, what Kuyun can do, and how to begin. It stays in your conversation, so you can scroll back to it later. If someone invited you to work on a project with them, the welcome ends with it, as a link. Under it are a few ways to start, each one tap: three works other people have published that Kuyun picked for you (open one and it starts, with a guide to talk it through), and a few things Kuyun can make for you — a research project, a daily briefing, a course — which either send the words as your own message or open Create with the kind and the idea already filled in. Once you have said anything, the welcome and its chips scroll back like any other message. Typing works just as well: just say what's on your mind.
From the next day on, early each morning (your time), Kuyun writes you a short message there, in the language you use with it: what moved while you were away, with a link to each project that did, and an invitation to say what you want to do. Once you have not used Kuyun for two days it stops writing them, and starts again the morning after you come back. A link to somewhere in Kuyun — a project, a thread — takes you straight there; a link to an outside site opens in a new tab.
The first time you open Home on a new day, a second short message follows: Pick up where you left off, with a button for each work you had open on the last day you used Kuyun (up to two, and no further back than a week) — your own projects open in Create, a work you view opens where you read it. When something published in Explore is on the same subject, a row of Related to what you're working on follows, up to two works, each one tap to open. Only you see these; nobody is told what you were looking at. If there is nothing to pick up, there is no message.
A reply puts its answer first. The evidence behind it — log lines, the reasons step by step — is folded under a line you can tap to open, and it prints open. Several things with a state (how each of your projects is doing) come as rows with a mark for each: ✓ fine, ! needs a look, ✕ not working. Things for you to do come as a numbered checklist, with ✓ on any already done. When the shape of something is the point, a reply can draw it: a small chart of numbers over time, or a diagram of how the steps of a process connect. A diagram that cannot be drawn shows what it says instead.
Before a reply reaches you, Kuyun reads it once for you: if it is written over the head of someone who prefers everyday language — a stack trace, log lines, file paths or code names in the open, or far too long — it goes back to be written again, and you see the second version. If a reply is still too technical, or not detailed enough, just say so — "simpler, please" or "more detail" — and you get the same answer again that way, with nothing added. What you write is also how Kuyun learns how technical to be with you.
When an assistant mentions a project, a person or a feature request in the app, you see its name (an email or a notification still shows its short code): a project you can open is a link to it, and you are "you". Something that is not yours to see shows only what it is — "a project", "someone" — never its name or whose it is.
It is a conversation, not a dashboard. You can reply to it, and everything you have said there before is above it — scroll up to see previous days.
Typing / at the start of the message box, in any chat, lists the commands you can use, each with a few words on what it does. Keep typing to narrow the list, move through it with the arrow keys, and press Enter or Tab (or tap one) to put it in the box; then add what goes with it and send. Escape closes the list. For now there is one: /remark, which sends the Kuyun team a remark about the app (see "Your data").
Finding your way around
- Home — one page with two parts. The main channel is the daily conversation described above. A thread is a subject kept apart from the day: start one from any message with start a thread — it opens in the panel beside the channel with that message quoted, and a small "↳ thread" line stays in the channel so you can find your way back — or start one fresh with + New thread at the top of the thread list, and your first message begins it. When a subject in the main channel grows into its own piece of work, Kuyun offers to take it to a thread and, if you agree, opens one and gives you the link. Ask "what threads do I have?" and it lists them. The panel on the right is your thread list, newest activity first, with the ones that have a reply you have not seen marked; threads quiet for a month fold under "older", where they stay. Open a thread and that panel becomes the thread, with a ← Threads button at the top to return to the list. Drag the panel's left edge to make it wider or narrower — or click the edge and use the left and right arrow keys. This browser remembers the width you choose; double-click the edge to go back to the usual width, which follows the size of the window. On a phone the panel is a full screen: the Threads button above the channel opens it, and ✕ takes you back to the channel.
- Explore — the works people have opened to everyone — courses, books, libraries — ordered for you; see Explore.
- Create — your projects: work that continues between visits, and the ones others share with you to work on together. This is where most of the substantial work happens; see Projects.
- Shelf — what you view: the works you started or were given, and your own creations that are out, the one you last opened first; see Shelf.
- Settings (the icon at the top right) — your account, language, notifications, what Kuyun knows about you, and your files.
Every conversation opens at its latest message, and stays there while you are at the bottom. A reply too long to fit on the screen stops at its beginning instead, so you read it from its first line; scroll down through it and the conversation follows the newest message again. Scroll up and earlier messages load as you go; there is also an earlier messages button at the top. Only a batch at a time is fetched, so a conversation that has run for months opens as quickly as a new one.
When Kuyun asks you something with choices, or a sentence with a blank, you answer right in its message: tap a choice, or type in the blank and send. The same works in every conversation.
Where an hour or more passed between two messages, a small date and time sits between them, so you can see when a conversation picked up again; one you reopen starts with the time it left off. This is the same in every conversation: the main chat, its threads, and a project's chats.
When Kuyun can't reply. Sometimes a message gets no answer, and Kuyun says why. If you have used today's tokens — each account gets a million free every day, more with a subscription, and a new account comes with $50 of promotional credit, once per inbox, that is spent once the day is gone (Tokens) — it says so in plain words, and nothing was attempted: more arrive at midnight where you are. In a conversation you already had going, that note stays there with your message, so you see it on your phone and your computer alike. A brand-new conversation whose very first message was refused keeps nothing, and neither does a voice message, which is checked before it is saved — send it again after the reset. If you sent too many messages in a single minute, Kuyun asks you to wait a moment, and that note is not kept either. If instead Kuyun tried and something went wrong on its side, it says the reply failed; that note is kept, and trying again later is the right move.
Getting to know you
Kuyun does not ask you anything about yourself on your first day, and it never asks your name or where you live: it is here for learning, research and self-improvement, and neither is part of that. If you want to be called something, or want it to know your home city for the right time, just say so in the chat — "call me Mike", "I live in Paris" — and it remembers; both are yours to see and change under Settings → About Me.
Once you have come back and used it a little, it may ask a few things about Kuyun itself — one at a time, in Home's main channel, each with a reason: whether it may notify you, once there is something to notify you about; whether to put an email on the account, so a password can be recovered. Each question is a message in the conversation with its answer right in it, so it stays where you can scroll back to it; once answered or put aside, it says so. Every question can be declined, and one you do not answer is simply dropped. What you were asked, and what you said, is listed under Settings → About Me.
If something you asked for ships, Kuyun tells you and asks you once, on Home, whether it helped — one tap. Your answer goes to the people who make Kuyun with your other remarks (see "Your data"). When the team answers something you said about Kuyun, the morning greeting passes the answer on. A remark that helped improve Kuyun also earns you promotional credit (Tokens).
What Kuyun carries from one conversation to the next depends on which conversation it is. The home chat remembers across all of yours: what you worked on, which projects you started, what you decided. A project's own chat, and a viewer's chat on someone's project, remember only their own conversation — your study partner on a course knows that course and what you did in it, not your other projects and not your home chat.
Language
Kuyun replies in the language you choose in Settings, and the app's own wording follows the same choice. One setting covers both. The app comes in English, Chinese (中文) and Spanish (Español); until you choose, it follows your browser's language, and English when that is none of them.
Your account remembers its language. When you create your account, it keeps the language your browser was using, and when you choose another in Settings, it keeps that. So on a new phone or computer the app opens in your language once you sign in, whatever that device is set to. A choice you make on one device stays that device's.
A few things are still written in English whatever you choose: the emails Kuyun sends, the notifications that pop up on your phone or computer, and some of the messages that say why something could not be done.