This part of documentation is intended to get you up and running with the Resonance Andorid SDK framework. We’ll walk through from setup to running your own Resonance-Powered-App.
This part is aimed to provide in depth details on how to approach development and it is organized as follows:
Below is reported current stable Gradle configuration for Resonance SDK for Android. Please be aware that using different version combinations may lead to unexpected behaviors.
1 2 3 4 5 | compile 'com.atooma:engine:2.0.1'
compile 'com.atooma:modules-mobile:2.0.1'
compile 'com.atooma:modules-server:2.0.1'
compile 'com.atooma:modules-google:2.0.1'
compile 'com.atooma:resonance:2.0.1'
|
In addition to application configuration, top level build.gradle
must also include credentials for accessing Atooma packages.
You can get credentials by following instructions reported in section What You Need?.
1 2 3 4 5 6 7 8 9 10 11 12 | allprojects {
repositories {
jcenter()
maven {
url "http://atooma.bintray.com/resonance"
credentials {
username 'YOUR USERNAME'
password 'YOUR PASSWORD'
}
}
}
}
|
Below is reported the basic Manifest configuration allowing to use resonance effectively. Additional directives may be needed in case you decide to use specific modules. All related details are reported in section reference.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | <uses-permission android:name="YOUR_PACKAGE_NAME.permission.RESONANCE" />
<permission
android:name="YOUR_PACKAGE_NAME.permission.RESONANCE"
android:protectionLevel="signature" />
<!-- ... -->
<meta-data
android:name="com.atooma.resonance.sdk.ApplicationId"
android:value="YOUR_ID" />
<!-- ... -->
<provider
android:name="com.atooma.activitytracker.history.ActivitiesProvider"
android:authorities="com.atooma.resonance.activitiesYOUR_ID"
android:exported="false" />
<provider
android:name="com.atooma.activitytracker.history.LocationsProvider"
android:authorities="com.atooma.resonance.locationsYOUR_ID"
android:exported="false" />
<provider
android:name="com.atooma.resonance.provider.SnapshotProvider"
android:authorities="com.atooma.resonance.snapshotsYOUR_ID"
android:exported="false" />
|
Please notice that the Application Id
required in Manifest is provided by Atooma Team together with credentials for accessing repositories.
Dec 2, 2015
Package | Version | Changes |
---|---|---|
engine |
2.0.1 |
RULE_TRIGGERED permission replaced by RESONANCE in manifest.
getActiveModules method now available in Atooma class.
Updated meta data to be provided for Instagram authentication.
Bugs squashed here and there. |
modules-mobile |
2.0.1 |
Code optimization. |
modules-server |
2.0.1 |
Code optimization. |
modules-google |
2.0.1 |
Code optimization. |
resonance |
2.0.1 |
Improved activity tracking with main focus on path recognition. Location provider configuration to be added in manifest. ACTIVITY_DETECTION and DATA_COLLECTOR_ENTRY_PERSISTED permissions replaced by RESONANCE in manifest. |
Nov 10, 2015
Package | Version | Changes |
---|---|---|
engine |
2.0.0 |
Code optimization. |
modules-mobile |
2.0.0 |
Package just includes all modules related to mobile device features. |
modules-server |
2.0.0 |
Package just includes modules related to server device except the ones related to Google services. |
modules-google |
2.0.0 |
Package just includes modules related to google services.
Gmail trigger INCOMING has been improved for
allowing to receive real time updates instead of relying on
periodic checks. |
resonance |
2.0.0 |
Code optimization. |
Please notice that modules-mobile
, modules-server
and modules-google
do not depend on each other. This means developer can use even just one of them in case he’s just interested in a subset of integrations.
Oct 21, 2015
Package | Version | Changes |
---|---|---|
engine |
1.0.7 |
- |
engine-modules |
1.0.10 |
Google Drive triggers have been added: FILEDELETED ,
DIRDELETED , SPACEUSED , FILEMODIFIED . |
Google Drive performers have been added: FILEADD ,
FILEDELETE . |
||
resonance |
1.0.1 |
- |
Oct 16, 2015
Package | Version | Changes |
---|---|---|
engine |
1.0.7 |
Added extendible subsystem for identifying possible conflicts between rules and within a rule definition itself. |
engine-modules |
1.0.9 |
Google Drive first implementation has been added. |
Google Calendar trigger has been added: ON-OVERLOAD . |
||
Gmail trigger has been added improved. INCOMING
allows to mark mail as read once it is received. |
||
resonance |
1.0.1 |
API for getting STILL and VEHICLE sub-activities has been
added. |
Oct 9, 2015
Package | Version | Changes |
---|---|---|
engine |
1.0.6 |
Bugs squashed here and there. |
engine-modules |
1.0.8 |
Dropbox first implementation has been added. |
resonance |
1.0.0 |
- |
Sep 30, 2015
Package | Version | Changes |
---|---|---|
engine |
1.0.5 |
- |
engine-modules |
1.0.7 |
Instagram triggers have been added:
NEW-PHOTO-FROM-ME , NEW-PHOTO-FROM-FOLLOWING ,
NEW-VIDEO-FROM-ME , NEW-VIDEO-FROM-FOLLOWING . |
resonance |
1.0.0 |
- |
Sep 25, 2015
Package | Version | Changes |
---|---|---|
engine |
1.0.5 |
- |
engine-modules |
1.0.6 |
Allowed usage of Google channels on devices lacking of
Play Services . |
Twitter first implementation has been added. | ||
Instagram first implementation has been added. | ||
Google Calendar trigger has been added: ON-EVENT . |
||
resonance |
1.0.0 |
- |