He said he complained to Google.
“Because of who they are and how sprawling the ecosystem is,” Mr. Siegl said, “they are held up and need to meet a higher standard than any other vendor schools deal with.”
In an emailed statement, Mr. Bout said of the company’s core education services, “In all cases, the use of these services is tied to the approval of an administrator who is responsible for overseeing a school’s domain.”
Classroom was the brainchild of Mr. Rochelle, who started Google’s education apps group, and Zach Yeskel, a Google product manager and former high school math teacher. They said they envisioned the app as a kind of “mission control” dashboard where teachers could more efficiently manage tasks like assigning and correcting homework, freeing teachers to spend more time with students. To create the app, they collaborated closely with teachers.
In May 2014, Google posted an announcement online, asking for volunteers to beta-test Classroom. More than 100,000 teachers worldwide responded, the company said, illustrating Google’s power to rapidly stoke demand among educators. That August, Google made Classroom available to schools.
“They developed a real momentum with teachers,” said Mr. Fisher of Futuresource Consulting. “Google Classroom was key to that.”
That was too fast for Chicago Public Schools.
Administrators there wanted to test Classroom first to make sure it complied with district policies and fit their teachers’ needs. So they set up a pilot program, involving about 275 teachers and several thousand students, to run for the entire school year. Every month, Ms. Hahn said, she collected teachers’ feedback and sent it to Google.
“We wanted to help them do it right,” Ms. Hahn said.
One immediate problem administrators identified: School board policy required employees to keep records of cyberbullying and other problematic comments. But Classroom initially did not do that. If a student wrote something offensive and a teacher deleted it, there was no archive.