Welcome to the Avelok docs

These docs are written for the four people who actually use Avelok: the athlete, the coach, the parent, and the club operator. Pick the path that sounds like you below and you'll be doing useful work in roughly five minutes.

Avelok runs as a WeChat Mini Program for athletes and parents, and as Avelok Studio — a desktop web app for coaches, clubs and federations. The two products share one source of truth, so a session a coach runs on Studio shows up the next morning in the player's pocket, and a parent's note about a sore shoulder is on the coach's screen before warm-up.

#Pick a starting point

#What's actually different here

Three things, in plain language.

#One memory, four roles

Most apps treat each user as a separate island. Avelok treats one athlete as the centre, and lets coaches, parents and clubs see only the slice they're meant to see — current strengths, current weaknesses, what was tried last week, what's queued up for next. The athlete owns the memory and decides who reads what. Coaches don't have to start over with a new player; players don't lose their context when they switch coaches.

We call this the athlete memory and it is the spine of the product. See Athlete memory.

#Calm by design

Avelok refuses two things on purpose: notification spam, and "engagement" tricks. There are no streaks, no XP bars, no daily reminders to come back. The app shows up only when there is something worth showing — a session summary you asked for, a question from your coach, a rest-day reminder your body asked for. Most days, you should not need it.

#Sport-shaped, not generic

The AI doesn't pretend to be a general fitness chat. It knows the rhythm of a table-tennis week, the difference between technical drills and footwork drills, what a "loop against backspin" means versus a "fast push." We start with table tennis and add sports one at a time, slowly, only when we have a real coaching partner in that sport. See SaaS strategy.

#What's in these docs