The following chart comes from Google Trends, and reflects the growing interest in App Inventor, based on searches for “MIT App Inventor” on Google.
Because App Inventor has been viewed as a training tool in K-12 level schools, and some introductory college courses, searches for App Inventor information have gone down during the northern hemisphere summer months, when school is not normally in session. This accounts for the up and down movement in the trend line.
This chart shows a relative level of interest for the top countries searching for “MIT App Inventor”.
RT @AppInventorPlus: Interest in App Inventor continues to grow: https://t.co/AevGj0740i #Android #AppInventor #STEM
Johan Xt. Olsen liked this on Facebook.
Manto Anelli liked this on Facebook.
I like AI2, but it needs to improve on the blocks manipulation.
When projects start getting bigger, it gets hard to have an overview of the blocks and to find correlated pieces.
Debugging on this UI becomes literally a Drag. If I try to use the mouse wheel it doesn’t scroll.
Are there any plans to ease the debugging process?
Hi Ronaldo,
I agree – when programs get large, the blocks get hard to manage. I saw one program that was sufficiently large that editing just bogged down completely. If you have not already done so, you might try using the “Collapse block” feature. Right click the mouse with the pointer over a block and select “Collapse block”; to reverse, right-click on a collapsed block and select “Expand block”. This helps somewhat.
AI version 1 had an actual debugger, of sorts, that enabled the programmer to view variable values on the Android device or emulator. But that went away with AI version 2. It would be great if they would bring that capability back to simplify debugging apps.
The major new feature they’ve announced recently is the ability to create add-on extensions to App Inventor, which should lead – eventually – to third parties creating libraries of new routines we can use our own apps.
Ed
Alessandro Queiroz liked this on Facebook.