Dropbox SDK for Android

Last night I had a great idea for an app, which should be pretty easy to implement, I thought. I needed to use the Dropbox API for that and so I went to their website and found out that they have an own Android SDK. I could not find any instructions on how to use it and so I tried to find out by myself and downloaded that package. Next thing I tried was importing it to Eclipse, and that’s where the trouble took its course…

What went wrong?

First thing I noticed: The package didn’t contain any Eclipse project file. So I created a new Android Project in Eclipse and imported their source code – Build Error. I found out that I had to add the .jar files included in the package to my project’s Java build path. Bingo! It compiled and started the Demo application.

Cool! I could sign in and out. Now I just had to reference it as an Android Library and use it in my own project, right? The answer is no. Despite the .jar for the Dropbox Java API implementation, the “SDK” includes only two files: DropboxSample.java (the Activity) and LoginAsyncTask.java
. The second one handles all the login stuff and would be very handy when writing an app which should be connected to Dropbox, but it is so tightly coupled to the sample Activity, that it’s impossible to reuse it anywhere else. That made me pretty angry and so I decided to refactor the SDK.

Refactoring an SDK

I have used a couple of SDKs before and what I wanted to have was this:

  • An isolated Android Library Project containing only SDK classes
  • A project containing the sample application, which references the SDK project
  • A decoupled LoginAsyncTask.java
  • A small set of helper classes providing the easiest way to use the SDK

Long story short – The result is a Github project containing two projects: One SDK project, which is an Android Library, and a Sample Application. As I said before, I decoupled the LoginAsyncTask.java and made the SDK easier to use. I added a Dropbox.java class, which encapsulates the login procedure, and a LoginListener class as a simple callback. Here are some code snippets on how to use it in your Activity:

Creating the Dropbox object and checking existing logins:

final static private String CONSUMER_KEY = "PUT_YOUR_CONSUMER_KEY_HERE";
final static private String CONSUMER_SECRET = "PUT_YOUR_CONSUMER_SECRET_HERE";

// ... //

mDropbox = new Dropbox(getBaseContext(), CONSUMER_KEY, CONSUMER_SECRET);
if (mDropbox.authenticate()) {
        	// We can query the account info already, since we have stored 
        	// credentials
        	getAccountInfo();
} 

Handling the login callback:

    // Notifies our Activity when a login process succeeded or failed.     
    DropboxLoginListener mLoginListener = new DropboxLoginListener() {

		@Override
		public void loginFailed(String message) {			
			showToast("Login failed: "+message);
			setLoggedIn(false);
		}

		@Override
		public void loginSuccessfull() {
			showToast("Logged in!");
			setLoggedIn(true);		
			displayAccountInfo(mDropbox.accountInfo());
		}    	
    };

Logging in:

 private void getAccountInfo() {
    	
    	if (mDropbox.isAuthenticated()) {
		// Access credentials are already stored, just login
		mDropbox.login(mLoginListener);	            		
    	} else {
    		// Code for getting email and password goes here //

	        mDropbox.login(mLoginListener, email, password);	        
    	}
    }

For more details, just have a look at the Sample Application! If you have any feedback, feel free to comment.

Thanks so far

Android UI pattern implementations

Most Android users may have recognized more and more common UI elements in Android applications these days. Widgets like ActionBar and QuickActions are a great approach to standardize the way Android applications are used. Google posted some design proposals and took the Twitter for Android app as a great example for Android design patterns. A more precise definition for these and more patterns can be found at androidpatterns.com.
Of course, I immediately needed to have some of these in my own applications. So I started looking for Google’s implementation examples or developer documentation – nothing! Not even a code snippet. Fortunately, I was not the only one with that problem. I found some pretty good implementations for ActionBar and QuickActions, but I was looking for a more “integrated” solution, so I continued my research. Hours of googling later, I found a video from a talk at Google I/O 2010, which pointed me at the Google I/O app, which seems to be a good reference. But I wanted a library, not an example implementation and so I kept on searching. Finally, I found this awesome project, which perfectly fits my needs: Greendroid!

Greendroid

… is the most complete library for android UI patterns I found by now. Just load the Greendroid project into Eclipse, add it as a library to your project and you’re ready to go! To give you an example, creating an ActionBar and filling it with items is as easy as this:

1. Put this into your XML layout:

<greendroid.widget.ActionBar
 	android:id="@+id/MyActionBar" 
	android:layout_height="@dimen/gd_action_bar_height"
	android:layout_width="fill_parent" />

2. Fill your ActionBar with items and a title:

@Override
	public void fillActionBar(final ActionBar mActionBar) {
		mActionBar.addItem(Type.Compose);
		mActionBar.addItem(Type.Refresh);
		mActionBar.addItem(Type.Locate);
		mActionBar.setTitle("My ActionBar");
		mActionBar.setOnActionBarListener(new OnActionBarListener() {

			@Override
			public void onActionBarItemClicked(int position) {
				switch(position) {
				case 0:
					// Compose action
					break;
				case 1:
					// Refresh action
					LoaderActionBarItem item = (LoaderActionBarItem) mActionBar.getItem(position);
					// Turn the item into a progress indicator
					item.setLoading(true);
					break;
				case 2:
					// Map action
					break;
 				default:
 					// Action for home button
					break;
 				}
 			}
	 });

I recommend you to take a look at their example application (also included in the repository) to see what else you can do with Greendroid. There isn’t really a documentation, but the example application is pretty much everything you need to understand how Greendroid should be used.

I hope we’ll see more applications use the UI patterns in the future to give the Android application landscape a more consistent look.
Have fun!