Developing Android Apps Visually, In 3 parts
An anonymous reader writes "Dr. Dobb's has a three-part blog (all three parts are up; this is part 1) about using App Inventor. The focus isn't so much on the technology but rather the discussion of 'can visual development let anyone program?' If so, is App Inventor really visual development? And should we be teaching real programmers about visual development. Most of the conclusions are in part 3. As a byproduct, they show you how to put App Inventor output on the Market and there are two games on the market (free) that resulted from the articles." Here's part two, to round out the trilogy.
Coincidentally I just started learning to develop mobile apps last week. I'm using Sencha Touch and PhoneGap, Eclipse, and the Android SDK. The combination works pretty nicely, and lets me build fairly pretty pseudo-native apps, working in JavaScript. Best, they will run on iOS and any future mobile device with WebKit.
My blog
Slightly off-topic, but Android development for me has been marred by the steaming pile of dung that is Eclipse. Netbeans is ok but it's android support isn't great.
I finally got around to trying IntelliJ IDEA, and hooray! Android development is now possible on my lowly 2009 PC. It is so much better than Eclipse. You should download it now and forget about Eclipse this instant. Let's see:
Cons compared to Eclipse:
* Not the official android IDE.
* Doesn't have some android tools built in (ddms).
* No GUI editor for the manifest.
* No GUI layout editor (although the Eclipse one is unusable anyway).
* Logcat always autoscrolls. It's slightly annoying.
Pros compared to Eclipse:
* The main UI is way faster and more responsive.
* The 'smart' features (code completion, refactoring etc), are even more clever than in Eclipse -- they practically read my mind.
* No retarded 'workspace' paradigm.
* The code editor is way more responsive.
* The UI is a lot more sane, and much less cluttered, even though it still has a ton of features.
* Built-in git support. Maybe this is in Eclipse, but I'm sure it is way more complicated.
* No retarded 'perspectives'.
* The UI is cleaner IMO, although it is a little win95-ish.
* I have no idea why, but it manages to detect my phone even though adb doesn't. (I know right?)
* It's just way better. There are tons of features that make you think "Wow, they really spent time implementing that (in a good way)?", random example: if you create a new class, edit and press undo, it will ask you if you want to undo creating the class!
In conclusion, fuck you eclipse. You suck.
No and no.
I have seen many people struggling to learn PHP (as part of their education). Not because they had any issues with the language itself, but because they couldn't systematically approach their problem. And if you would have read the TFA, or even simply peeked at the pictures, you would have seen that this IDE is almost a glorified code coloring editor, where words of code fit together like jigsaw pieces.
The art of programming is actually the art of reverse-engineering: you put your program together like you take your solution apart. If you don't know how to carefully dissect your ideas, then you are not a programmer.