Support

LearnR is maths and English practice for primary school children, Kindergarten to Year 6. A grown-up sets up a profile for their child, the child practises on an iPad, and the grown-up reads how it is going. Questions are generated rather than drawn from a fixed list, and what gets asked next is chosen from what that child has been finding hard.

There is no timer, no score and nothing a wrong answer takes away. Where the questions come from lists every year and the syllabus content behind it, straight from the questions themselves.

A child has no password and no email address. That is deliberate: a child should not be asked to manage a password, and an account with no mailbox behind it cannot be signed into from anywhere a parent has not handed the code.

1. A grown-up signs in at learnr.muzza.tech with Google or with an email and a password.
2. On Children they add the child - a name, an avatar or a photo, the school year they are in, and which subjects they practise.
3. That screen shows a four-character login code. The child types it into the boxes at the top of the LearnR home page, or into the first screen of the iPad app.

The year and the subjects are the grown-up’s to set, and a child cannot change either. Everything else on the child’s screens - which level card they open, how long they stay - is theirs.

Four things make a code stop working, and they look the same from the outside:

• It has been used. A code is spent the moment it signs somebody in. The child stays signed in afterwards - they do not need it again - but the code itself is finished.
• It is more than an hour old. A code lasts an hour from when it was issued.
• A character was misread. Codes never contain 0, O, 1, I or L, because a code is read off one screen and typed into another. If you are looking at something that seems to be one of those, it is a different character.
• Too many wrong tries. Guessing is limited, so after several failures that browser or device is asked to wait before trying again. Only wrong codes count towards it, and a successful sign-in clears it.

The fix for all four is the same: the grown-up opens Children, taps the child, and issues a new code. There is no limit on how many times you can do that.

If a code that is fresh, correct and unused still will not work, that is a fault rather than a rule - please email us and say so.

The iPad app plays offline. Every question is generated on the device from content built into the app, so once a child has signed in they can keep practising with no connection at all. Answers are stored on the device and sent when a connection comes back, which is why a report can be a few minutes behind a child who has just finished on a train.

The website needs a connection. It is a website, so there is nothing to fall back on if the network goes: if it will not load, it will not load. If the site loads but nothing seems to save, that is worth emailing about.

A grown-up removes a child on the Children screen. That deletes the child’s profile and everything recorded against it - every answer, every practice session, their photo and their speed-run results. It cannot be undone and nothing is kept back.

To delete a whole grown-up’s account, open the menu under your picture and choose Account, then Delete account. That deletes the account and every child on it, with all of their play history, and it cannot be undone - it asks you to confirm first. If you can’t sign in any more, email us from the address the account uses and we will do it for you. Our privacy policy sets out everything either deletion covers.

A wrong answer marked right, or a right answer marked wrong, is worth telling us about - questions are generated, so a fault in one affects every child who meets it rather than only yours. Send the question as it appeared and the answer your child gave, and quote the year and subject if you can.

The same goes for a question that is unreadable, badly drawn, or asks something no child that age has been taught. Both subjects are written against the syllabus, and a question in the wrong year is a content bug.