Google Tries to Solve Android Fragmentation with New APIs
Google recently released a new tool that developers can use to solve fragmentation issues. Google has already made an API (application programming interface) called Fragments API to developers within the Honeycomb SDK. This API lets developers more easily scale their applications to match the varying screen sizes, shapes, and resolutions of different Android devices. The new tool released by Google this week enhances the API and makes it possible to target devices/systems other than those running Android 3.0 Honeycomb. This means developers should be able to scale their apps to work on all Android devices between 1.6 Donut and 3.0 Honeycomb.
Google Releases reCAPTCHA API to Improve Android Security
Google today announced a new tool developers can use to authenticate people securely while simultaneously improving the experience for mobile phone users. The company made available the new reCAPTCHA Android API as a part of Google Play Services.
Google Hopes New API Will Improve Android Wear Complications
Google today announced a new version of its Complications API for developers in order to help them create better experiences for Android Wear. Complications are dynamic data sets that appear on watch faces, such as step counts, notifications, weather alerts, and similar.
Google Makes More Android APIs Available to Developers
Google recently released a new tool for developers who are writing apps for the Android platform. Google made the Google Play Developer Publishing API available to all developers, which will allow them to upload APKs to beta testing, staged rollouts, and production, as well as add publishing operations to their app processes.
Google Play Services 7.3 Expands Android Wear Powers
Google today announced Play Services 7.3, an update to the core functions of the Android platform. Play Services 7.3 will bring new features to Android devices thanks to an expanded range of tools being made available to developers.
Not good enough, Google
Apps would be permitted to support non-standard resolutions as well, if the developer chooses to do the extra work.
All handsets granted access to the market would be required to support at least one of the "standard" resolution sizes so that everything works on every device.
As standard resolutions, I would suggest: 240x320, 480x800 and 600x1024.
Slightly oversize devices like the Motorolas running at 480x854 or 800x1280 would be required to have a "border" mode similar to running an iPhone only app on an iPad, where is simp...
good job google