The current Android Studio guide seems to assume that readers have already worked through the Blocks tutorial, which makes it harder to use as a true standalone onboarding path. The intro says it walks users through “configuring, programming, and operating” the control system, but the Android Studio section itself mainly links out to other pages and does not clearly walk a new team through hardware configuration and setup in the same way a fresh Android Studio user would expect.
A related issue is that parts of the guide still feel biased toward the older smartphone-based workflow, even though the FTC docs elsewhere now state that most teams use a REV Robotics Driver Hub as the Driver Station and a REV Control Hub as the Robot Controller. The control system overview explicitly says “Most teams use a REV Robotics Driver Hub, but select Android smartphones are also supported,” so the Android Studio onboarding flow would be clearer if that Driver Hub + Control Hub path were treated as the default/current setup, with smartphone workflows presented as alternate or legacy-compatible paths.
For example, the current Android Studio tutorial structure points to intro/config/install/manage/opmode pages, but it does not make the hardware configuration path especially obvious from the perspective of a team starting directly in Android Studio. In contrast, the hardware configuration docs do contain the needed material, including creating a configuration file from the Driver Station for either a Control Hub or smartphone Robot Controller, but that context is easy to miss if a reader starts from Android Studio and expects a self-contained workflow.
The gamepad/run example is better than it used to be because it now mentions both Driver Hub and phone usage, including direct USB-A connection on the REV Driver Hub and OTG on a phone. However, the broader tutorial still feels like it inherits assumptions from the older phone-centric setup model rather than presenting the modern Driver Hub-first experience as the primary path.
Suggested improvements
- Make the Android Studio guide standalone for first-time users, without requiring implied familiarity with the Blocks tutorial.
- Add a clearly labeled “recommended modern setup” path for:
- REV Control Hub as Robot Controller
- REV Driver Hub as Driver Station
- hardware configuration
- app/version/update expectations
- deploying and running a first OpMode
- Reframe smartphone Driver Station / smartphone Robot Controller instructions as alternative setups rather than the assumed baseline.
- Add explicit links near the top of the Android Studio guide to the exact hardware configuration and control system pages a new Java team will need.
- Consider a short “Before writing code” checklist for Android Studio teams:
- Control Hub / Expansion Hub connected
- Driver Hub paired
- robot configuration created
- SDK/app versions compatible
- first deploy path confirmed
Why this matters
New teams or mentors starting directly in Android Studio may reasonably expect that guide to be a complete getting-started path. Right now, it feels easy to miss essential setup steps unless they already know to borrow context from Blocks-oriented documentation or older smartphone-era FTC setup assumptions. The current docs already reflect that Driver Hubs are common, so the Android Studio guide would benefit from matching that reality more explicitly.
The current Android Studio guide seems to assume that readers have already worked through the Blocks tutorial, which makes it harder to use as a true standalone onboarding path. The intro says it walks users through “configuring, programming, and operating” the control system, but the Android Studio section itself mainly links out to other pages and does not clearly walk a new team through hardware configuration and setup in the same way a fresh Android Studio user would expect.
A related issue is that parts of the guide still feel biased toward the older smartphone-based workflow, even though the FTC docs elsewhere now state that most teams use a REV Robotics Driver Hub as the Driver Station and a REV Control Hub as the Robot Controller. The control system overview explicitly says “Most teams use a REV Robotics Driver Hub, but select Android smartphones are also supported,” so the Android Studio onboarding flow would be clearer if that Driver Hub + Control Hub path were treated as the default/current setup, with smartphone workflows presented as alternate or legacy-compatible paths.
For example, the current Android Studio tutorial structure points to intro/config/install/manage/opmode pages, but it does not make the hardware configuration path especially obvious from the perspective of a team starting directly in Android Studio. In contrast, the hardware configuration docs do contain the needed material, including creating a configuration file from the Driver Station for either a Control Hub or smartphone Robot Controller, but that context is easy to miss if a reader starts from Android Studio and expects a self-contained workflow.
The gamepad/run example is better than it used to be because it now mentions both Driver Hub and phone usage, including direct USB-A connection on the REV Driver Hub and OTG on a phone. However, the broader tutorial still feels like it inherits assumptions from the older phone-centric setup model rather than presenting the modern Driver Hub-first experience as the primary path.
Suggested improvements
Why this matters
New teams or mentors starting directly in Android Studio may reasonably expect that guide to be a complete getting-started path. Right now, it feels easy to miss essential setup steps unless they already know to borrow context from Blocks-oriented documentation or older smartphone-era FTC setup assumptions. The current docs already reflect that Driver Hubs are common, so the Android Studio guide would benefit from matching that reality more explicitly.