ClarkKent
‘A mild-mannered reporter’ library for android
Gaurav Lochan
Little Eye Labs

Friday 6 December 13
Problem
Getting info from a production app
Important Events / Logs
Failures (not just crashes)
Latencies
Very useful for d...
Related Services
Crash Reporting - Crittercism, Crashlytics, Bugsense
Analytics - Flurry, Google Analytics, Omniture
BaaS:...
Where would you see
these?
Crittercism

Flurry

Errors

Y

Y

Y

N

Events

N

Y

Y

N

Latency

Friday 6 December 13

Par...
ClarkKent
Provides simple abstraction for ‘reportable’ objects:
Event
Failure
Latency
Configure which service to report to
...
Sample Code

Friday 6 December 13
Roadmap
Client
Implement different reporters (Crittercism, Parse,
Flurry etc)
Implement offline mode
Use Java annotations f...
Logger
Much more lightweight than log4j / slf4j
Wraps around android.util.log. Change log level with
runtime flag
Write log...
Contact

@gauravl
https://github.com/LittleEyeLabs/Garage/tree/master/
android/utils

Friday 6 December 13
Upcoming SlideShare
Loading in …5
×

ClarkKent - A remote reporting library for android apps

989 views

Published on

Any android app with over 10K users is bound to face errors that are hard to debug remotely. Event getting the logcat is often not enough.

ClarkKent ('a mild-mannered reporter') is a library tries to solve this problem by enabling an app to report failures, events, and latencies to a service. The nice part is that the remote service is configurable, and can easily be switched - today it supports Parse, Crittercism, Crashlytics and will support Google Analytics soon.

It also includes a nice Logging abstraction library.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
989
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ClarkKent - A remote reporting library for android apps

  1. 1. ClarkKent ‘A mild-mannered reporter’ library for android Gaurav Lochan Little Eye Labs Friday 6 December 13
  2. 2. Problem Getting info from a production app Important Events / Logs Failures (not just crashes) Latencies Very useful for debugging issues, understanding app usage, and optimizing for different devices Friday 6 December 13
  3. 3. Related Services Crash Reporting - Crittercism, Crashlytics, Bugsense Analytics - Flurry, Google Analytics, Omniture BaaS: Parse, StackMob, etc Provide good queries, flexible Friday 6 December 13
  4. 4. Where would you see these? Crittercism Flurry Errors Y Y Y N Events N Y Y N Latency Friday 6 December 13 Parse New Relic Y Y N Y
  5. 5. ClarkKent Provides simple abstraction for ‘reportable’ objects: Event Failure Latency Configure which service to report to Append key info for each report (deviceID, userID, timestamp, etc) Optimized: Batch network calls, offline mode Friday 6 December 13
  6. 6. Sample Code Friday 6 December 13
  7. 7. Roadmap Client Implement different reporters (Crittercism, Parse, Flurry etc) Implement offline mode Use Java annotations for reportables Server Implement a custom UI on top of Parse - better queries Friday 6 December 13
  8. 8. Logger Much more lightweight than log4j / slf4j Wraps around android.util.log. Change log level with runtime flag Write log to a file, support uploading log Use varargs to prevent unnecessary string construction Friday 6 December 13
  9. 9. Contact @gauravl https://github.com/LittleEyeLabs/Garage/tree/master/ android/utils Friday 6 December 13

×