Archive for December, 2009


Posted: December 31, 2009 in Android, Java, Mobile
Tags: ,

You do know if you find someone advocating TDD for Mobile Applications and UDD for the underlying OS development to run like hell, right? Why? Because User Driven Development where the unit tests are not set in stone until middle  or end of development is what actually works for mobile application development. Think about it, when do you do optimization? Which is first optimization or unit testing?

And you will see some hype companies claiming its otherwise, including some OEMs that should know better.

Reblog this post [with Zemanta]

I debated how I should do this post. I am going to talk about certain points and behaviors without naming people as I can more points across without us focusing on names and titles.

1. Apps pre-installed on devices. Be EXTREMELY CAREFUL.  It is my experience that both OEMs and middleware companies will after having chosen which APPs to be pre-installed per device to inquiry of non-informed android  app companies in order to reverse engineer ideas.  Not just foreign OEMs and companies. This is not to say you canto trust its just to say trust upon proof and verification of honesty.

2. Use non-OEM  IDEs and Android plugin tools.  Handset OEMs have an agenda to lock you in to using their tools to develop for their handsets and they do this usually by limiting power of the plugins and IDE tools. Some OEM personnel will even go so far as to be disingenuous in stating that additional plugins can be installed beyond SVN/CVS despite it being not true of that specific OEM IDE edition. do not fall for that effing bullshit.  That is not to say that you cannot use JetBrains, Netbeans and other android plugins. in fact certain Netbeans infrastructure is used in certain android tools in the android sdk and both JetBrains and Netbeans IDEs are comparable to Eclipse and Google’s ADT.

3. Okay, making money.  Ad wise if you can get USA application users you can make some serious ad money revenue.  On the non add side money made will tend to come about if you build a service coupled with the application that adds to the application in some manner. Once we have the information on Jan 5th about Android Market changes that answer will of course change and improve.

Now, I have caught both domestic and foreign companies pulling above mentioned bad behavior towards both android developers and android application development companies.  That is why I am some pleased that Google with Nexus One is determine to kick their effing heads in. Nexus One gives us leverage against the abuses outlined above. I look forward to the Android 2.1 SDK from Google coming out shortly.

Reblog this post [with Zemanta]

What is in 2.1?

Posted: December 28, 2009 in Android, Java, Mobile

The guess is the Dalvik that was prototyped for the Eclair builds is fully operational in Android 2.1. That basically means a doubling of Virtual Machine performance. At this time that is the only solid information I have of what has changed between Android 2.0.1 and And Android 2.1..

NexusOne Invites

Posted: December 25, 2009 in Android, Java, Mobile

If Google wanted to really improve their open stance, what better way than to give Nexus One Purchase invites to everyone who ever submitted a bug report for the Android OS.

Technorati claim

Posted: December 25, 2009 in Uncategorized

QXRWH6NHQNH2 just to make sure I get listed on Technorati. Have a nice xmas.

SE Android SDK AddON

Posted: December 22, 2009 in Android, Java, Mobile

SonyEricsson released their SDK addon for X10. You need ot instal 1.5/1.6 for the addon to work.

First proof of GooglePhone, the trademark filing(via engadget). Now, this still couldbe the ADP3 handset.

But, consider these differences. Droid is trademarked by Lucasfilms and thus one of the reasons why Android2.0 cold not be released source etc was that the trademark license agreement had to be finalized. With Philip K. Dick’s daughter complaints about not contacting her for permission it certainly puts Google in a similar situation where they have to draw up an agreeement for use of the term. TotalRecall 2090 was based on the Novel see at hulu.

If this is not ADP3, than we should see a FCC filing of a Nexus  device with US based AT&T frequencies or US CDMA frequencies as Nexus One does not have them. If its a direct response to the OPhone than we might not see that yet as some China GSM frequencies are the same as the Europe GSM frequencies and Nexus One does have the Europe GSM frequency band.

But than what differences are offered to differentiate between Nexus One and a non-Google Android distro?

Reblog this post [with Zemanta]

The GooglePhone

Posted: December 15, 2009 in Android, Java, Mobile
Tags: , ,

When Apple released iPhone, Apple INC was on the FCC license, see this. Thee is no creditable proof of the existence of any FCC license with Google’s name on it despite the hype link baiting of those of TechCrunch and others. The only thing true at this point is that Google will be selling Neus One to developers as an ADP3 device without T-Mobile subsidy and that it runs Android 2.1.

Reblog this post [with Zemanta]


Posted: December 13, 2009 in Android, Java, Mobile
Tags: ,

Like I stated before some of us disagree and know it is an ADP device with 2.1. It goes on sale to developers in Jan 2010 and its being called Nexus One and has Flan(2.1) and has the fast Dragon Qualcomm Processor.


Posted: December 12, 2009 in Android, Java, Mobile
Tags: ,

Although we differ on whether this can be described as a Google phone since HTC is the hardware partner, it seems according to Techcrunch that this may become reality before 2010. I do think the 2.1 designation is Flan. I think we are getting a 2.1SDK for x-mas.