Today I want to talk about something development related again. About libraries for Android apps.
Libraries are a bunch of code that simplifies developing of certain features. Because most Android libraries are open source it's also possible to fork and modify them. But you should take care about the specific licenses.
I'll present you some more popular, but also some not so popular libraries. But all of them are usable for many different purposes.
1. Material Dialogs
Material Dialogs is one of the most popular libraries for Android apps. It's developed by one of the most famous guys from the Android Dev scene, Aidan Follestad.
Material Dialogs is some kind of wrapper for dialogs, which enables you the most easiest way to show users popups. There's also an extension library, that for example helps to create file chooser dialogs.
This library is there to help you creating a bottom navigation for your Android app. It's very easy to integrate and it let's you customize almost every little aspect of the so called â€œBottom Barâ€.
Please remind, that this library is still in beta stadium, so it might be possible that there are big changes with every new release.
Glide is the ultimate image loader library. With Glide it's very simple to download and show images and even GIFs. It's also possible to use it with different transformation implementations, so that you can customize the look of the images.
RecyclerViews are a pretty good way to show lists of entries, but it's also a little bit difficult to implement them. FastAdapter is there to help you with that. It simplifies the implementation of adapter classes for these RecyclerViews and also adds some more options like expanding items. It's really helpful. The library is developed by Mike Penz, another famous Android developer.
Nowadays apps often need to access some internet resources or APIs. But implementing methods to enable the network transfers are often quite hard. Bridge, another library by Aidan Follestad, helps you with that and makes using networks connections very easy. It also brings build-in JSON conversion, so that you don't need to handle all that JSON objects.
6. Android Iconics
Using PNG images for icons on Buttons etc. isn't a good idea anymore. They PNGs needs to be provided in different sizes and also needs to be updated often, when Google decides to update there Material Design guidelines including the icons. Android Iconics offers a very easy way to use SVG vector graphics instead. The icons are saved inside of font files and are more easy to update. The library also includes some extensions with different icon sources.
Using Fragments for different views is better than using single activities for every different view. Fragments are more easily to switch and with the use of Fragments it's also more easy to make an app tablet compatible. FragNav helps you managing multiple stacks of Fragments and switching and navigating between them. It's also pretty cool to use it in combination with the BottomBar library described above.
Do you use any of this libraries in your app projects? What experiences do you have with them? Commentâ€¦