Android apps on your Windows machine

   Following a three-month alpha phase and a well-received CES 2012 demo, BlueStacks has launched the beta version of its innovative Android emulator for Windows XP, Vista and 7. Using a patent-pending binary-translation technology, BlueStacks allows x86-based PC users to access the growing wealth of apps designed for devices powered by ARM's processing architecture and Google's mobile OS.
On the flip side, BlueStacks provides developers with a massive secondary install base without having to port their software. "A billion PCs is a huge potential market for any developer," said HandyGames CEO Markus Kassulke. "There is the potential to make good money from the additional app discovery and usage. The best part is, we don't have to do any work. Our apps run without any modifications."
During alpha, BlueStacks was downloaded more than a million times in over 100 countries. Users ran over 4.5 million apps with multi-protocol IM applications Kakao Talk and WhatsApp being the most popular in Korea and the US, while the multi-player game Wordfeud was the most used app in Germany. Games appear to be the beta's largest attraction, as they weren't widely available in the previous build.

Credits:http://www.techspot.com/news/48002-bluestacks-hits-beta-runs-android-apps-on-your-windows-machine.html

Google Nexus Tablet

A Google Nexus tablet is all set to go, an Android enthusiast site claims. And it's even cheaper than the Kindle Fire, so the story goes.

The latest scuttlebutt about the rumored Google tablet makes the case with a lot more certitude. In fact, an Android enthusiast site goes so far as to say it's a "done deal," citing sources. The Asus MeMo 370T which appears to be the template for the Google tablet--has been "scrapped after Google contracted with Asus to produce their 'Nexus tablet,'" the report begins.
"Earlier reports said the device would retail for $199-$249, but we are now told the target price is $149-$199." That of course lands it right in Amazon's wheelhouse: the Kindle Fire has been a hit due, in no small part, to its $199 price.

Credits:http://news.cnet.com/8301-13924_3-57399239-64/google-nexus-tablet-a-done-deal-claims-report/

Android 5.0 – Jelly Bean

Jelly Bean Features

• Toggle Options
• Efficient File Management
• Themes
• A Better Browser
• Screen Lock
• Upgrade Procedure 
• Improved Operating System
• Keyboard Issues: A standard keyboard is a must for the new Android 5.0 as in the absence of any specific Google-designed keyboard.

How to create app widget in android?

What is app widget?

App Widgets are miniature application views that can be embedded in other applications (such as the Home screen) and receive periodic updates. These views are referred to as Widgets in the user interface, and you can publish one with an App Widget provider. An application component that is able to hold other App Widgets is called an App Widget host. The screenshot below shows the Music App Widget.


To create an App Widget, you need the following:

AppWidgetProviderInfo object

Describes the metadata for an App Widget, such as the App Widget's layout, update frequency, and the AppWidgetProvider class. This should be defined in XML.

AppWidgetProvider class implementation

Defines the basic methods that allow you to programmatically interface with the App Widget, based on broadcast events. Through it, you will receive broadcasts when the App Widget is updated, enabled, disabled and deleted.

View layout

Defines the initial layout for the App Widget, defined in XML.

Additionally, you can implement an App Widget configuration Activity. This is an optional Activity that launches when the user adds your App Widget and allows him or her to modify App Widget settings at create-time.
The following sections describe how to setup each of these components.

Declaring an App Widget in the Manifest

First, declare the AppWidgetProvider class in your application's AndroidManifest.xml file. For example:

<receiver android:name="ExampleAppWidgetProvider" >
    <intent-filter>
        <action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
    </intent-filter>
    <meta-data android:name="android.appwidget.provider"
               android:resource="@xml/example_appwidget_info" />
</receiver>

The <receiver> element requires the android:name attribute, which specifies the AppWidgetProvider used by the App Widget.
The <intent-filter> element must include an <action> element with the android:name attribute. This attribute specifies that the AppWidgetProvider accepts the ACTION_APPWIDGET_UPDATE broadcast. This is the only broadcast that you must explicitly declare. The AppWidgetManager automatically sends all other App Widget broadcasts to the AppWidgetProvider as necessary.
The <meta-data> element specifies the AppWidgetProviderInfo resource and requires the following attributes:

• android:name - Specifies the metadata name. Use android.appwidget.provider to identify the data as the AppWidgetProviderInfo descriptor.
• android:resource - Specifies the AppWidgetProviderInfo resource location.

 credits:developer.android.com