Recommended Android libraries by Udacity

Creating a content provider is no easy feat, and it has many components. Many developers have struggled with this, so naturally, someone created a library to simplify this process. Check out Schematic for an example of such a library.

Loading images over the network is a challenge since it depends heavily on network availability and consumes a lot of battery. There are many libraries that help with this, including robust features such as caching, configured timeouts and more. See Picasso for an example of such a library.

Barcode scanning is a feature that is available in many different applications, so that should give you a hint that there are libraries that help with that. The Google Mobile Vision library includes API’s for scanning barcodes.

Complex logging needs can also be addressed using Libraries. The default logger falls short if you need to modify what kind of things you need displayed in the debugger depending on what version of your app is Running. Timber includes this, and many more features.

This entry was posted in Application Development and tagged . Bookmark the permalink.

1 Response to Recommended Android libraries by Udacity

  1. Additional notes:

    Here are some other Libraries that many Android applications use.

    Picasso and Glide An extremely common problem that Android developers face is the proper use of images in their application. Including many high quality images will drastically increase your apk size, while downloading images over the network comes with memory consumption and network availability problems. Picasso and Glide are both very robust libraries that facilitate the loading, caching and displaying of Images. They include tons of amazing features, such as the ability to include placeholder images and local caching, so almost every application that includes images uses one of these. Check out the documentation on Picasso and Glide.

    Butterknife: If you’ve created an app with a lot of views, then you’ll know how tedious it can be to write findViewById() calls for each one, as well as to create custom onClicks for each one. These tasks pertain to Data Binding, the realm of connecting your data to the user facing views. Butterknife is a revolutionary library that uses annotations to make this much easier. Check out the documentation for some examples of how this can make your life much easier. You can even implement it in our Emojifier app if you want, checkout this code to see how it would look.

    Timber: Created and maintained by the same guy that created Butterknife, Timber is a really cool tool for Logging. I’m sure you have all used the built-in Logger and know the importance of seeing information about your app in the debugger. Timber takes this further by providing a modifiable platform for all your logging needs. It contains these, and many more features: Log without a TAG (Timber creates one for you); Create different logging logic for Debug and Release version of your app (you probably only want to see errors in the release version); Automatic error detection. Again, you can see this library in action in our Emojifier application if you want here, but it is totally optional.

Leave a Reply

Your email address will not be published. Required fields are marked *