Byte Into It blog

Tuesday, December 7, 2010

Google launches eBookstore with choice of sellers and devices

Published on Ars Technica - Front page content | shared via feedly

We expected Google to launch its upcoming e-book store before the end of the year, and the company announced Monday that the new Google eBookstore is now open for business in the US. Google is touting the "open" nature of its e-books by making them accessible to the widest array of popular e-reader devices, including the iPad, Nook, and Sony Reader.

Google's new eBookstore works a little differently than other stores—at least when it comes to reading via computer. All purchased titles are kept in Google's cloud-based storage and accessed via a browser. When reading via an iOS or Android-based device, a dedicated app can download and cache titles for reading offline. And for devices compatible with Adobe's DRM-protected e-book formats—including Sony Reader and Barnes & Noble Nook—PDF or EPUB files can be downloaded and transferred to your device using Adobe Editions software.

Read the comments on this post

Gingerbread Released, Here's What's New

Published on ReadWriteWeb | shared via feedly

Today Google launched its newest flagship phone, the Nexus S, and with it, the next version of the Android operating system, code-named Gingerbread (Android 2.3). The new platform introduces a number of new features for end users and developers alike, most notably several user interface changes including a new keyboard and text selection tool, support for NFC technology, better power management, Internet (VoIP/SIP calling, better copy and paste, gyroscope support and more.

Sponsor

For Users

The new features for users in Gingerbread are detailed here on the Android Developers website. To summarize, those are as follows:

UI Refinements: the new UI has been redesigned to be easier, faster and more power-efficient. The theme's background has been changed to black in areas like the notification bar, menus and other parts of the UI. Changes in menus and settings have also been introduced for simplified use and navigation.
New Keyboard: The keyboard has been updated for faster input and editing. The keys have been reshaped so presses are more accurate, and an idea stolen from add-in applications like SwiftKey, the new keyboard now displays word suggestions based on what you're typing. You can switch to voice mode from the keyboard to replace selections, too. Multi-touch key-chording lets you enter numbers and symbols with keyboard shortcut combos, instead of having to change to the numeric keyboard mode.
Word Selection Improved: Now you can select a word via press-hold, a similar gesture to what's used on iPhone for the same task. On Gingerbread, this takes you to a free-selection mode where you can adjust the area needed to select by dragging two bounding areas together.
Copy/Paste Improved: The press-hold gesture mentioned above also starts the copy/paste process. After selecting content, press anywhere in the selection mode to copy the text.
Improved Power Management: Android now is more active in managing apps that keep the device awake, even going so far as to close apps when appropriate. In the Application Settings, users can now see how the battery is being used by various apps.
Application Control: A shortcut to Manage Applications is now in the Options menu from the Home Screen. A new Running tab displays a list of active apps and the storage/memory being used. From here, apps can be stopped, ending the need for add-on "task killer" type applications to do this.
Internet Calling: Internet Calling (SIP) addresses can be added to Contacts and calls can be placed from the Quick Contact or Dialer. A SIP account is needed for this feature to work. This feature will be available depending on manufacturer and carrier support.
NFC: Near-field communications support is now included in the OS. With NFC, you can "touch" or "swipe" an NFC tag embedded in a poster, sticker, ad, or anywhere else and then be directed to a website associated with the URL included in the tag's data. NFC support will be determined by the phone's hardware.
Downloads Management: Downloads can now be access and manager from the browser, email or within an app. A new Download Manager is introduced for this.
Camera: The camera app now provides access to multiple cameras on the device, if the phone includes more than one (such as a front-facing camera, for example).

What's New For Developers: See Next Page

Gingerbread For Developers

Developers need to be aware of the following features:

Concurrent garbage collector: The Dalivik VM introduces a new, concurrent garbage collector that minimizes application pauses, helping to ensure smoother animation and increased responsiveness in games and similar applications.
Faster event distribution: The plaform now handles touch and keyboard events faster and more efficiently, minimizing CPU utilization during event distribution. The changes improve responsiveness for all applications, but especially benefit games that use touch events in combination with 3D graphics or other CPU-intensive operations.
Updated video drivers: The platform uses updated third-party video drivers that improve the efficiency of OpenGL ES operations, for faster overall 3D graphics performance.
Event Handling: Applications that use native code can now receive and process input and sensor events directly in their native code, which dramatically improves efficiency and responsiveness. Native libraries exposed by the platform let applications handle the same types of input events as those available through the framework. Applications can receive events from all supported sensor types and can enable/disable specific sensors and manage event delivery rate and queueing.
New Sensor Types: Android 2.3 adds API support for several new sensor types, including gyroscope, rotation vector, linear acceleration, gravity, and barometer sensors. Applications can use the new sensors in combination with any other sensors available on the device, to track three-dimensional device motion and orientation change with high precision and accuracy. For example, a game application could use readings from a gyroscope and accelerometer on the device to recognize complex user gestures and motions, such as tilt, spin, thrust, and slice.
Open API for Native Audio: The platform provides a software implementation of Khronos OpenSL ES, a standard API that gives applications access to audio controls and effects from native code. Applications can use the API to manage audio devices and control audio input, output, and processing directly from native code
Native graphics management: The platform provides an interface to its Khronos EGL library, which lets applications manage graphics contexts and create and manage OpenGL ES textures and surfaces from native code.
Native access to Activity lifecycle, window management: Native applications can declare a new type of Activity class, NativeActivity whose lifecycle callbacks are implemented directly in native code. The NativeActivity and its underlying native code run in the system just as do other Activities -- they run in the application's system process and execute on the application's main UI thread, and they receive the same lifecycle callbacks as do other Activities. The platform also exposes native APIs for managing windows, including the ability to lock/unlock the pixel buffer to draw directly into it..
Native access to assets, storage: Applications can now access a native Asset Manager API to retrieve application assets directly from native code without needing to go through JNI. If the assets are compressed, the platform does streaming decompression as the application reads the asset data. There is no longer a limit on the size of compressed .apk assets that can be read. Additionally, applications can access a native Storage Manager API to work directly with OBB files downloaded and managed by the system. (Dev tools for creating and managing OBB files will not be available until early 2011.)
Robust native development environment: The Android NDK (r5 or higher) provides a complete set of tools, toolchains, and libraries for developing applications that use the rich native environment offered by the Android 2.3 platform.
Internet telephony: Developers can now add SIP-based internet telephony features to their apps. Android 2.3 includes a full SIP protocol stack and integrated call management services that let applications easily set up outgoing and incoming voice calls, without having to manage sessions, transport-level communication, or audio record or playback directly.
Near Field Communications (NFC): The platform's support for Near Field Communications (NFC) lets developers get started creating a whole new class of applications for Android. Developers can create new applications that offer proximity-based information and services to users, organizations, merchants, and advertisers. Using the NFC API, applications can respond to NFC tags "discovered" as the user "touches" an NFC-enabled device to elements embedded in stickers, smart posters, and even other devices. When a tag of interest is collected, applications can respond to the tag, read messages from it, and then store the messages, prompting the user as needed.
Mixable audio effects: A new audio effects API lets developers easily create rich audio environments by adding equalization, bass boost, headphone virtualization (widened soundstage), and reverb to audio tracks and sounds. Developers can mix multiple audio effects in a local track or apply effects globally, across multiple tracks.
Support for new media formats: The platform now offers built-in support for the VP8 open video compression format and the WebM open container format. The platform also adds support for AAC encoding and AMR wideband encoding (in software), so that applications can capture higher quality audio than narrowband.
Access to multiple cameras: The Camera API now lets developers access any cameras that are available on a device, including a front-facing camera. Applications can query the platform for the number of cameras on the device and their types and characteristics, then open the camera needed. For example, a video chat application might want to access a front-facing camera that offers lower-resolution, while a photo application might prefer a back-facing camera that offers higher-resolution.

Discuss

On the Heels of Recent Domain Seizures, ICANN Insists "We Don't Take Down Websites"

Published on ReadWriteWeb | shared via feedly

Following the recent government seizure of over 80 websites, there was a certain amount of finger-pointing aimed at ICANN, the Internet Corporation for Assigned Names and Numbers - the nonprofit organization tasked with managing IP address spaces and managing top-level domains.

ICANN has just issued a statement, saying that it was not responsible for any part of the government actions. "As we have said many times, ICANN was not a party to those actions" by the U.S. Immigation and Customs Enforcement agency (ICE), "nor was it a target of them."

Sponsor

According to Domain Incite, the requests to take down websites went through VeriSign, the company that operates the .com domain.

"ICANN does not take down domain names," the ICANN statement says, "we have no technical or legal authority to do that. We have no involvement in the takedown of any website, which is an issue of national authority. ICANN knew nothing about this enforcement action until after the fact. And with good reason, since we are not a law enforcement entity or an agent of the U.S. or any other government. ICANN is the non-profit coordinator of the Internet's global domain name system and is not involved in website content in any way."

While not an official agency, ICANN was created in part by a mandate from the U.S. government. As a result - and due to questions about transparency and accountability - some have viewed the organization's "neutrality" with skepticism.

ICANN's announcement comes the same day as an Obama Administration has promised more crackdowns on websites that violate copyright laws.

Discuss

Google’s Chrome OS: What to Expect at Launch

Published on GigaOM | shared via feedly

Tomorrow, Google is holding a Chrome event, where it's likely we'll see the official launch of the first Google Chrome OS device, and a supporting web app store. Chrome OS was first introduced as a browser-based platform for netbooks in November of 2009, with a target launch by the end of 2010. The mobile market has changed much since then, but Google seems unwavering in its plans to tackle the computer market with an operating system of its own.

Google isn't blind to the current situation though: it knows that tablets, handsets and smartphones are hotter now than netbooks were when Chrome OS was announced. More than 340 million mobile phones were sold globally in just the third quarter of this year, for example. Compare that to Gartner's recent estimate of 352.4 million computers sold around the globe in all of 2010, and it's not surprising that potential demand for a small Chrome OS computer, or any netbook, for that matter, is lower now than it was a year ago. As a result, I suspect we'll hear that Google has been using Chrome OS devices in-house and that Chrome OS consumer devices may launch early next year from a number of hardware partners. Here's a recap of what to expect from these devices:

A netbook without Windows — You won't find Microsoft Windows on a Chrome OS computer. Instead, it's a Linux kernel under the hood with a customized version of Google's Chrome browser as the entire interface.
Google Apps at the core — Google's web-based applications are prominent throughout, even at the time of sign-in, which requires a Google account. Docs, Calendar, Gmail, Search, Google Talk and more are all integrated into the platform.
Web App Store — Likely to launch with Chrome OS devices is an online store for web apps, so you can add third-party software based on web standards such as HTML5 and JavaScript.
A mobile processor — Just like the majority of netbooks available on the market today, Chrome OS computers can run on Intel's Atom chipset, although they can also run on low-p0wered chips built from the ARM architecture, currently used in many smartphones and tablets.
No hard drive — In lieu of a spinning hard drive, Google is looking to use solid state disks, or flash memory for all local storage, much like Apple's new Mac Book Air. That configuration, combined with a light operating system should allow for Chrome OS to boot in roughly five seconds or less.
Connectivity will be key — While I expect some offline functionality in Chrome OS, the device's primary use case is being connected, most likely to a Wi-Fi network, although support for mobile broadband is a safe bet for future iterations.

Since Google set the stage for Chrome OS more than a year ago, it may actually be more interesting tomorrow to hear about the target audience for the devices. With more alternatives to netbooks today than at this time last year — including a solid smartphone and tablet platform in Android, which just improved with the release of its Gingerbread version today — Chrome OS could be aimed less at consumers (at least initially) and more towards the mobile enterprise.

Related content from GigaOM Pro (sub. req.):

Live with the WikiLeakable world or shut down the net. It's your choice | John Naughton | Comment is free | The Guardian

http://www.guardian.co.uk/commentisfree/cifamerica/2010/dec/06/western-democracies-must-live-with-leaks