Page tree
Skip to end of metadata
Go to start of metadata

Getting Started

The Bluedot Point SDK enables an 'always-on' geo-location capability for apps by delivering accurate location awareness, while substantially reducing battery consumption compared to Core Location or other standard methods. The Point SDK connects to the Bluedot's backend system, Point Access, to download your pre-configured Geofences, Geolines™, Bluetooth Beacons, conditions and actions.

The Point SDK enables rapid development of location-aware apps. It delivers precise location awareness to the mobile application, but without the usual battery drain that would typically occur. There's also no need for additional hardware, making it highly scalable. This means the Point SDK enables location-based apps and experiences that were previously impossible. The rest is up to you.

The Point Access web application provides interfaces to configure location-related data for mobile Apps powered by the Bluedot Point SDK. The Point SDK then downloads and executes them within the Application, both in foreground and background execution modes.

Developer resources for the SDKs for Android and iOS, Bluedot Point Access and Public APIs can be accessed from this page.

From the Bluedot team.

Latest Release

Release date February 24, 2017

Point SDK for Android V1.9.4

  • New Feature:

    • This release introduces support for triggering actions based on the Sequential, Bearing and Speed conditions configured at the Zone level on the Bluedot backend.

    • Android O support added. 
  • Defect fixes:

    • Minor defect fixes and improvements to enhance performance and stability.

Point SDK for iOS V1.9.4

  • New Feature:

    • This release introduces support for triggering actions based on the Sequential, Bearing and Speed conditions configured at the Zone level on the Bluedot backend.

  • Defect fixes:

    • Minor defect fixes and improvements to enhance performance and stability.

Point Access V1.9.4

  • New Feature:

    • Sequential condition to allow for triggering of actions on the mobile devices based on the direction at which the devices cross geofences. The Geofences in a zone can be ordered and a percentage can also be specified to enhance the reliability of triggers.

    • Bearing condition to allow for triggering of actions on the mobile devices based on the angle at which the devices enter a geofence. It is now possible to trigger actions on user devices that entered the geofences from the north only.

    • Speed condition to allow for triggering of actions on the mobile devices based on the travel of the devices at the time of entry into a geofence. 

  • Defect fixes:

    • Bug fix for correcting issues with the chronological sorting of Check-in activities log at the Zone level.

Public APIs V1.9.4

  • New Feature:
    • The APIs support adding and updating of Sequential, Bearing and Speed conditions

 

More information on the complete version release notes can be found here.

  • No labels