A starting prompt
Paste this into the builder and change the names, rules and colours to yours. It produces a working first version; everything after is refinement.
No login, no data, no problem
The single decision that makes a school app easy is no accounts. Notices, timetables, homework lists and resources are not secret; publishing them in an app anyone in the class can install avoids every child-data policy question and every forgotten password. Personal state — which homework is done — stays on the student's own phone. Say "no login" in the prompt and the builder designs around it.
Content teachers can update in a spreadsheet
Notices, homework and quiz questions all load from published Google Sheets. Add a row, the app updates. This is the same trick used across our use cases and it is the reason a teacher can run the app alone for a whole year.
Reminders that reduce late homework
Each homework row has a due date; the app schedules a local notification the evening before at a time you choose. Students who have already ticked it done do not get the reminder. It is a small thing that changes outcomes.
Whole-school variant
For a school rather than a class, ask for a "select your class" screen on first launch that filters notices, timetable and homework by class, and an "all school" notices category. The sheet gains a class column. Everything else stays the same, which is why the same prompt scales from one classroom to five hundred students.
Publishing to students
You can share the built APK directly, or publish on Play as an unlisted app and hand out the link. If the audience is children, keep the app free of ads and tracking — the builder produces exactly that by default — and read Play's Families policy before choosing a target age group in the listing.