Android-Proximity-SDK | Estimote Proximity SDK for Android | iOS library
kandi X-RAY | Android-Proximity-SDK Summary
kandi X-RAY | Android-Proximity-SDK Summary
Android-Proximity-SDK is a Kotlin library typically used in Mobile, iOS applications. Android-Proximity-SDK has no vulnerabilities, it has a Permissive License and it has low support. However Android-Proximity-SDK has 348 bugs. You can download it from GitHub.
Stick an Estimote Beacon at your desk, in your car, or on a package, and the Estimote Proximity SDK will let your app know when you enter or exit its range. Works indoors, in the background, and is accurate up to a few meters. Powered by Estimote Monitoring: Estimote’s own signal-processing technology, with emphasis on maximum reliability. (up to 3 times better than other beacon-based technologies we’ve benchmarked against.
Stick an Estimote Beacon at your desk, in your car, or on a package, and the Estimote Proximity SDK will let your app know when you enter or exit its range. Works indoors, in the background, and is accurate up to a few meters. Powered by Estimote Monitoring: Estimote’s own signal-processing technology, with emphasis on maximum reliability. (up to 3 times better than other beacon-based technologies we’ve benchmarked against.
Support
Quality
Security
License
Reuse
Support
Android-Proximity-SDK has a low active ecosystem.
It has 76 star(s) with 43 fork(s). There are 27 watchers for this library.
It had no major release in the last 6 months.
There are 32 open issues and 68 have been closed. On average issues are closed in 38 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of Android-Proximity-SDK is current.
Quality
Android-Proximity-SDK has 348 bugs (0 blocker, 0 critical, 302 major, 46 minor) and 92 code smells.
Security
Android-Proximity-SDK has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
Android-Proximity-SDK code analysis shows 0 unresolved vulnerabilities.
There are 2 security hotspots that need review.
License
Android-Proximity-SDK is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
Android-Proximity-SDK releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
It has 4215 lines of code, 35 functions and 122 files.
It has high code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Android-Proximity-SDK
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Android-Proximity-SDK
Android-Proximity-SDK Key Features
No Key Features are available at this moment for Android-Proximity-SDK.
Android-Proximity-SDK Examples and Code Snippets
No Code Snippets are available at this moment for Android-Proximity-SDK.
Community Discussions
Trending Discussions on Android-Proximity-SDK
QUESTION
Detect individual beacon using proximity SDK
Asked 2018-Oct-24 at 12:10
I have used this example to detect beacons. In this example, Is it possible to detect which beacon is triggering the action?
...ANSWER
Answered 2018-Oct-24 at 12:10You can do that with the ProximityZoneContext
object that's being passed to the onEnter
/onExit
actions:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Android-Proximity-SDK
Go to https://cloud.estimote.com/#/
Click on the beacon you want to configure
Click Edit settings button
Click Tags and put your desired tag/tags.
Click Save changes Tags are Cloud-only settings — no additional connecting to the beacons with the Estimote app is required!
The ProximityObserver is the main object for performing proximity observations. Build it using ProximityObserverBuilder - and don't forget to put in your Estimote Cloud credentials!.
withLowLatencyPowerMode - the most reliable mode, but may drain battery a lot.
withBalancedPowerMode - balance between scan reliability and battery drainage.
withLowPowerMode - battery efficient mode, but not that reliable.
onError - action triggered when any error occurs - such as cloud connection problems, scanning, etc.
withScannerInForegroundService - starts the observation proces with scanner wrapped in foreground service. This will display notification in user's notifications bar, but will ensure that the scanning won't be killed by the system. Important: Your scanning will be handled without the foreground service by default.
withTelemetryReportingDisabled - ProximityObserver will automatically send telemetry data from your beacons, such as light level, or temperature, to our cloud. This is also an important data for beacon health check (such as tracking battery life for example).
withAnalyticsReportingDisabled - Analytic data (current visitors in your zones, number of enters, etc) ) is sent to our cloud by default. Use this to turn it off.
withEstimoteSecureMonitoringDisabled - using this will disable scanning for encrypted Estimote packets. ProximityObserver will not try to resolve encrypted packets using Estimote Secure Monitoring protocol. Only unencrypted packets will be observed.
Click on the beacon you want to configure
Click Edit settings button
Click Tags and put your desired tag/tags.
Click Save changes Tags are Cloud-only settings — no additional connecting to the beacons with the Estimote app is required!
The ProximityObserver is the main object for performing proximity observations. Build it using ProximityObserverBuilder - and don't forget to put in your Estimote Cloud credentials!.
withLowLatencyPowerMode - the most reliable mode, but may drain battery a lot.
withBalancedPowerMode - balance between scan reliability and battery drainage.
withLowPowerMode - battery efficient mode, but not that reliable.
onError - action triggered when any error occurs - such as cloud connection problems, scanning, etc.
withScannerInForegroundService - starts the observation proces with scanner wrapped in foreground service. This will display notification in user's notifications bar, but will ensure that the scanning won't be killed by the system. Important: Your scanning will be handled without the foreground service by default.
withTelemetryReportingDisabled - ProximityObserver will automatically send telemetry data from your beacons, such as light level, or temperature, to our cloud. This is also an important data for beacon health check (such as tracking battery life for example).
withAnalyticsReportingDisabled - Analytic data (current visitors in your zones, number of enters, etc) ) is sent to our cloud by default. Use this to turn it off.
withEstimoteSecureMonitoringDisabled - using this will disable scanning for encrypted Estimote packets. ProximityObserver will not try to resolve encrypted packets using Estimote Secure Monitoring protocol. Only unencrypted packets will be observed.
Support
Our Kdoc is available here.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page