Question & Answer
Question
How to develop location-aware apps in IBM MobileFirst/Worklight, Part 2?
Answer
On Demand Consulting
Author: Siwen Wang
This is part 2 by Hisham Abdel-Hafez on development of location-aware apps in IBM MobileFirst/Worklight which covers more advanced aspects of the topic.
The new set of location services introduced in IBM MobileFirst/Worklight 6.0 allows developers to write location-aware applications that capture and transmit a stream of location data, which can benefit both the user who owns the device and enterprises that are looking to grow their businesses. The location data collected from the device sensors by application code is referred to as a device context. This includes geographic data, which is normal longitude and latitude, and WiFi data, which is the WiFi Service Set Identifier (SSID).
The two main pillars for the new location services are:
For more detailed procedure, please follow the link below.
Developing location aware apps in IBM MobileFirst/Worklight Part 2
Author: Siwen Wang
This is part 2 by Hisham Abdel-Hafez on development of location-aware apps in IBM MobileFirst/Worklight which covers more advanced aspects of the topic.
The new set of location services introduced in IBM MobileFirst/Worklight 6.0 allows developers to write location-aware applications that capture and transmit a stream of location data, which can benefit both the user who owns the device and enterprises that are looking to grow their businesses. The location data collected from the device sensors by application code is referred to as a device context. This includes geographic data, which is normal longitude and latitude, and WiFi data, which is the WiFi Service Set Identifier (SSID).
The two main pillars for the new location services are:
- Acquisition policies: Acquiring device context can be exhausting to device resources and, more important, to battery life. It also varies from one application to another according to business requirements. An acquisition policy allows a developer to customize the acquisition behavior in terms of frequency, position accuracy and other properties to match different business requirements.
- : These allow developers to create custom actions based on device context changes. Think of triggers as things that fulfill the following statement: when something happens, take action. In light of this statement, we can explain the components of a trigger:
- Something happens: This can be a change in device context data, like a position change, entering or exiting from a geofence, or connecting or disconnecting from a specific WiFi network.
- Take action: The action can be either something done locally on the mobile device, like updating the user interface (UI) with the new location information, or it can be an event transmitted to the MobileFirst/Worklight server, or it can be both.
For more detailed procedure, please follow the link below.
Developing location aware apps in IBM MobileFirst/Worklight Part 2
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSQTW3","label":"IBM On Demand Consulting for Hybrid Cloud"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
01 February 2019
UID
ibm10771901