FAQ
Practical answers for schools, teachers, administrators, and program leaders considering a bubble STEM system.
If you do not see your question here, reach out. We would rather help you make a confident decision than push you toward the wrong fit.
You can. For personal use, that can be a fine option. The difference is that most off-the-shelf drones are not designed for classroom use.
They are often harder to maintain, less structured for shared use, and treated as disposable when something breaks.
bubble is built as a classroom system. Students can repair, modify, and keep improving what they use, so the learning does not stop at first flight.
Yes. The system is designed around shared use, clear setup, and repeatable classroom structure.
Students typically work in pairs or small groups, which reduces chaos, increases collaboration, and makes it easier for teachers to manage the room.
Programs can start in surprisingly small indoor spaces and expand into larger environments as confidence grows.
Gyms, cafeterias, classrooms, and maker spaces can all work depending on lesson goals. A dedicated lab is not required, but a consistent, organized working area is helpful.
No. Many programs begin with teachers who are learning alongside their students.
The system is structured to make first success approachable, and support is available when needed. You do not need to be an expert to get started.
That is common. Many kits are designed for a single lesson or a short burst of excitement.
bubble is designed as a system, not a one-time activity. Students start with a guided build, then move into modification, repair, redesign, and new challenges.
The drone is the entry point, not the end point.
The larger value is the design process around it: building, testing, improving, printing replacement parts, and expanding into new forms like rovers, hovercrafts, or custom projects.
Yes. bubble does not need to replace everything else in your program.
It can complement robotics, CAD, 3D printing, electronics, aerospace, and engineering pathways already in place.
Those are strong systems. bubble is not meant to attack them or copy them.
It adds something different: open-ended iteration, real-world flight, repairability, and a stronger connection between design decisions and visible outcomes.
A printer expands the system significantly, but you do not need to begin with a full lab on day one.
Schools can start with a single evaluation or classroom system, then expand into printing as the program grows.
That is part of the design philosophy.
Most failures are not meant to end a program. They become teachable moments. Frames can be reprinted, and parts are built around common, well-documented components.
The system is designed to be open. Files, parts, and programming pathways are intended to support modification, repair, and growth.
Students learn more when they can change what they build.
Yes, with the right setup and planning.
The system is intended to support active, collaborative classroom environments rather than one student using one device while everyone else waits.
bubble systems are designed to work in real classrooms, labs, and engineering spaces without complex infrastructure.
The system does not require a dedicated lab, but it benefits from a consistent, organized working area.
No specialized electrical infrastructure is required beyond normal classroom or lab access.
The system is designed to remain lightweight and does not depend on high-end hardware.
These systems are educational tools and should be used with structured guidance, especially in classroom environments.
bubble systems are designed to be repaired and maintained, not replaced. Ongoing operation depends on simple, repeatable maintenance.
The system can grow from a small pilot into a full classroom or lab deployment without needing to start over.
bubble is designed to reduce risk, not pretend that a flying system is risk-free. The aircraft is lightweight and built around protective propeller shrouds, controlled classroom operation, repairable parts, and supervised use.
Like any moving electromechanical system, it should be operated inside a defined flight area and under clear classroom procedures. Safe use depends on both the design of the product and the way the program is managed.
Students begin with clear operating rules before they fly. Classroom use should include instructor supervision, pre-flight inspections, a designated takeoff and landing area, controlled student positions, and disarmed power whenever the system is being handled or repaired.
Propellers, guards, batteries, and structural parts should be inspected regularly, and damaged parts should be repaired or replaced before the next flight. bubble also provides guidance so teachers can establish a repeatable routine instead of improvising safety rules during class.
For programs in the United States, fully indoor operations are not governed by FAA Part 107 because FAA drone rules apply to outdoor operations in the National Airspace System. School and district safety policies still apply indoors.
Outdoor educational flights may operate under the Exception for Limited Recreational Operations or under Part 107, depending on the purpose of the flight. Registration, TRUST, Remote ID, and airspace authorization requirements can depend on aircraft weight, operating purpose, configuration, and location.
The school or operator remains responsible for choosing the correct operating path and following applicable federal, state, local, and institutional rules.
Indoor use can be authorized by the school or district and managed through its own facility and safety policies. A classroom, gym, cafeteria, or other fully enclosed space can provide a controlled environment for instruction.
Outdoor use requires two separate checks: permission to take off and land from the school property, and compliance with the FAA rules for the airspace above it. Property permission does not automatically provide airspace authorization, and airspace authorization does not automatically provide permission to use the property.
Outdoor sessions should use a controlled operating area, remain clear of uninvolved people, and be reviewed against current airspace and local restrictions before flight.
Not every configuration includes a camera, and the core system can be used without one. Some kits and expansion options use a removable micro FPV camera to provide a live first-person view through classroom goggles.
The camera is intended as an optional piloting and learning tool, not as a requirement for the program. Schools can choose camera-free operation or remove the camera to match their privacy policies. Any recording-capable accessory added by a school should be managed under its existing consent, privacy, and data-handling rules.
Many schools do not begin with a full program purchase.
The most common path is to start small, validate the system, and grow once results are visible. That can mean a single evaluation kit, a pilot group, or a supported classroom sponsor.
No. The system is intentionally designed to scale.
Schools can begin with one system, then expand into small group use, full classroom deployment, and later full lab capability.
Because you are not buying a consumer gadget.
You are investing in a classroom system designed to be shared, repaired, reused, and expanded over time instead of thrown away when something fails.
Yes. We are actively exploring ways for supporters to help fund access for schools.
That can be a strong option when interest is high but timing or budget is still catching up.
Yes. Schools are not expected to figure everything out alone.
The goal is not just delivery. The goal is successful use in a real classroom environment.
Yes. That is one of the main reasons to start a conversation rather than guess from a product grid alone.
Different classrooms have different constraints, and the system should fit your reality.
That is exactly how the system is designed to work.
Start with one, validate the fit, then expand into full classroom or lab-scale deployment when the time is right.
The cleanest path is usually to start with a conversation and a small pilot.
That gives your team a chance to see the system in context before scaling up.
Start by deciding what success means for your program. Useful measures can include participation, completed builds, flight competency, troubleshooting and repair cycles, design iterations, teamwork, engineering checkpoints, and student reflections.
For a pilot program, a simple starting rubric and an end-of-program review are often more useful than collecting large amounts of data. The goal is to document learning and program improvement without gathering unnecessary personal information.
bubble can also help a school shape a practical scorecard for internal reviews, administration updates, or grant reporting.
The best setup depends on your students, your space, and your goals. We would rather help you make the right decision than push a one-size-fits-all answer.