{"__v":3,"_id":"55a9410c5d3abb0d0012f1b4","category":{"__v":11,"_id":"55a93098cf45e1390093f351","pages":["55a930bdcf45e1390093f353","55a932afc8bd450d000dd1d6","55a938ba4c661b3700cf4e1f","55a939b502becf2d007aac34","55a93a015d3abb0d0012f184","55a93b225d3abb0d0012f191","55a93c4002becf2d007aac43","55a93d4c02becf2d007aac4c","55a940485d3abb0d0012f1af","55a9409802becf2d007aac64","55a9410c5d3abb0d0012f1b4"],"project":"559a61d2dbcfd20d00710b39","version":"559a61d2dbcfd20d00710b3c","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-07-17T16:43:04.054Z","from_sync":false,"order":4,"slug":"android-sdk-reference","title":"Android SDK Reference"},"parentDoc":null,"project":"559a61d2dbcfd20d00710b39","user":"559a618bdbcfd20d00710b38","version":{"__v":23,"_id":"559a61d2dbcfd20d00710b3c","project":"559a61d2dbcfd20d00710b39","createdAt":"2015-07-06T11:09:06.510Z","releaseDate":"2015-07-06T11:09:06.510Z","categories":["559a61d3dbcfd20d00710b3d","55a589ddaaf9cf1900114dd0","55a589e30f354f0d00fd0312","55a589ea80c8a30d00b323cc","55a589f6aaf9cf1900114dd1","55a58d4e80c8a30d00b323e6","55a8e7a227a17d21005251a2","55a93098cf45e1390093f351","55afb085f202b12100cd9e83","55afb22e902fd51700f5f8bf","55afb260902fd51700f5f8c2","55afb28ec8a85321007a5462","55afb294f202b12100cd9e95","55afb29b902fd51700f5f8c5","55afb2a1c8a85321007a5463","55afb2a7902fd51700f5f8c7","55afb2ad902fd51700f5f8c8","55afb2b5902fd51700f5f8ca","55b74b2131bccb190081bedc","55bb441b54f9640d006e6cf2","565711085cb2420d00d70071","5681681330018c0d006bf7ff","588f38b5923d610f00c72dad"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-07-17T17:53:16.944Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":9,"body":"##Location service authorization\n- By default, MOCA tracks user location and proximity interactions\n- The geo-location is tracked with 100-meter precision. \n- This is performed by means of Google Play Services Locations API\n- The user must allow the location tracking for the device\n- The geo-location minimizes battery usage by employing adaptive tracking\n- When the permission is not granted, MOCA does not track user location.\n\n##How event tracking works\n- MOCA SDK uses SQLite database stored in a local file on your phone to store all locally tracked events.\n- Periodically, when your device is connected to Internet (via Edge, 3G, LTE or Wifi), \u000bthe SDK incrementally transfers the packs of events to the cloud.\n- The local database is freed only when the transfer is successful (Store-And-Forward)\n- By default, the event transfer is performed every 15 minutes\n\n##Offline behavior\n- MOCA SDK downloads proximity campaigns data from the cloud asynchronously using \u000bperiodic asynchronous background fetch mechanism. \n- The frequency is controlled by SDK but can also be tuned by the app.\n- The downloaded data is persisted locally and acts as a cache.\n- If the connection to Internet is not available, the cached data is used to run the campaigns.\n- This enables you to offer proximity experiences even if the Internet connection is saturated or not available.","excerpt":"","slug":"design-considerations-1","type":"basic","title":"Design considerations"}

Design considerations


##Location service authorization - By default, MOCA tracks user location and proximity interactions - The geo-location is tracked with 100-meter precision. - This is performed by means of Google Play Services Locations API - The user must allow the location tracking for the device - The geo-location minimizes battery usage by employing adaptive tracking - When the permission is not granted, MOCA does not track user location. ##How event tracking works - MOCA SDK uses SQLite database stored in a local file on your phone to store all locally tracked events. - Periodically, when your device is connected to Internet (via Edge, 3G, LTE or Wifi), the SDK incrementally transfers the packs of events to the cloud. - The local database is freed only when the transfer is successful (Store-And-Forward) - By default, the event transfer is performed every 15 minutes ##Offline behavior - MOCA SDK downloads proximity campaigns data from the cloud asynchronously using periodic asynchronous background fetch mechanism. - The frequency is controlled by SDK but can also be tuned by the app. - The downloaded data is persisted locally and acts as a cache. - If the connection to Internet is not available, the cached data is used to run the campaigns. - This enables you to offer proximity experiences even if the Internet connection is saturated or not available.