Context States for Android supports Android versions greater than 2.2.
Intel® Cloud Services Platform Developer FAQs - Context Services
- What Android versions are supported by Context States for Android?
- Can I use Context SDK from an Android Service?
- Can I get states from another device for the same user?
- Can I add a listener to a disabled state?
- Can I enable only a specific number of states to be collected?
- Can I have different states’ vectors, one for each user device?
- Can I push a custom state which is not listed in Context SDK?
- Do I need to logout after closing the application?
- Do I need to login in order to start collecting states?
- Do I need to enable the GPS in order to collect location states?
- Can I configure how the states are collected?
- I registered with Intel Cloud Services Platform but don’t remember which email I joined with.
- How do Context Services behavior models differ from a recommendation engine?
- My app stores and analyzes data types you have not listed. Can I store and retrieve other types of data with Context Services?
- What types of data does Context Services store?
- Which platforms are supported?
- Where am I allowed to sell my app if I use the Intel Cloud Services Platform beta?
- What is the cost of the Context Services APIs?
- Can I use only Context Services in my app?
- My apps require the collection, analysis, and use of explicit and implicit personal context to deliver rich user experiences. How do my apps protect the privacy of end users?
- What is the function of Context Services APIs?
- How is "context" defined in Context Services?
- Can I embed third-party widgets such as YouTube* videos or Google* Maps into my app?
- What about technical support?
- Is there a cost to use these services?
- What Context Services are available?
Yes. The library supports to be used within an Android service by declaring the correct information in the Android manifest file.
Yes. It is possible to get the states of another device of the same person.
Yes. Adding a listener to a disabled state will enable the state collection.
Yes. Each state is enabled separately.
Yes. Each different device has a unique ID which allows you to maintain different states’ vectors for the same user.
No, you are only allowed to push a state which applies to the supported ones.
No, it is not required.
Yes. After login, you will be able to collect and push the states to the Context Services. This will allow you to enhance your states’ vector and enable more cloud features.
No, but you will obtain more accurate location states by enabling the GPS. Network location should be enabled in location access settings if GPS is not enabled, otherwise location is not collected.
Yes. Each particular state type can be configured using settings. Make sure you pass the right settings. Bundle parameter when enabling it.
We can help you out. Please contact our support team.
Context Services behavior models "learn" a user’s behavioral patterns by collecting and analyzing specific user context (e.g., context about places a user visits). The output of the model is a scored/weighted list that is essentially enhanced context that may serve as input to recommendation systems (which evaluate large amounts of various types of context via any type or combination of analysis techniques such as collaborative filtering, content filtering, Bayesian inference, etc.).
Context data types supported in the current release are:
• Point of interest (POI) search history
• Computed navigation route
• POI check-ins
• POI ratings
• Current location
This is a cloud service: it is cross platform and not device specific. You can use it to build hosted web applications or native applications running on laptops, smartphones, and tablets. The only requirement for the platform is that it has a web browser, and that it can perform HTTP requests.
You may sell it in any store including the Intel AppUp® center.
Context Services APIs are free to use, but use is restricted to:
• 1 million API calls per developer per API key per day
• 500 API calls per developer per API key per second
No, Intel Identity Services are needed for user login purposes.
Context Services APIs for privacy controls empowers end users with ultimate control over their data/privacy by prompting them to specify what data apps can collect and use for their personal context. They also enable users to delete personal context that has been stored by the service.
Context Services APIs enable you to build context-aware apps that are responsive and personalized to a user’s situation and needs, while empowering users with ultimate control over their privacy. The APIs enable collection, monitoring, storage/retrieval, and analysis of context. Behavior model APIs based on pattern analytics of user behavior enable apps to adapt to a user’s situation and enable proactive recommendations. The API for privacy control enables users to ultimately control what context about them can be collected and how it can be used.
Context is any information, explicit or implicit, that can be used to characterize the situation of an entity. An entity is a person, place, object, or media that is considered relevant to the interaction between a user and an application.
Yes. Be sure to follow the terms and conditions required by the owners of those services/widgets.
You can ask questions, get help, and provide product feedback on our Support Forum.
There is no cost to use the Cloud Services Platform beta. However, there is a daily limit on the number of calls that your app can make to the API. Your app can make a total of 1 million API calls per developer per API key per day or 500 API calls per developer per API key per second.
Cloud Services Platform beta provides a set of Context Services that make apps aware and customizes them by providing the ability to collect, aggregate, store, and analyze user data, starting with location data. Services currently available are: context data types, privacy controls for end users, storing/retrieving context, monitoring for new context, and behavior models.