Feeds

Google's Inventor gets short shrift

Creating mobile apps isn't Lego, you know

Best practices for enterprise data

Veteran tech watcher David Pogue has taken a look at Google's new building-block based development environment for Android, and he's not impressed.

The Android App Inventor follows a long line of breakthrough environments that promise to simplify application development to a series of mouse clicks. Unfortunately it seems that the App Inventor is no better than its predecessors at allowing those without any programming skills to write programs, and entirely failed to turn David Pogue into a mobile app developer.

"It’s extremely unlikely that a nonprogrammer could actually invent anything with App Inventor without the assistance of a teacher or an experienced friend, or hours poring through the App Inventor message boards" said Pogue in his review of the beta published by the NY Times. That was one of his more restrained assaults on App Inventor, which is a shame as it looks very pretty:

App Inventor is on closed beta at the moment: we've asked for an invitation and will give you a better look when we get a chance. The environment should be familiar to anyone who's used a "fourth generation" programming language that tries to use clicks for everything, but ultimately leaves you editing code to make things work.

In App Inventor those lumps of code are colour-coded to fit together - but ultimately deciding which block to use, and where to put it, is no more difficult than typing stuff.

We've used a fair range of such graphical tools, and only been really impressed by the Lego Mindstorms environment - which has the same genesis as App Inventor (both were born out of MIT projects). But while Mindstorms benefits from a very limited range of capabilities (turn motor on, turn motor off, listen to sensor, wait), App Inventor has to allow for dozens of different hardware platforms and thousands of capabilities.

Pogue spent a day failing entirely to create a single working application, or even complete the tutorials. He admits that many of his problems were down to the beta nature of the platform, but others can only be attributed to the complexity of programming itself - something that can't be hidden behind colour-coded blocks. ®

Recommendations for simplifying OS migration

More from The Register

next story
Trying to sell your house? It'd better have KILLER mobile coverage
More NB than transport links to next-gen buyers - study
iWallet: No BONKING PLEASE, we're Apple
BLE-ding iPhones, not NFC bonkers, will drive trend - marketeers
Auntie remains MYSTIFIED by that weekend BBC iPlayer and website outage
Still doing 'forensics' on the caching layer – Beeb digi wonk
Scotland's BIG question: Will independence cost me my broadband?
They can take our lives, but they'll never take our SPECTRUM
NBN Co adds apartments to FTTP rollout
Commercial trial locations to go live in September
Samsung Z Tizen OS mobe is post-phoned – this time for good?
Russian launch for Sammy's non-droid knocked back
Speak your brains on SIGNAL-FREE mobile comms
Readers chat to the pair who flog the tech
prev story

Whitepapers

7 Elements of Radically Simple OS Migration
Avoid the typical headaches of OS migration during your next project by learning about 7 elements of radically simple OS migration.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Consolidation: The Foundation for IT Business Transformation
In this whitepaper learn how effective consolidation of IT and business resources can enable multiple, meaningful business benefits.
Solving today's distributed Big Data backup challenges
Enable IT efficiency and allow a firm to access and reuse corporate information for competitive advantage, ultimately changing business outcomes.
A new approach to endpoint data protection
What is the best way to ensure comprehensive visibility, management, and control of information on both company-owned and employee-owned devices?