Slashdot Mirror

Intel did an ARM on x86 emulator called libhoudini for Atom based Android phones, And Intel treat Apple like a spoiled favourite child, so I'm sure Intel would be willing to share code.

https://commonsware.com/blog/2...

Libhoudini run 32 bit ARM code on x86 of course, not 64 bit ARM code on x64.

I'm sure this will be welcomed by (most users and developers alike.

However, the more control they exercise, the more danger that they will abuse it (e.g. a carrier partner asks Google to get rid of an app that acts as an SMS gateway, so users don't need to pay for carriers' SMS package).

I believe that the key to keeping this sort of abuse under control (other then clear rules) is for Google to specify which rule was broken for every app that gets rejected.

CommonsGuy wrote a good post about this (no, I'm not him):
http://commonsware.com/blog/2012/02/23/think-about-principles.html

First off, let me admit that I have not yet read the Book reviewed here, but from reading the review, it sounds like it is targeted mainly to the "new to programming" crowd.

I have started my Android Development career by reading Mark Murphy's "Busy Coder's" books, and gotten a lot of details out of his Tutorial book.
http://commonsware.com/books.html

I'm not affiliated with him, but I'd like to really recommend his books to any developer who has an existing background in either Java and wants to quickly get productive in Android Development.

As an additional bonus, all of Mark's books are available electronically or as self-published printed paper back's.

He himself is also a great guy and very active on the Google Android developer forums.

Sorry dude, but you either looked at an earlier version of the SDK or you didn't find your way around. Or you are just whining (sorry but is always a possibility).

[...]

There are (literally) hundreds of application examples that ship with the 1.5 SDK. I've mostly gone through the API samples, but there other larger ones as well. Though you may not find links to the code from the html docs.

I did have some trouble getting sample unittests running, but other than that everything seems pretty sharp.

There is a level of maturity that a SDK acquire with time, Android is still in full swing right now, but the sheer amount of samples they have in a year from release is IMHO impressive. You are going to try Android again, consider getting the books from http://commonsware.com/ (no relation to the site, I did buy the books and I am happy with the material).

Google has a minimum bid because that is the cost of production for that ad.

And your proof of this assertion is...what, exactly?

I have an ebook on the market for developing applications for the Android platform, with the print edition slated to appear in bookstores any day now. I am trying to run an AdWords campaign to help promote the book. I have 52 keywords set up in AdWords to run my ad against. 51 of them are "inactive for search" because the minimum bid is $1.00, so they won't show up on Google's sites, though it will help them show up on AdSense sites (as I understand it).

So, please explain to me:

• How it costs $1.00 to inject three lines of HTML, including one hyperlink, into search results?
• How come it costs $1.00 to do that for a search on android documentation but not for android assistance, for which there is no enforced minimum bid?

There may be valid reasons why Google has a $1.00 minimum bid on some Android-related keywords, but I have a very tough time believing that it is related to "cost of production".

Well, there's already one book out on Android development and 3-4 others in progress by various authors.

And, in the interests of full disclosure, I wrote the book I linked to above.