Lisa Hoover 0 Junior Poster

Twitter users are a loyal bunch and few would argue that it's a useful networking tool. The one thing Twitter is not, however, is private. While that's not a big deal for most people, it certainly is in the world of academics where it's ill-advised to have children using communication tools that anyone can view. It's a good thing someone thought of Edmodo.

Like Twitter, Edmodo is a free microblogging site, but without the subsequent privacy issues. Students and teachers are able to share notes or links to one another, send short messages or alerts, and otherwise communicate with each other in Twitter-like fashion. The difference is that everything is private, secure, and safe. While it's possible to share messages with users outside the Edmodo community, that is not the default method of delivery.

Jeff O'Hara and his business partner Nic Borg know a thing or two about what schools need in a communication tool. O'Hara, a network administrator in a suburban Chicago school district contacted Borg, a Web developer for a neighboring school district at the end of 2007.

"My initial idea was actually to start a video sharing site for educators," recalls O'Hara. "I had known of Nic's work that he had done at my wife's school district and was impressed with his programming skills so I approached him to see if he wanted to work on some things. I had become so involved in twitter, we thought a microblogging site with private groups would be an excellent e-learning tool."

Built with a standard LAMP stack, it took O'Hara and Borg about 10 months of working nights and weekends to get Edmodo ready for this week's launch. To avoid service outages, the pair say they will constantly monitor load capacity and are ready to move to a dedicated server if and when the need arises.

Though there are other communication tools on the market, O'Hara points to privacy as the number one thing that sets Edmodo apart from similar services. "It's created solely for the teacher and privacy of their students, but also bridges the gap between privacy and being public by the teacher having sole discretion on if they want to make any post public."

O'Hara and Borg are busy working out kinks and addressing any bugs that crop up during Edmodo's first week as a live service. "We wanted to get Edmodo out the door for the school year so we scrapped a few features in order to launch. After that, we have some other ideas for some other web 2.0 tools for use classroom," says O'Hara.

Services like Edmodo often sound great conceptually, but their value doesn't often take shape until users have a chance to check it out for themselves. Response so far has been very positive. Indeed, one teacher's response -- , natch -- may have inadvertently provided the company's new tagline when he proclaimed Edmodo "Microblogging designed for education."

Dani AI

Generated

A clear, useful snapshot by about why teachers wanted a private, Twitter-like classroom tool. For readers visiting this thread years later: the Edmodo service changed ownership (acquired by NetDragon in April 2018) and the free consumer-facing Edmodo.com platform was discontinued on September 22, 2022 — these events affected availability and how districts procured the product. (en.prnasia.com)

Legal and privacy context matters more than UX alone. Federal guidance treats school-vendor relationships and student data seriously: FERPA governs educational records and the use of third-party contractors, and COPPA applies when personal information is collected from children under 13. School districts are expected to use written agreements, define permitted uses of data, and follow parental-notice/consent requirements where applicable. (studentprivacy.ed.gov)

Practical checklist for classroom microblogging and small-group social tools:

  • Require district procurement and a signed Data Privacy Agreement (DPA) specifying data ownership, retention, deletion, and export rights.
  • Use invite-only classes/groups with teacher-generated join codes and approval flows; disable public posting by default.
  • Minimize PII: prefer initials, avatars, or school-only handles for younger students; avoid location or contact fields.
  • Set moderation and incident procedures: teacher moderation, clear posting rules, and logging/archiving policies.
  • Maintain an exit plan: regular exports/backups and contractual guarantees for data return or deletion. (nsdpa.org)

Longer-term: cloud edtech platforms evolve (acquisitions, business-model shifts, shutdowns). District vetting should weigh privacy controls, data portability, procurement paths, and classroom workflows when comparing alternatives (Google Classroom, Microsoft Teams for Education, Canvas, Schoology, Seesaw, etc.). Clear policies, teacher training, and a documented DPA are the most effective safeguards for student privacy regardless of the specific tool.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.