Howdy Google, Android APIs are a large number


It has been years since I made any mobile improvement. Much of what I’ve accomplished has been with cellular app dev structures like Appcelerator.

The last time I did anything vast was a few hacks at the Android client for Open Far-flung Lower back in 2008. The APIs weren’t bad then, and the general development experience wasn’t too harsh. My fundamental issues are associated with my inexperience in coding cellular (for instance, how do I pass statistics between sports?).

How to make Android an actual part of your commercial enterprise How to make Android an essential piece of your commercial enterprise Android smartphones and tablets can now competently be part of iPhones and iPads for your cell portfolio.

Examine Now

[ Get the best office apps for your Android device, and explore 10 Android apps developers will love. | Keep up on key mobile developments and insights with the Mobile Tech Report newsletter. ] I thought that Android api could have stepped forward by way of now. Desirable gosh changed into incorrect.

Crummy documentation

The documentation for Android has exploded into a multitude. Many of the Google web pages and various community websites are nearly outdated. It’s like going to a dilapidated town where the gasoline station advertises a gallon of fuel for 88 cents and realizes the vicinity has been closed for about 18 years.

Yet humans are writing millions of Android apps. Why does no one seem to be doing the paintings and maintaining the documentation up to snuff?
OMG, such a lot of documents

Related Articles : 

There was an API way and an XML way to do almost everything in Android. Maybe it’s still like that, but it isn’t apparent. Nowadays, you have to edit at least two documents, probably three, to do nearly anything. With the brand new protection version, you know, you not only ought to specify what permission you want within the XML but Also Add It to your Java code.

Howdy Google

Via the manner, not one of the tutorials (come on, I best wanted touch statistics to display!), without a doubt, I’ll let you know this. Did you, without a doubt, replica Solar? The APIs seem like they have been designed through the Java Community Process. When this all commenced, a part of how Google was given itself in hassle changed into taking the first-rate of Java and making an API that tasted a chunk more significant like Ruby than like Java.

I flavor that manufacturing in the current Android unit-to-create-a-locator-to-create-a-factory-to-generate-a-locator-to-locate-a-singleton sample that the Java network System and Java EE turned into so fond of making. Combine that with the ton of XML, and it gives me gas.

Speaking of that safety model, what turned into the factor of making me write it two times? Half of the API adjustments I’ve noticed don’t appear to have any brilliant cause. Holy crap, It’s J2EE!

Whine: I don’t need to jot down Java anymore

I wager a part of my issue because I don’t need to write conventional Java anymore — a lot of typing, so little cause for the typing.

Whether using Scala or present-day JavaScript, I’m ready for an exchange. I thought Apple gratuitously wrote a language with Quick … And there was an element of that. Google ought to use the identical method but pass JavaScript instantly and smoothly on this big mess of an API It has created.

I still love my Android smartphone. On the other hand, my female friend swears through her iPhone and uses stuff like Locate My Friends, which creeps me out. I imply Tim Cook’s dinner blocked me on Twitter for retweeting an editorial about Apple’s exertions regulations in China. Maybe I’m paranoid, but I don’t want Apple to know who I am always. Instead, I’d tell Google where I am at all times (like it wouldn’t be capable of extrapolating that anyway). I cannot wait to grab one of the new Motorola Force Zs and purchase one of these battery modules, the boombox, and the projector. (Someone asked why I’d want the projector, and I said, “Do assignment things!”)

Apples circulate to create a new language, which appears to be a chunk much less cracked to me now. Writing Android stuff feels like writing J2EE in 2002. I have an XML butcher.