How to Get Started with Weyd: Goal, Diagnostic, Plan
5 min read
Weyd can track your learning automatically, semi-automatically, or manually. Here's when to use each method — and why the data quality matters.
The coaching and plan adaptation in Weyd is only as good as the data it has about what you're actually doing. Users who log consistently get plan adjustments that fit their real practice patterns. Users who don't log, or who log inconsistently, get generic recommendations that don't account for what they're actually spending time on.
There are three ways to get your activity into Weyd. Each has different setup requirements and different data quality — here's how to choose.
Connecting a learning app lets Weyd pull your activity data automatically. You don't need to do anything after setup — Weyd syncs in the background.
Available integrations:
How to connect: Dashboard → Settings → Integrations → Connect
What Weyd does with integration data:
Limitations:
Best for: Your primary daily-use tools. If you use Duolingo every day, connect it on day one.
If you practice with an app that doesn't have a direct integration — or you want to log something specific like a test result, an Anki session summary, or a LingQ stats page — paste a screenshot.
How it works:
Weyd reads the image, identifies what app it's from, extracts the relevant numbers (time, cards, XP, score), and logs them to your activity record.
What it works with: Any app that shows a stats screen, session summary, or result page. If you can screenshot it, Weyd can usually parse it.
What it can't do: Screenshots give you a moment in time — Weyd can log the session stats it sees, but it can't backfill historical data from a screenshot of a cumulative stats page.
Example screenshots that work well:
Best for: Occasional logging of apps you use sometimes but haven't integrated, or importing specific results you want on record (test scores, assessment results).
If you practiced something that doesn't generate a screenshot — a conversation with a native speaker, a reading session with a physical book, a podcast you listened to while commuting — just tell the coach what you did.
How it works:
Example:
"Did 45 minutes of conversation practice with my language exchange partner. We talked about work stuff mostly. I struggled to explain my job in Spanish — kept losing vocabulary mid-sentence. Got better toward the end."
Weyd will:
The more detail you give, the more useful the log. "I studied for an hour" is logged as generic activity. "I did 40 minutes of shadowing with a JapanesePod101 intermediate episode and 20 minutes of grammar review" is logged with skill-level detail.
What kinds of sessions to log this way:
Best for: Offline practice, social learning, and anything that doesn't generate app stats.
All three logging methods feed the same underlying data model. Weyd maps each logged activity to skill categories:
| Activity | Primary skill tracked |
|---|---|
| Anki reviews | Vocabulary |
| LingQ reading | Reading, Vocabulary |
| Shadowing | Listening, Pronunciation |
| Conversation practice | Speaking, Listening |
| Podcast listening | Listening |
| Grammar exercises | Grammar |
| Duolingo | Vocabulary (A1-A2), Grammar exposure |
| italki session | Speaking, Listening |
The skill totals feed your weekly quotas (visible on the Progress page). If a skill is consistently under-quota, Weyd will flag it and suggest rebalancing.
You don't need to log every minute of every session. What matters is consistency over time — even rough logging is more useful than perfect logging for two weeks followed by nothing.
The minimum useful logging frequency: 3–4 sessions per week. Below that, the data is too sparse for pattern detection to work reliably.
If you're using a connected integration for your main study tool, that satisfies the consistency requirement automatically. Supplement with chat logging for anything else.
Connect Duolingo, Anki, LingQ, and more — see all your progress in one place.
Connect your tools5 min read
5 min read
5 min read