TL;DR – Today marks the release of GnuCash Android v2.1.5. This will be last release supporting Android devices running 2.3 (Gingerbread) to 4.3 (Jelly Bean). Starting from version 2.2.0, only Android 4.4 (KiKat) and above will be supported in newer releases.
For many years, GnuCash Android has supported as many Android releases as possible. As newer Android versions get released, it gets harder to take advantage of newer features while maintaining backwards compatibility with older Android versions. The Android Support Library has helped much in that regard, but there are some features which become available in newer versions of Android which cannot be ported via the support library. A while back, the minimum API level was raised from 8 (Froyo) to 10 (Gingerbread) in order to take advantage of newer API features. Today we are taking another step in the evolution of GnuCash Android.
The Android Storage Access Framework (SAF) was introduced in Android 4.4 (KitKat) and allows Android applications to open and save files on any number of services without having to perform separate integrations with each one. The presents a uniform interface to the users of the platform and the same set of APIs to the developers for accessing and saving files irrespective of the file synchronization service.
GnuCash Android currently supports exporting transaction data using Dropbox, Google Drive and ownCloud, by having explicit integrations for each one. There are always more requests for integration coming in., but it is impossible to include the SDKs for all available file sync services.
Starting from v2.2.0, GnuCash Android will be using the Storage Access Framework for exporting files to third-party services. This should improve the reliability of the export and synchronization of the files.
However, the SAF only works when the 3rd party providers support it. And I must say I’m a bit disappointed by the level of support from the big players in file sync. As far as I can tell, as of today, the support for SAF is as follows:
- Google Drive – full support, as would be expected from Google.
- OneDrive – partial support. Ability to read/open files, but no ability to write files
- ownCloud – read-only support
- Dropbox – no support at all
GnuCash Android will keep integration with Dropbox since it is relatively popular with GnuCash Android users and has no support at all for the Storage Access Framework. All other explicit integrations will be removed and will only work through the Storage Access Framework.
All users with devices running Android 2.3 to 4.4 will continue to have access to v2.1.5 of GnuCash Android. I hope this change has minimal disruption for the most users.
Hard to believe it’s been 3 years already since the first release of GnuCash Android to the Google Play store. Since then, the app has come a long way from it’s humble beginnings as a simple expense tracker which saved a transaction and an amount and exported them to OFX.
Over several iterations in the 1.x series, we added support for double-entry accounting, split transactions, import and export of GnuCash XML files, support for QIF export format and more. We also now have 4 regular contributors instead of just one which bids well for the future 😉
Today we are announcing release of v2.0.0 of GnuCash Android which is the first major design overhaul. The app now follows the material design guidelines with bold use of color for distinguishing accounts, calculator for transaction entry, improved reporting, multi-currency transactions and so much more.
The full changelog for the v2.0.0 release can be found on GitHub. There is also a GnuCash Android Google+ community where you can discuss with other users, suggest ideas, and interact with the developers.
I am also pleased to announce that starting with v2.0.0, Kindle Fire users can also download GnuCash Android directly from the Amazon App Store for Android
The app has been slowly rolling out in the Google Play store over the past week, so some of you may have it already. Today, we are making it fully available to everyone. We look forward to your feedback and hope you enjoy using it as much as we did developing it.
26 January 2013´- That is the date when the Android Contact Picker library first went live in the Maven central repository. The Android contact picker library enables you to support the workflow of opening the contact list, user picks a contact, selects a number and then have that number returned to your application through an Android Intent.
Since that time, several things have happened in the Android universe; new Android releases, migration to Gradle as the preferred build system for Android, introduction of Android Studio, Material Design and much more.
Well, over the weekend, I updated and published v3.0.0 of the Android Contact Picker library to maven central. This update includes the following:
- Update to Material design
- New menu option for searching contacts
- Menu option for adding a new contact
- Added a new sample application for testing the app
- Bug fixes
The new library is deployed as an .aar artifact to the Maven central repository. This is the library format currently preferred by gradle and eases integration with your current application. To use the library, simply add the dependency to your Gradle file as follows:
The minimum supported Android API level has also been increased from API level 7 to 8 and the library uses the AppCompat library for backwards compatibility support.
As always, your feedback is welcome! Tell me in the comments how you use the library, and what kinds of things you are missing, or just that you like it