Decide who is holding the device.
An app used by a student in a lesson, a teacher preparing one, and a parent checking in at home are three different products. Most education projects run into trouble by trying to be all three at once.
Naming the primary user first makes every later decision easier: how much text is on screen, whether it works on a shared iPad, whether it needs an account at all, and what happens when the lesson ends.
Three different products
- Feature 1
Student-facing: short sessions, few words, forgiving of mistakes.
- Feature 2
Teacher-facing: preparation, grouping and review between classes.
- Feature 3
Shared devices: no personal login, or a very fast one.
Data and privacy are design decisions.
Anything involving children raises the bar on accounts, storage, analytics and third-party services. The safest apps in this space collect as little as possible and keep it on the device, which is also the simplest thing to explain to a school or a parent.
We build that way by default. Our own app has no account, no advertising, no analytics and no tracking, and its privacy policy says exactly what it does — because the app really does behave that way.
How Zynx would approach it.
Scope the one lesson or task the app must support, prototype it, then test it with the people who will actually use it. A short session with real students or teachers tells you more than a long feature list.
Procurement, device management and school IT policies also shape a release. Those are worth raising in the first conversation rather than the week before launch.