Coming Soon to Google's App Inventor for Android

Yesterday, I mentioned that languages like Java may be better for programming apps and it turns out that Java is the language to use. I was exploring Google's App Inventor for Android, looking for a way to upload code I had written by hand, when I stumbled upon the FAQ page. That was one of the questions. Google claims to be working on a way to upload Java code to the Block Editor so that more complex apps can be developed. So if you are looking to use Google's App Inventor for Android, then you should learn/use Java to write your programs. However, you must also note that there are several limitations in using Google's service. One is that the app can only be so big before it cannot be uploaded to the Android Market. Google is currently working on the problem, but it is still a restraint at this point. Also, while you may soon be able to upload Java code to the site, you will not be able to download anything off the site for use with other software. You can share the programs you create through Google's App Inventor for Android, but only one person can work on a specific account at a time. This limits the ability of multiple people to create an app together, but it still can be done. Personally, I am really looking forward to being able to upload code to the site because then I can write the basic functions of my app in code, then handle all the visuals on Google's App Inventor for Android.

The Debugging Process

After you have run your app on the emulator, you will undoubtedly discover bugs in the program. Thus the debugging stage begins. Debugging is the process of going through the program and fixing all the tiny errors in the "code" so that the programming will perform as expected. It is basically the same process using Google's App Inventor for Android, except you aren't dealing directly with the app's code. Debugging a program can take an enormous amount of time, even for experienced programmers. The issue is that each time you "fix" a bug other bugs can be created/revealed. This makes a process that could take a few hours to complete turn into a several day long battle.
Using the App Inventor for Android, the debugging process takes longer than it might using codes like C++ because the only way to discover errors is through testing it on the emulator or an Android device. It is also not always as easy to recognize which part of the program has errors. Usually, you can only identify one error at a time and even when the bug is identified then you have to figure out how to fix it using the Block Builder tools. App Inventor for Android is a lot easier to understand and use of the user has at least some knowledge of basic programming languages like C++. For example, knowledge of Boolean is essential to debugging most apps. But the most important part of debugging a program is not giving up.

The Simulator

Once you have finished programming an app, you have to test it out to ensure it will work. On Google's Inventor for Android, you can either plug in you Android phone or use the emulator Google provides. When you attempt "HelloPurr" Google will tell you how to connect your Android phone to the app builder. If you are like me and your Android phone is not compatible, use the emulator. While the emulator is a fabulous tool, it does not always work. It requires a lot of processing power because it simulates all the functions of a typical Android phone. If you are using the emulator on a laptop, I suggest you close unnecessary windows to prevent potential slowness.
To use the emulator, open the block editor. Once it's open and you are finished the program click "New Emulator." A message will pop up telling you how to use the emulator and warning you of potential slowness.When a picture appears on the simulated phone, it is ready to be connected to the app. Go to the block editor again and click on the box that says "Connect to Device" a list should appear with the name of the emulator on it. Select the emulator and wait for the app to load. Go through the processes of your app. If everything preforms satisfactorily then your app is complete, otherwise go back and edit the app. Remember that apps are constantly being reworked. It is rare for an app to turn out perfect on the first try.