«

DroidDrop – Remote Logging for Android

By carmendelessio

Video Demo – remote logging

DroidDrop Remote logging gives Android Developers the ability to log data from their applications to a drop on drop.io.

How to:
Download DroidDropNotes.jar

Include the jar in your Android project.  It will add 16K to your APK.

Get a developer API Key from drop.io (free, painless, takes 2 minutes)
http://dev.drop.io/

Review the source code and example on GitHub.

DropioLogDemo.java shows the first screen for the app
UpdateLog.java has sample usage to show logging an exception and saving user input.

Declare a DroidDropNote Client:
DroidDropNoteClient dropClient= new DroidDropNoteClient(“–YOUR API Key”);
dropClient.setToken(“–drop password or token”);

Write out a Note/Text contents:
results = dropClient.createNote( “DROPNAME”, “Note title”,  “Message”);

Tags: , , , , , ,

This entry was posted on November 4, 2009 at 9:51 pm and is filed under Android, Java, drop.io. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Responses to “DroidDrop – Remote Logging for Android”

  1. Android Overview - Diagnosing Sporadic Errors Says:
    November 16, 2009 at 2:50 pm | Reply

    [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

  2. Diagnosing Sporadic Errors | The Androider Says:
    November 16, 2009 at 6:05 pm | Reply

    [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

  3. Diagnosing Sporadic Errors « Android Junkies Says:
    November 16, 2009 at 8:41 pm | Reply

    [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

  4. Diagnosing Sporadic Errors | AndroidGuys Says:
    November 16, 2009 at 9:15 pm | Reply

    [...] First, gather concrete data. Relying simply on Market comments and the like is not going to get you far. Instead, you need to get at the Java stack trace of the crashes in the field. Fortunately, there are multiple tools to help collect that data, from Flurry to DroidDrop. [...]

  5. Dave @ Datalogging Says:
    November 18, 2009 at 5:27 am | Reply

    This reminds me of a GPS application for Droid where you can log everywhere you go by just using two buttons and then be able to take that off and use it with Google maps.

Leave a Reply