Kuyun AI · Works to try

Help · Studying with a project

Studying with a project

Reading in another language and out loud, a reminder to study, and a briefing's daily rhythm. A course's practice sets — answers, the sheet, writing code — are Practice in a course; the overview is Projects.

Reading in another language, and out loud

In a conversation, a message written in a language you do not read carries two buttons underneath it: 译 shows it in your language, in a small window over the page that goes away with a tap anywhere outside it, and 🔊 reads it aloud. They appear only where they would help — a message in your own language has neither. Kuyun goes by the writing: Japanese, Korean, Russian or Chinese text for an English or Spanish reader, and for a Chinese reader a run of English long enough to be a sentence rather than a word like PDF. Since the buttons go by the alphabet, a Spanish reader is not offered them on an English message.

These two buttons are switched off for now in every conversation but one: a role-play practice keeps 译 under the partner's lines, with a ▶ that plays a line again in place of 🔊, and none under your own (A project's two conversations). The people running Kuyun may turn them on again everywhere. A course's own listen buttons, below, are not affected.

On a project's documents — the brief, the plan, the summary, the findings — selecting text does nothing. To change one, say what you want in the project's chat.

In a course, the text you are meant to hear — a model sentence, a line of dialogue, a new word — comes with its own 🔊 listen button to tap; a dialogue gets one button per line and a play all. This is the listen fence: your study partner marks that text as it teaches, and a teacher can mark it when writing a chapter. The button is all there is: tap it and the line plays, tap it while it plays to stop, tap again to hear it again — as often as you like, at your listening speed.

In a published course, these lines and a practice set's sentences are recorded ahead of time, so they play at once. A line added to the course since its last recording is read live, in the live voice, until it has been recorded too — that is done from time to time, not on a fixed day. When a course stops being shown to the public — its creator takes it down, archives it or makes it personal, Kuyun takes it down, or it is deleted — its recordings go with it at once.

A conversation is read as one: each speaker has their own voice — a woman in a woman's voice, a man in a man's, and two people never in the same one — and the names before the lines ("A:", "B:", "田中:") are not read out, only what each person says. A line played on its own keeps its speaker's voice. This happens whenever most of the lines start with a short name and a colon and there are at least two names; labels such as "Note:" or "Meaning:" are always read as words. Who is a man and who a woman comes from the course itself when it says so, and otherwise Kuyun works it out once from the names and lines; when it cannot tell, the voices take turns. If a voice is wrong for someone, tell the course's chat and the conversation can say who is who. A practice sentence played on its own — to write down, or to say back — is heard in the voice of the person who says it in the course, when the course says who that is.

When your study partner stops for you to go on — after a dialogue to read and hear, say — it puts the word under its message as a button: Next, or Explain that again. Tap one and it is sent as your own message, just as if you had typed it. These quick replies are the short way, never the only one: you can always type or say anything else instead, and asking a question first is fine. They sit under the newest message only, and go once anything newer is said. Kuyun's other chats can offer them too.

Exercises work the same way, through what Kuyun calls answer fences: a blank to fill shows as a box you type into — bordered, marked type here, with a line under the sentences saying so (a fill fence) — and a multiple choice as buttons you tap (a choice fence). The fill-in box belongs to work that has practice — a course: a book, an article or a library offers no blanks to fill, so a line of underscores there (a signature line, a form to copy) stays text. Your answer goes to your study partner as a normal message, and it responds exactly as it would to one you typed: its feedback on your answer, then the next item in the same reply — it does not stop to ask whether you are ready. In a language course it also gives you the whole sentence to hear and to say back with the microphone; in any other course the answer is checked and it moves on. Practice the lesson sets for your hands — slicing, kneading, playing a scale — is done away from the screen: your study partner sets the task, asks how it went, and helps with what went wrong. What you answered stays on the exercise — your words in the boxes, your pick highlighted — when you come back to the conversation. Opened as a file from the explorer, the same exercise reads as plain text, with the blanks shown as lines and the choices as a list.

For teachers writing a course: ask the project chat to put the exercises in a chapter into answer fences, or to mark sentences for listening, and it rewrites the chapter that way. Exercises written as fences never carry the answer — your study partner checks the reply, so the key is not in text a student can read.

Everything here is read, heard and practised on Kuyun: a viewer downloads none of it — no chapter, recording or table — and picks up on any device they sign in on (Sharing a project).

Reading a work

Open a chapter from the files, or press 📖 at the top of the page, and the work opens in the reader. A course and a role-play practice are the exception for the files: their lessons and scenarios are taught and played, not read, so tapping one in the files, or its practice, starts it with your study or practice partner in the conversation instead (A project's two conversations). 📖 still opens them in the reader. The reader opens over the whole screen on a phone, and in a reading window over the page on a computer. The reader has two views, and the button at the top switches between them, keeping your place:

The reader remembers which view you chose for each work on that device, until you sign out. Both views go through the work in the order it is delivered: a book's chapters, a course's lessons, an article's sections, a role-play practice's scenarios, a briefing's digests. A lesson's practice comes at the end of the lesson, as it does on its page. On a course or a role-play practice its maker locked, the reader holds only the lessons or scenarios you have finished, since the others are still locked (A project's two conversations). A chapter with a narration has 🎧 Listen at the top, which starts the player bar and keeps playing while you read (Talking instead of typing). ✕ at the top, the Escape key, or on a computer a click outside the reading window, puts the page back.

The bottom says how far through the chapter you are, as a percentage — 100% at its end. A− and A+ at the top make the text smaller or larger; you stay at the same place in the chapter, and the size is kept for the next time you read on that device.

Some works show how a word is read: a Japanese story, say, can give the reading of each word written in kanji. The page shows the words alone, so you read them as a Japanese reader would. When the chapter has readings, a button at the top (ふりがな for Japanese, Readings for other languages) puts each reading on a line just above its word, smaller and in a different type; press it again to hide them. Once you turn readings on, they stay on everywhere you read for as long as that browser tab stays open. The narration says each word once, the way its reading says it.

Kuyun keeps where you are with your account: the chapter and how far through it, not a page number, since a bigger type or a smaller screen makes more pages. Open the work on another device and 📖 takes you back there; coming back to the work, the button to continue does the same (Shelf, "A work's own page"). Listening, the player's 📖 opens the chapter you are hearing. Opening a chapter in the reader counts as having been to it — it is marked "you are here" in the files, and your study partner knows how far you read — while finishing one is still something you tell the assistant (A project's two conversations). Where a page breaks is your screen's choice, so two people's page 12 may differ. If you made the work, its own page shows it the way a viewer reads it, reader included — ▶ View in Create, or Open on your Shelf; in Create a chapter opens as a file, with Edit beside it.

Looking at a course before you sign up

A course whose owner has published it (Sharing a project, "Publishing") has a public page anyone can open without an account: its cover, who made it, the opening of its README and the titles of its lessons. There is no lesson to read and no conversation there — signing in opens the course itself. Its one button, Start free, opens the sign-in page: sign in, or follow New to Kuyun? Sign up to the sign-up page, which names the course, and the address you give there joins the signup queue; whichever way you come in, the course is waiting when your account opens. The sign-in page lists the published courses under works to try, whenever there is one.

Telling the people who made it

Found a mistake, something unclear, or a lesson that went too fast? You can tell the people who made the project: just say it to your study partner, in your chat. It offers to pass it on, and if you agree it shows you the note with Send and Cancel. Nothing is sent until you press Send — your conversation itself stays yours, and only the note you sent reaches them, with your @handle. When they answer, you get a notice, the answer appears under the note, and your study partner tells you in your chat — once things are quiet, if you are in the middle of talking — and what you can do now because of it. It remembers the answer afterwards too, so you can ask about it. Up to ten notes a day to one project. Something about Kuyun itself — the app, a button — is for the Kuyun team instead: say so in any chat.

If you remove the project, the notes you sent go with it, except ones the people who made it already answered.

A reminder to study

A course has no schedule. Its lessons are all written when the course is made, nothing is brought to you on a clock, and Kuyun sends no notice that a lesson is waiting — you study when you like, at your own pace.

If you want a nudge, your study partner offers one when you finish your first lesson together: a reminder every day, or once a week on a day you pick, at an hour you pick, on your own clock. It is set only if you say yes, and it is asked once. You can also ask for one at any time, and ask the same chat to move it or stop it. The reminder opens the course where you are, and it says the same each time — it never names a lesson, which would be out of date the day after. It keeps coming while the work on your projects is paused, after a week away or when today's tokens are spent: a reminder costs nothing, and coming back is what it is for.

Something every day

Some questions are not answered once. "Brief me every morning on the top market stories", "keep an eye on the visa rules for Japan" — say it in the chat, with the time of day you want it, and Kuyun makes a project that is researched afresh every day at that hour, on your own clock (the city you have told Kuyun you live in). Each day's update lands on the project's page and you get a notice; its summary is rewritten to say what is current today, and what changed.

Because these updates are about today, the second model that checks them is told what day it is where you are. If your plan schedules something for a date that has not come round yet, the check asks whether the routine was carried out with the most current information there is — it never faults an update for not containing next month's news.

Each day's digest is one page: titled with its date, kept to the length you asked for, leading with what changed since the day before — or saying plainly that nothing has — and giving every item its source and date. There is one a day, however many things are watched; the archive keeps every day's page as it was, each under its own date in the project's Digests. A day's page appears there only once the check has passed it: what Kuyun read and noted on the way stays in the project's working files, never among the digests. If you edit a day's page yourself, it is yours — Kuyun does not write over it.

When the check sends a day's page back — a section to cut, an item without its date — Kuyun works on that same day's page again straight away, not at tomorrow's hour, keeping what the check did not question. It tries up to three times; if the page still does not pass, Kuyun reworks the plan instead. While a page is sent back, it is not in Digests yet, and the project's chat says so. If you want to see it now, ask the chat, and it makes the change the check asked for and files the page itself.

The first update starts as soon as you ask, and from then on each one starts at the hour you chose; each takes a few minutes and is checked before it is filed, so it is ready shortly after. It comes to you: when the day's digest has passed that check, your Secretary puts it in your Home chat as a message, every item with its source and date, ending with a link to the project where every day's page is kept. A long one opens folded to its first dozen lines or so, so you can read the top and move on; the ▾ bar on the foot of the message opens the rest, and ▴ folds it again. The notice says it is there, unless you are already looking at Home. If the Secretary cannot write it that day — its model down, your tokens for the day used — the notice points at the project instead, and the digest is there as always. You can also ask in any chat — "what's in my briefing?" — and Kuyun reads it to you. You do not need a separate reminder for it; the notice is the reminder.

Reading someone else's briefing. If you view a briefing someone published, each day's page is in it, in the list beside your conversation with it. It can come to your Home chat too, if you want: the chat asks you once — or press 🏠 Send each day to my Home among the chips under its first message — and after that you switch it on or off yourself under the briefing's ⚙ → Send each day's briefing to my Home. Removing the briefing turns it off; if you start it again, the chat asks again. When it is on, each day's page comes to your Home exactly as it was written, with a link back to the briefing, as soon as it has passed Kuyun's check — at no cost to you, since nothing is written for it. It opens folded like your own, and the notice says it is there unless you are looking at Home. The person who made it is not told that you asked for it.

This is a page of Kuyun's own handbook, the one its assistant answers from — ask it in the app and it will say the same.