sheen.bot logo

← Insights

OnBot Java or Android Studio: Which Should Your FTC Team Actually Start With?

Nov 20, 2026·Sheen Robotics
OnBot Java or Android Studio: Which Should Your FTC Team Actually Start With?

Start with OnBot Java to eliminate driver, Gradle, and laptop permission hurdles during your rookie season. Only migrate to Android Studio once your team hits three specific milestones: Git version control, desktop path simulators, and external vision libraries.

Unless your team already includes a seasoned Android developer and a fleet of unlocked, high-spec laptops, you should start with OnBot Java. It gets your robot moving on day one by shifting the entire development environment onto the REV Control Hub, bypassing the driver installations, massive Gradle downloads, and administrative permission blocks that stall novice teams for weeks. You should only switch to Android Studio when your software demands force you to—specifically when you require multi-developer Git workflows, advanced motion profiling simulators, or third-party computer vision dependencies.

The School Laptop Reality and the OnBot Advantage

In most South African schools and community clubs, the programming environment is not an open, pristine development lab. It is a locked-down school-owned laptop trolley, a shared family desktop, or a learner's entry-level notebook running an Intel Celeron or older Core i3 processor. School IT administrators routinely block USB debugging drivers, restrict local administrative rights, and throttle peer-to-peer network discovery over enterprise Wi-Fi networks.

Android Studio is a resource-intensive integrated development environment (IDE). A fresh installation requires downloading several gigabytes of SDK components, build tools, and Gradle dependencies. On a budget laptop running on battery power during load-shedding, indexing an Android project and running a local build can take minutes per iteration. If a USB cable disconnects midway through an Android Debug Bridge (ADB) flash, the driver state can lock up, leaving novices stuck in troubleshooting loops before they have written a single line of control logic.

OnBot Java circumvents these failure modes entirely. The editor and the Java compiler reside inside the REV Control Hub itself. The workflow requires only two steps:

  • Connect the student's laptop, tablet, or Chromebook to the Control Hub's local Wi-Fi access point.
  • Open any web browser and navigate to 192.168.43.1:8080.

The code is typed into the browser, compiled onboard the Control Hub's internal processor in seconds, and saved directly to its flash storage. No software is installed on the programming machine. If a laptop battery runs flat during a workshop, the student simply moves to another machine, connects to the robot's Wi-Fi, and continues exactly where they left off.

The Community Elitism Trap

Experienced teams on international forums frequently dismiss OnBot Java as a toy, advising rookie teams to jump immediately into Android Studio. This advice comes from teams with dedicated mentors, institutional memory, and years of existing code repositories. For a new team, adopting Android Studio prematurely introduces an overwhelming cognitive burden.

A novice programmer cannot easily distinguish between a syntax error in their Java code, a failed Gradle dependency sync, a misconfigured Android manifest, and a loose USB-C port.

When an error occurs, the beginner needs to know that the issue is inside their runOpMode() method, not buried inside a 100-line Gradle build log. OnBot Java isolates the programming logic from build system configuration. Students learn Java syntax, object-oriented concepts, and the FTC SDK hardware maps without having to manage the plumbing of the Android operating system.

The Three Milestones That Force Migration

OnBot Java is an exceptional onboarding tool, but it has concrete architectural limits. Staying on OnBot Java too long will eventually cap your robot's competitive ceiling. You should plan your migration to Android Studio only when you hit one of three specific engineering milestones:

  • Milestone 1: Collaborative Multi-Programmer Workflows (Git). OnBot Java stores source code on the robot. It does not natively integrate with Git or GitHub. While you can download zip archives of your source files, you cannot easily resolve merge conflicts or track granular commits. When you reach the point where two or three coders must work on autonomous routines and tele-op code simultaneously without overwriting one another, migrating to an Android Studio repository on GitHub becomes non-negotiable.
  • Milestone 2: Autonomous Motion Profiling and Simulators. Competitive autonomous routines increasingly rely on advanced path-generation libraries such as Road Runner or Pedro Pathing. These frameworks make extensive use of desktop path visualisers and physics simulators (such as MeepMeep) that run on the computer, not on the robot. You cannot run these desktop simulators inside a web browser connected to a Control Hub.
  • Milestone 3: Complex External Libraries and Custom Vision. While OnBot Java supports standard AprilTag detection and basic OpenCV pipelines through the built-in SDK, incorporating heavy external Java archives (.aar or .jar files), machine learning models outside the standard toolchain, or custom native code libraries requires modifying the Gradle build scripts directly.

Comparing the Environments

CapabilityOnBot JavaAndroid Studio
Host Device RequirementsAny browser (Chromebook, tablet, entry-level laptop)Decent PC/Mac/Linux (8GB+ RAM, fast SSD recommended)
Initial Setup TimeUnder 5 minutes1 to 3 hours (longer on slow connections)
Version Control (Git)Manual zip backups; no direct branching or pull requestsNative Git, GitHub, GitLab, and branch merging
Build SpeedFast (small internal compiler running on Hub)Varies (can be slow on budget hardware)
Advanced Pathing (Road Runner)Limited and difficult to integrateFully supported with visual trajectory tuners
Internet DependencyCompletely offline at the fieldOffline after all Gradle caches and SDKs are downloaded

A Practical Roadmap for Rookie Teams

Do not let IDE setup stand between your team and a driving chassis. The pragmatic development path spans two phases:

Phase 1 (The First Season): Build your entire robot in OnBot Java. Write clean, modular OpModes. Master hardware mapping, DC motor encoders, servo limits, and the built-in AprilTag detection pipelines. Download a zip backup of your code at the end of every single build session. If you need technical guidance on setting up your team's hardware architecture, review our resources at Sheen Robotics FTC.

Phase 2 (The Off-Season Migration): Once the competitive season concludes, use the off-season to install Android Studio on your primary programming laptops. Clone the official FtcRobotController repository from GitHub. Teach your students the basics of Git: staging, committing, pushing, and branching. Port your tested OnBot Java classes into the TeamCode directory of the Android Studio project. Because OnBot Java uses identical FTC SDK classes, your core code will compile without structural rewrites.

By migrating during the off-season, your programmers master version control and Gradle builds in an environment free of competition deadlines, turning what would have been a rookie stumbling block into an intentional engineering upgrade.

#ftc#java#robotics#programming#stem education

More Insights