Creating an app for Android doesn't require a full-blown integrated development environment. There are several simple, easy-to-learn and easy-to-use tools that make programming Android apps a breeze. Michael Lehman introduces MIT App Inventor 2, Basic4android, and a few other entry-level development environments to build your own app. He'll show how to test apps on an Android emulator or directly on your phone or tablet, and demonstrate tools for building hybrid apps that run on Android, Windows Phone, and iOS devices, as well as straight on the web. Start building your first app with these simple tools today.
Instructor •. Skills covered in this course • • • Course Transcript We've talked briefly about using the Android Emulator for testing, but let's look in detail at some of the aspects of using the Android Emulator and why it's convenient and some things to watch out for. In order to fire up your app in the Emulator you come up to connect and you select emulator. The emulator fires up. Waits 20 seconds to make sure everything is installed properly and fires up the app companion and then deploys your app to the app companion so that you can begin interacting with it. What's important to remember that the emulator is an emulator, it's not a device.
Troubleshooting for App Inventor 2. Quick Fixes for Common Issues. Auto Update Issues ▻. Using the Emulator ▻. App Inventor Setup Software ▻. Video series on how to program in MIT Android App Inventor.This video shows how to connect to the emulator ifso that you can program even if you have no phone. Best Emulator for Mac - OpenEmu.
So therefore what you're going to see is still an approximation of what someone will see on a device. And in particular, there are multiple versions of the Android Operating System. And the one that's included with the emulator inside App Inventor 2, is one of the earlier versions of the Android Operating System. So, if you want to see how your app is going to look on a more modern device, you'll want to • Practice while you learn with exercise files.
Started evaluating MIT App Inventor (ver 2.2) on Windows 7 (from Administrator account). Since I don't have Android devices, I have to use an emulator. AiStarter.exe and emulator.exe both work when explicitly started, but when I start aiStarter.exe and on Chrome and then do Connect/Emulator, emulator.exe is not started, and aiStarter disply messages like: 127.0.0.1 - - [16/Dec/2014 04:15:13] 'GET /echeck/ HTTP/1.1' 200 38 The system cannot find the path specified.
Problem checking for devices: status 1 I tried disabling Chrome extensions, and trying to start from FireFox and Maxthon browsers, with identical negative results. Both Googling and searching didn't help. • What is the failed path in the error message referring to? • Any suggestions how to debug App-Inventor/emulator startup failure? Since no remedy seemed to help, I decided to start from a clean slate.
I went to and followed 'How to Update the App Inventor Setup Software' • Uninstalled current App Inventor • Booted my machine • Downloaded the latest Windows installer from • Installed the AppInventor_Setup_Installer_v_2_2 (1).exe that I downloaded, accepting all the installer's defaults. The installation directory was chosen by the installer in C: Program Files (x86) AppInventor • Logged out and after logging in again - aiStarter is running • Killed all the BlueStack processes • Tried Connect/Emulator. Emulator won't start, though it's not failing as previousely • Started emularor using run_emulator.bat • After a few tries, finally emulator is syncing with App Inventor 2. Outlook for mac view mail and calendar at same time.