Request an App, Google API, or Service

Staff and students are invited to request new apps, Google APIs, or services to be used for instruction using a simple Google Form. Here is an explanation of the different types of resources:

• App—Apps are software programs that run on iPad or Mac devices (e.g., Safari, Keynote, Pages, Numbers)
• Google API—A Google API is a set of connections to your district Google account that allows integration with other online services (e.g., Sign-in with Google to use Padlet online).
• Service—A service is a website or app that requires a sign in (e.g., Schoology allows users to sign in with an app or website to access all its services).

Several facets are considered when evaluating a potential new app, Google API, or service (resource). The district considers the following factors:

Instructional Alignment

• Does the resource support curriculum goals and standards?
• Does the resource enhance learning, assessment, or student engagement?
• Is the resource developmentally appropriate for the intended grade levels?
• Is the resource aligned with district strategic goals (e.g., Framework 220, Authentic Learning, Digital Citizenship)?
• Does the resource promote creativity, agency, or personalization?

Data Privacy & Security

• Is the resource compliant with FERPA (Family Educational Rights and Privacy Act), COPPA (Children's Online Privacy Protection Act), and SOPPA (Student Online Personal Protection Act)?
• Is the resource aligned with Barrington 220 Board Policies, procedures, and guidelines?
• Does the resource show ads?

Technical Compatibility

• Does the resource work smoothly with district devices (e.g., iPad 11, MacBook Air M4)?
• Does the resource integrate with existing systems (e.g., Google Workspace for Education, Schoology)?
• Are bandwidth, Wi-Fi, and network requirements manageable?
• Does the resource require additional hardware or software?

Cost & Licensing

• What is the pricing structure?
• Are there additional or future costs (upgrades, training, support)?
• Is the tool scalable and sustainable long-term?
• How much storage space does the resource use?

Vendor Reliability & Support

• Is the company stable, reputable, and responsive?
• Are training resources, documentation, and customer support available?

Implementation & Usability

• Does the district already own and support a resource that is the same or similar?
• How difficult is the resource to deploy, configure, or maintain?
• Is the resource intuitive for student and staff use?
• Is onboarding or training required?
• Does the resource support accessibility features (e.g., VoiceOver, screen readers)?

Other Potential Issues

• Does the resource introduce potential negative impacts on student focus, screen time, or well-being?
• Is there evidence or research supporting the resource’s effectiveness?

To answer these questions, members of the Technology & Innovation team, members of the Teaching & Learning team, teachers, and staff are consulted. The process can take about three weeks, depending upon the resource and timing of the receipt of the request.

All of these considerations ensure that every new app, Google API, or service added to our digital ecosystem truly supports high-quality teaching and learning while protecting students, staff, and the district. By carefully examining instructional value, privacy and security, technical compatibility, cost, vendor reliability, and potential impacts on student well-being, we make decisions that are thoughtful, strategic, and sustainable. 

This collaborative review process—grounded in district goals like Framework 220, Authentic Learning, and Digital Citizenship—helps us select resources that are safe, effective, developmentally appropriate, and aligned with the needs of our community. In short, these steps allow Barrington 220 to provide innovative tools while maintaining a secure, equitable, and purposeful learning environment for all.