← Back to Home · Back to Programming

Programming · Getting Started

Spin up an FTC codebase fast

Android Studio, FTC SDK layout, OpModes, and a first-run checklist to get code on the robot quickly.

What this is

Quick path to install tools and open the FTC SDK.
Explains OpMode types and core folders.
First run checklist to avoid dead-on-arrival code.

When you need it

New laptop setup or onboarding rookies.
Fresh SDK season drop or repo reset.
Robot won’t run sample code after import.

How it works

Install Android Studio (latest stable), open the FTC SDK project, let Gradle sync.
FTC SDK layout: /TeamCode for your code, /FtcRobotController app, samples under samples/.
OpModes: Linear (run once top-to-bottom) vs Iterative (init/loop callbacks).
Push code to Control Hub via Wi‑Fi (RC app) or USB (Driver Hub as RC phone).

Common mistakes

Missing SDK dependencies (no internet on first Gradle sync).
Putting code in /FtcRobotController instead of /TeamCode.
Forgetting @TeleOp/@Autonomous annotations or unique names.
Running without selecting the OpMode on the Driver Station.

How to test it

Build in Android Studio; confirm “BUILD SUCCESSFUL”.
Deploy and open the Driver Station; verify your OpMode appears.
Run a sample (e.g., BasicOpMode_Linear) to confirm loop runs.
Check telemetry appears on Driver Station; add a custom line to verify your build.

Related problems

Gradle sync fails → check network, Gradle JDK, invalidate caches, retry.
OpMode missing → annotation/name collision; clean/rebuild.
Robot not moving → hardware map names mismatch or not initialized.