Information about FTC App Inventor from Bruce Schafer at ORTOP
Another choice is FTC App Inventor, which is based on MIT App Inventor. This environment is a drag-and-drop block programming environment, which has similarities to the LEGO Mindstorms NXT and EV3 programming environments. Normally, App Inventor is cloud based, which has some advantages but could be a problem at schools or tournaments where Internet access is limited. In contrast, the current FTC App Inventor beta version can be installed on a laptop and once the installation is complete no Internet connection is required. App Inventor is discussed on this page.
Note: FTC App Inventor is accessed using a web browser even when though its use does not involve the Internet.
The third choice is Blocks Programming. While it is newer that FTC App Inventor it has more features and two major advantages:
(a) It does not require you to install software on your PC or Mac. It only requires a web browser, preferably Google Chrome.
(b) When you make a change to a program and save it, it is immediately available on your robot controller phone. No build, download and install process is required.
Blocks Programming is discussed on this page.
Resources for RELIC RECOVERY season
YouTube lessons on using App Inventor to create op modes including one for driving a robot during Teleop Period
Update Oct. 2016: The versions of App Inventor released in Fall 2016 have several changes that affect the lessons above.:
1. The latest version of App Inventor can be found on the App Inventor Download Page under VirtualBox Applicance Files .
2. This file was created using the App Inventor available in the fall of 2015. The version of App Inventor released in September 2016 no longer needs calls to WaitForNextHardwareCycle or WaitOneFullHardwareCycle. In fact, these blocks are no longer available from the menus. If you import the AIA files above, any use of these blocks will be greyed out. They can be deleted if you are using the current ersion of App Inventor.. You should also add a call to UpdateTelemetry after each sequence of calls to “TelemetryAdd…” as the current version will not transfer the telemetry information to the Driver Station phone until this call is executed.
3. This file has been updated to conform to the App Inventor used during the 2016-17 season.
4. Update: A beta of an updated FTC App Inventor was released in late January 2017, which fixes a bug caused the Vuforia images to overflow if loaded more than once. You will find it available for download at https://frc-events.firstinspires.org/FTCImages/2016/beta
5. The op mode in this video uses a single color sensor, a Modern Robotics Color Sensor, which is connected via an I2C port. I2C is an interface that requires that each device connected to it have a unique address. The default I2C address for the Modern Robotics Color sensor is 3C hexidecimal or 60 decimal, which is what App Inventor assumes if it is not told otherwise. If you use more than one I2C you must assign a different address to each sensor. You can leave one of them at 3C and assign the others a different hexadecimal address using Modern Robotics Core Device Discovery utility. You must then inform App Inventor of your choices using the Set I2C Address to give the address in decimal of each reassigned color sensor in the initialization part of your op mode.
If you have questions about FTC App Inventor send email to firstname.lastname@example.org