Use a QR Code reader app, such as QR Droid, and point your camera at this image to link your phone to the app in the Google Play store!
Interest in MIT App Inventor is growing rapidly, world wide. Many of the readers of this web site do not speak English as their native language.
To help you use the tutorials on this web site, please use the new Google Translate option in the column on the right side of every page. Select your language and this page will be automatically translated.
My native language is English. I speak a little Spanish that I learned when I was much younger, in high school. I expect to begin reviewing Spanish and improving my Spanish skills soon.
I previously posted a short tutorial on writing to and reading from text files stored on an Android device, using an App Inventor app.
Unfortunately, as some comments noted, the file being created seems to disappear – the data is written and can be read back – but the file is no where to be found on the phone!
After some research, I now know where the file is – and also how to copy the file from the phone (or tablet) to your personal computer. While the solution to finding and saving the file to your computer is ultimately easy, I need to update the tutorial and explain some things about the Android file system. You will also need to install a free app on your phone in order to copy the file to your computer.
I have posted an updated tutorial that explains the details and shows how to store your files in the right location, how to find them (they are hidden from most views), and how to copy them to your personal computer.
From the MIT App Inventor web site:
Summary: We have been having problems with storing “assets” image, sounds and other objects that you upload to your projects. We are working with Google to resolve these problems as soon as possible.
Things to be aware of:
If we fail to read an asset when you load your project, we substitute a zero-length file. Be careful exporting your projects, as assets may be missing from the “.aia” file exported. Make sure you keep a local copy of your assets on your own computer.
We have been making modifications to the system to mitigate the worst of the problems. In particular we will never serve up a missing asset to the “buildserver” when you package an App. This ensure that if you successfully package an App, the resulting APK is valid. If we fail to read an asset, you will get a “Build Failed” message. If this happens, just keep trying the build. It may work the second or third time around. If it never seems to work, you can remove your assets from your project and upload them again. This may help.
There are 33 introductory tutorials available for the “Hour of Code” project (teachers may optionally create their own as well).
Use caution in interpreting the hype over “Hour of Code”. It’s a primitive introduction to some limited programming concepts; many of the tutorials have limited association with computer science. If your expectations are set appropriately, its fine.
Most Android apps are written in the Java programming language. Google’s Android software development system converts “source code” (a text file) written in Java, into the code that runs on the Android device.
In many programming language systems, source code is converted into the “machine instructions” of the processor. The processor does not speak “Java” but speaks its own language. A program called a “compiler” converts the original program source code into the “machine language” of the processor.
Many programs for Windows, for example, have been converted into the individual instructions that are processed by an Intel or AMD processor. The “compiler” converts the program source code into a .exe file that contains the machine language instructions of the Intel and AMD processor.
But what if you wanted your program to run on a hardware device that has a Qualcomm or ARM processor?