Android Developers Maximum: June 2012

Android SDK Tools, Revision 20

[This post is by Xavier Ducrohet, Tech Lead for the Android developer tools]

Along with the preview of the Android 4.1 (Jelly Bean) platform, we launched Android SDK Tools R20 and ADT 20.0.0. Here are a few things that we would like to highlight.

Application templates

Tracer for GLES

Device Monitor

Systrace

Settings > Developer Options > Monitoring: Enable traces

To learn more on the layout editor, XML editing, build system & SDK Manager improvements, please read the ADT 20.0.0 and SDK Tools R20 release notes.

Join us today, June 28th, at the “What’s new in Android developer tools” session for some fun tool demos and a sneak-peak into what’s coming next.

Android @ I/O: the playground is open

Last year at Google I/O, we talked about momentum, mobile and more. This year, we’re picking up right where we left off. More than 400 million Android devices have now been activated—up from 100 million last June. And twelve new Android devices are activated every every second—that’s more than 1 million a day. Today, we’re rolling out a new version of Android called Jelly Bean, adding more entertainment to Google Play, and introducing two powerful—yet distinctly different Nexus devices to bring you the best of Google.

Jelly Bean: simple, beautiful and beyond smart
Jelly Bean builds on top of Ice Cream Sandwich. It makes everything smoother, faster and more fluid. For example, notifications are now more dynamic: if you’re late for a meeting or missed a call, you can email or call directly from notifications. The keyboard is smarter and more accurate, and can predict your next word. And voice typing is faster, working even when you don’t have a data connection.

We’ve redesigned search from the ground up in Jelly Bean, with a new user interface and faster, more natural Voice Search. You can type your query or simply ask Google a question. Google can speak back to you, delivering a precise answer, powered by the Knowledge Graph, if it knows one, in addition to a list of search results.

Today’s smart devices still rely on you to do pretty much everything—that is, until now. Google Now is a new feature that gets you just the right information at just the right time. It tells you today’s weather before you start your day, how much traffic to expect before you leave for work, or your favorite team's score as they’re playing. There’s no digging required: cards appear at the moment you need them most.

Starting in mid-July, we’ll start rolling out over-the-air updates to Galaxy Nexus, Motorola Xoom and Nexus S, and we’ll also release Jelly Bean to open source.

Google Play: more entertainment
Google Play is your digital entertainment destination, with more than 600,000 apps and games plus music, movies and books. It’s entirely cloud-based, which means all of your content is always available across all of your devices. Today our store is expanding to include magazines. We’ve been working with leading publishers Condé Nast, Hearst, Meredith and more to offer magazines like House Beautiful, Men’s Health, Shape and WIRED.

Now, you can also purchase movies in addition to renting them. And we’re adding television shows on Google Play—in fact, we’re adding thousands of episodes of broadcast and cable TV shows, like "Revenge," "Parks & Recreation" and "Breaking Bad," from some of the top studios, like ABC Studios, NBCUniversal and Sony Pictures. You can play back movies and TV shows on all your Android devices, through Google Play on the web, and on YouTube, and soon we’ll bring the experience to Google TV devices.

Movie purchases, TV shows and magazines are available today on play.google.com, and will roll out to Google Play on devices over the coming days.

Nexus 7: powerful, portable and designed for Google Play
All of this great Google Play content comes to life on Nexus 7, a powerful new tablet with a vibrant, 7” 1280x800 HD display. The Tegra-3 chipset, with a quad-core CPU and 12-core GPU, makes everything, including games, extremely fast. And best of all, it’s only 340 grams, lighter than most tablets out there. Nexus 7 was built to bring you the best of Google in the palm of your hand. Hang out with up to 10 friends on Google+ using the front-facing camera, browse the web blazingly fast with Chrome and, of course, crank through your emails with Gmail.

Nexus 7 comes preloaded with some great entertainment, including the movie "Transformers: Dark of the Moon," the book “The Bourne Dominion,” magazines like Condé Nast Traveler and Popular Science, and songs from bands like Coldplay and the Rolling Stones. We’ve also included a $25 credit to purchase your favorite movies, books and more from Google Play, for a limited time. Nexus 7 is available for preorder today from Google Play in the U.S., U.K., Canada and Australia, and starts at $199 in the U.S. It will start shipping mid-July.

Nexus Q: It’s a sphere!
It's great to be able to take your entertainment with you wherever you go, but sometimes you want to ditch the headphones and enjoy music with friends and family. So we’re introducing Nexus Q, which combines the power of Android and Google Play to easily stream music and video in your home—all controlled by an Android phone or tablet. Designed and engineered by Google, Nexus Q is a small sphere that plugs into the best speakers and TV in your house. It’s the first-ever social streaming device—like a cloud-connected jukebox where everyone brings their own music to the party. Available first in the U.S., you can preorder Nexus Q today from Google Play for $299, and it will ship mid-July.

If you own one of the 400 million Android devices out there, you already know that it’s much more than simply a phone or tablet. It’s your connection to the best of Google—all of your stuff and entertainment, everywhere you go. Now you have a new version of Android, more entertainment and a growing portfolio of Nexus devices to choose from—all available in Google Play. The playground is open.

Posted by Andy Rubin, Senior Vice President of Mobile and Digital Content

Introducing Android 4.1 (Jelly Bean) preview platform, and more

[This post is by Angana Ghosh, Product Manager on the Android team]

At Google I/O today we announced the latest version of the Android platform, Android 4.1 (Jelly Bean). With Jelly Bean, we’ve made the great things about Android even better with improved system performance and enhanced user features.

Improvements include a smoother and more responsive UI across the system, a home screen that automatically adapts to fit your content, a powerful predictive keyboard, richer and more interactive notifications, larger payload sizes for Android Beam sharing and much more. For a lowdown on what’s new, head over to the Jelly Bean platform highlights.

Of course, Jelly Bean wouldn’t be complete without a healthy serving of new APIs for app developers. Here are some of the new APIs that Jelly Bean introduces:

Expandable notifications

Android Beam

Bi-directional text support

Gesture mode

Media codec access

Wi-Fi Direct service discoverability

Network bandwidth management

For a complete overview of new APIs in Jelly Bean, please read the API highlights document. Note that this is a preview of the Jelly Bean platform. While we’re still finalizing the API implementations we wanted to give developers a look at the new API to begin planning app updates. We’ll be releasing a final platform in a few weeks that you should use to build and publish applications for Android 4.1.

For Android devices with the Google Play, we launched the following at Google I/O today:

Smart app updates

App encryption

Google Cloud Messaging for Android

Learn more

Starting from today, over 20 Android sessions at Google I/O will deep-dive in many of these areas. Join us in-person or follow us live.

A new friend just moved into the neighborhood...

The statues on the front lawn of the Android building got a new friend this afternoon...

Also, you may have noticed we did a little redecorating. We’ve been asking you what content you wanted to see more of on the Google Mobile blog, and the answer was quite clear: more Android! This blog, in addition to the +Android page on Google+, will be your place to find all the latest news from the Android team.

See you tomorrow at I/O!

Posted by: Hugo Barra, Director of Product Management, Android

Replying to User Reviews on Google Play

[This post is by Trevor Johns from the Android team — Tim Bray]

User reviews on Google Play are great for helping people discover quality apps and give feedback to developers and other potential app users. But what about when developers want to give feedback to their users? Sometimes a user just needs a helping hand, or perhaps a new feature has been added and the developer wants to share the good news.

That’s why we’re adding the ability for Google Play developers to respond to reviews from the Google Play Android Developer Console. Developers can gather additional information, provide guidance, and — perhaps most importantly — let users know when their feature requests have been implemented.

We’ll also notify the user who wrote the review via email that the developer has responded. Users can then contact the developer directly if additional followup is needed or update their review.

We’re releasing this feature today to those with a Top Developer badge (). And based on feedback from users and developers, we will offer it to additional Google Play developers in the future.

Conversations are meant to be two-sided, and facilitating discussion between developers and users will ultimately yield better apps, to the benefit of everyone.

Helping you build beautiful, powerful, successful apps

[This post is by Billy Rutledge, Director of Developer Relations for Android. — Tim Bray]

Just in time for Google I/O next week, the Android Developers site is stepping into a new look that is streamlined, simplified, and refocused. A developer’s tasks fall into three baskets: Designing, developing, and distributing. We're trying to make developer.android.com's organization reflect this reality, shepherding you through the app development life cycle, from start to finish.

Design

Earlier this year, we launched Android Design, an online style guide which lays out the principles, building blocks, and patterns for excellence in Android user interfaces. It seems to be working; every day, we see more and more beautiful apps arriving in Google Play. At I/O, we’ll continue to talk design, kicking off with Android Design for Success, led by Matias Duarte.

Develop

An Android app should be fast, powerful and useful. With Android Training, one of the many parts of the Develop section that we continue to build out, we lay out best practices in a variety of framework topics to help you achieve those goals. If you’re at I/O and you’re interested in Android tools, be sure to start off your show with What’s new in Android Developers’ Tools.

Distribute

The most important piece of the piece of the puzzle is about getting your app in front of millions and millions of Android users on Google Play. That’s why we added a section on distributing your app — a peek into the world of publishing and promoting your app. Chris Yerga on the Play team will be kicking off our how-to sessions on distributing your with Android apps in Google Play.

This is just a small sample of the Android sessions at Google I/O, many of which will be live-streamed so you can follow along even if you can’t make it out to San Francisco. In the meantime, we hope you find the new Android Developer site much more useful as you build great apps.

Join the discussion on

+Android Developers

Using DialogFragments

[This post is by David Chandler, Android Developer Advocate — Tim Bray]

Honeycomb introduced Fragments to support reusing portions of UI and logic across multiple activities in an app. In parallel, the showDialog / dismissDialog methods in Activity are being deprecated in favor of DialogFragments.

In this post, I’ll show how to use DialogFragments with the v4 support library (for backward compatibility on pre-Honeycomb devices) to show a simple edit dialog and return a result to the calling Activity using an interface. For design guidelines around Dialogs, see the Android Design site.

The Layout

Here’s the layout for the dialog in a file named fragment_edit_name.xml.

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/edit_name"
    android:layout_width="wrap_content" android:layout_height="wrap_content"
    android:layout_gravity="center" android:orientation="vertical"  >

    <TextView
        android:id="@+id/lbl_your_name" android:text="Your name" 
        android:layout_width="wrap_content" android:layout_height="wrap_content" />
      
    <EditText
        android:id="@+id/txt_your_name"
        android:layout_width="match_parent"  android:layout_height="wrap_content" 
        android:inputType=”text”
        android:imeOptions="actionDone" />
</LinearLayout>

Note the use of two optional attributes. In conjunction with android:inputType=”text”, android:imeOptions=”actionDone” configures the soft keyboard to show a Done key in place of the Enter key.

The Dialog Code

The dialog extends DialogFragment, and since we want backward compatibility, we’ll import it from the v4 support library. (To add the support library to an Eclipse project, right-click on the project and choose Android Tools | Add Support Library...).

import android.support.v4.app.DialogFragment;
// ...

public class EditNameDialog extends DialogFragment {

    private EditText mEditText;

    public EditNameDialog() {
        // Empty constructor required for DialogFragment
    }

    @Override
    public View onCreateView(LayoutInflater inflater, ViewGroup container,
            Bundle savedInstanceState) {
        View view = inflater.inflate(R.layout.fragment_edit_name, container);
        mEditText = (EditText) view.findViewById(R.id.txt_your_name);
        getDialog().setTitle("Hello");

        return view;
    }
}

The dialog extends DialogFragment and includes the required empty constructor. Fragments implement the onCreateView() method to actually load the view using the provided LayoutInflater.

Showing the Dialog

Now we need some code in our Activity to show the dialog. Here is a simple example that immediately shows the EditNameDialog to enter the user’s name. On completion, it shows a Toast with the entered text.

import android.support.v4.app.FragmentActivity;
import android.support.v4.app.FragmentManager;
// ...

public class FragmentDialogDemo extends FragmentActivity implements EditNameDialogListener {

    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);
        showEditDialog();
    }

    private void showEditDialog() {
        FragmentManager fm = getSupportFragmentManager();
        EditNameDialog editNameDialog = new EditNameDialog();
        editNameDialog.show(fm, "fragment_edit_name");
    }

    @Override
    public void onFinishEditDialog(String inputText) {
        Toast.makeText(this, "Hi, " + inputText, Toast.LENGTH_SHORT).show();
    }
}

There are a few things to notice here. First, because we’re using the support library for backward compatibility with the Fragment API, our Activity extends FragmentActivity from the support library. Because we’re using the support library, we call getSupportFragmentManager() instead of getFragmentManager().

After loading the initial view, the activity immediately shows the EditNameDialog by calling its show() method. This allows the DialogFragment to ensure that what is happening with the Dialog and Fragment states remains consistent. By default, the back button will dismiss the dialog without any additional code.

Using the Dialog

Next, let’s enhance EditNameDialog so it can return a result string to the Activity.

import android.support.v4.app.DialogFragment;
// ...
public class EditNameDialog extends DialogFragment implements OnEditorActionListener {

    public interface EditNameDialogListener {
        void onFinishEditDialog(String inputText);
    }

    private EditText mEditText;

    public EditNameDialog() {
        // Empty constructor required for DialogFragment
    }

    @Override
    public View onCreateView(LayoutInflater inflater, ViewGroup container,
            Bundle savedInstanceState) {
        View view = inflater.inflate(R.layout.fragment_edit_name, container);
        mEditText = (EditText) view.findViewById(R.id.txt_your_name);
        getDialog().setTitle("Hello");

        // Show soft keyboard automatically
        mEditText.requestFocus();
        getDialog().getWindow().setSoftInputMode(
                LayoutParams.SOFT_INPUT_STATE_VISIBLE);
        mEditText.setOnEditorActionListener(this);

        return view;
    }

    @Override
    public boolean onEditorAction(TextView v, int actionId, KeyEvent event) {
        if (EditorInfo.IME_ACTION_DONE == actionId) {
            // Return input text to activity
            EditNameDialogListener activity = (EditNameDialogListener) getActivity();
            activity.onFinishEditDialog(mEditText.getText().toString());
            this.dismiss();
            return true;
        }
        return false;
    }
}

For user convenience, we programmatically focus on the EditText with mEditText.requestFocus(). Alternatively, we could have used the <requestFocus/> tag in the layout XML to do this; however, in some cases it’s preferable to request focus programmatically. For example, an OnFocusChangeListener added in the Fragment’s onCreateView() method won’t get called if you request focus in the layout XML.

If the user focuses on an EditText, the soft keyboard will automatically appear. In order to force this to happen with our programmatic focus, we call getDialog().getWindow().setSoftInputMode(). Note that many Window operations you might have done previously in a Dialog can still be done in a DialogFragment, but you have to call getDialog().getWindow() instead of just getWindow(). The resulting dialog is shown on both a handset and tablet (not to scale):

The onEditorAction() method handles the callback when the user presses the Done key. It gets invoked because we’ve set an OnEditorActionListener on the EditText. It calls back to the Activity to send the entered text. To do this, EditNameDialog declares an interface EditNameDialogListener that is implemented by the Activity. This enables the dialog to be reused by many Activities. To invoke the callback method onFinishEditDialog(), it obtains a reference to the Activity which launched the dialog by calling getActivity(), which all Fragments provide, and then casts it to the interface type. In MVC architecture, this is a common pattern for allowing a view to communicate with a controller.

We can dismiss the dialog one of two ways. Here we are calling dismiss() within the Dialog class itself. It could also be called from the Activity like the show() method.

Hopefully this sheds some more light on Fragments as they relate to Dialogs. You can find the sample code in this blog post on Google Code.

References for learning more about Fragments: