ohmage (http://ohmage.org) is an open-source, mobile to web platform that records, analyzes, and visualizes data from both prompted experience samples entered by the user, as well as continuous streams of data passively collected from sensors or applications onboard the mobile device.
Due to the requirement that each study will usually require slight modifications to the application, we made this library project. It makes it easy to create new apks with different package names which can be deployed independently to the play store if needed. The library project allows us to easily make slight modifications for specific deployments while still keeping a consistent code base.
This library project allows files or resources to be replaced by the apk which uses it. A simple example project which uses this library can be forked from here ohmageApp. Any resources with the same name that you define in your project will override the same resources in this library. This allows for simple configuration for different deployments.
These are the projects which currently use the ohmageAndroidLib
- ohmageApp - The basic wrapper around the library project. Use this project if you wish to build the default version of ohmage which uses this library apk. Fork this project if you want to build your own custom apk which uses ohmage as a backend.
- MobilizeApp - The mobilize version of the app.
Notes: These should all be included as Library Projects. For ActionBarSherlock, you should update its version of the Android Compatibility Library otherwise it will complain that it found 2 versions of android-support-v4.jar. The easiest thing to do is to copy the jar from libs/ in this library to the libs/ folder of the ActionBarSherlock library. For Google Play Services you will also need a Google Maps Android API key which you will reference in your manifest. Information on getting a key can be found here: https://developers.google.com/maps/documentation/android/start.
All other external libraries which are needed are included in the libs directory of the project, but of course you will need the android SDK which can be found here: http://developer.android.com/sdk/installing.html.
We are using a combination of robotium and
calabash-android (which is basically an android
implementation of cucumber). Robotium tests are in the test folder
and can be run as unit tests. The cucumber tests requires calabash-android to be installed. At this point
this fork must be used to do the testing as it includes
additional functionality not available in the main branch. Clone the fork, change into the ruby-gem
directory and run rake install (you might need sudo rake install depending on how your gems are
installed.) Then you can run calabash-android build to build the testing apk, and finally
calabash-android run to start the tests.