Linked by Thom Holwerda on Fri 16th Nov 2007 19:38 UTC, submitted by anonymous
Google "This in-depth, hands-on article introduces Android, Google's Linux/Java mobile phone SDK. After a tour of Android's tools, documentation, and code samples, it suggests a path for further exploration and concludes with a simple applet showing the power and simplicity of the Android environment."
Permalink for comment 284928
To read all comments associated with this story, please click here.
On screen keyboard.
by Timmmm on Fri 16th Nov 2007 22:53 UTC
Timmmm
Member since:
2006-07-25

I've played around with Android a bit, and have noticed a few things:

Firstly there's no on screen keyboard. Anyone who's used an iPhone or iPod Touch will agree that this approach is superior to the Blackberry's tiny tiny keyboard. As this is the internet, and some people will no doubt disagree with my awesome opinion, I'd better say: 1) The screen and keyboard no longer compete for space, but share it. 2) It looks much better. 3) It really does work well. 4) It can be context-sensitive (e.g. the '.com' button). 5) It can rotate with the device to give a landscape mode.

In its current form it can't really compete with the iPhone interface as it depends on physical buttons too much. For example there is no way to scroll the favourites bar just using the touch screen.

Finally, you can't code with C++! :-( Java's ok I guess, but I must start a language war. :-)

1. Java *is* slow. Get over it.
2. I recently read a book ('Java for C/C++ Programmers') about Java written in 1996. They were praising its simplicity and the fact that it left out complex unneccessary features from C++ like templates, enums, and assertions. Guess what's been added to Java since then?
3. Who want's to write 'if ("this".equals(that)) {...'? When it comes down to it, no one really abuses operator overloading.
4. Maybe it's just me that encapsulates memory operations, but I never had any problems with memory leaks or segfaults (which Java doesn't avoid - it still has null pointers).
5. It's lack of type safety means you have to use exceptions everywhere. *And* they even say in the Java docs that it is better to be able to do type checking at compilation.

Personally I think D is the best approach to modernising C++. Java does have portability (probably the reason Android uses it) and libraries in its favour though.

Reply Score: 2