Choose free classroom platforms and set up a class section safely and practically.
Why it matters
The right tools let students start coding in minutes and let you see their progress at a glance. The wrong ones eat lessons with login problems, installation failures and blocked websites. Choosing and setting up tools is a real part of a CS teacher's job, along with protecting students' data.
The main kinds of tools
| Kind | Examples | Good for |
|---|---|---|
| Block-based environments | Scratch, Code.org App Lab and Sprite Lab, MakeCode | younger students and first courses; no syntax errors |
| Curriculum platforms with sections | Code.org, CodeHS, Runestone Academy (CS Awesome for AP CSA) | full courses with lessons, teacher dashboards and progress tracking |
| Browser code editors | Python Tutor, online editors built into platforms | quick text-based practice without installs |
| Local editors | Thonny (Python for beginners), IDLE, VS Code | older students, offline use, real-world workflow |
| Assignment and grading | GitHub Classroom, Gradescope, your LMS (Google Classroom, Canvas) | distributing starter code, autograding, collecting work |
| Physical computing | micro:bit, Raspberry Pi, Arduino | engagement, connecting code to the physical world |
Many of these have free tiers or are free for teachers. Features, pricing and age limits change, so check each provider's current education terms before planning around them.
Choosing tools: questions to ask
- Does it fit the course? Language, level and standards.
- Does it run on our devices? Chromebooks, tablets, locked-down school laptops, slow networks.
- What does it cost now and later? Is the free tier enough for a whole year?
- How do students log in? Single sign-on with school accounts saves lessons.
- What student data does it collect? Is it approved by the school or district?
- Is it accessible? Screen-reader and keyboard support, captions, contrast.
- What is the backup? If the service is down, can you teach the lesson unplugged?
Student data and privacy
Teachers are responsible for using tools their school allows. In the US, relevant laws include FERPA (student education records), COPPA (online services and children under 13) and many state student-privacy laws; other countries have their own (for example GDPR in the UK and EU). Practically:
- Use tools your school or district has approved, or ask your technology coordinator before signing students up.
- Prefer platforms that let students join a teacher section without personal email addresses.
- Do not upload student work or names to tools that are not approved.
- Know how to delete student accounts and data at the end of the year.
Worked example: first-week setup checklist
For a new middle-school class using Code.org:
- Teacher account created with school email; section created per class period.
- Students join with a section code; younger students use picture passwords.
- Course assigned to each section; teacher previews lesson 1 as a student.
- Login cards printed for each student and a copy kept securely.
- Test on a school device with the school network, including the student login flow.
- Unplugged backup activity ready for day 1 in case the network fails.
- Parent or guardian letter sent explaining the tool, if the school requires it.
Managing the room
- Use the teacher dashboard to spot students who are stuck (no progress) during the lesson, not just after.
- Ask students to put screens down or lids half-closed during instructions.
- Keep a "three before me" rule: check notes, ask a partner, check the hint, then ask the teacher.
- Have an extension task ready so fast finishers do not drift.
Common mistakes
- Testing only on your own laptop. School devices and networks often block things.
- Signing up students before approval. Privacy rules exist for good reasons.
- Changing tools every unit. Each new tool costs a lesson of setup and confusion.
- No backup plan. Platforms go down; unplugged activities save the lesson.
- Ignoring the end of the year. Archive work, export what students want to keep and remove accounts.
Quick recap
- Choose tools for fit, devices, cost, login, privacy, accessibility and backup.
- Many good platforms are free for teachers; check current education terms.
- Use approved tools and follow your school's privacy rules (FERPA, COPPA, state law in the US).
- Test the full student flow on school devices before day 1 and keep an unplugged backup.
Try it
Open the Do tab and set up a practice class section on a free platform.