Introducing SCamp:
4DK’s intelligent middleware for the device
 |  |  |  |
|---|
|
From the handset development point of view, SCamp will offer a set of APIs to enable application interoperability and interworking. SCamp will expose a framework that allows existing APIs to communicate with each other in a richer and more flexible manner, allowing seamless access to data and services across the whole handset. Ultimately, SCamp makes life easier for developers to create smarter and more dynamic applications. |
SCamp’s unique context engine collects information from all the sources available in the device (eg: GPS, calendar, settings etc) and processes it to provide meaningful context indicators. For example, from GPS SCamp derives location, from the accelerometer it derives velocity, from the calendar it derives event-based information. All of this information is exposed via API to the developer. |
To make life even easier, SCamp also facilitates device-based service discovery and registration within the native UI. For example, if a new application is downloaded to the device, SCamp will be aware of it and be able to expose it to the rest of the device ecosystem – on-the-fly. In addition, it will automatically expose it to the existing application menu to facilitate its discovery and access by the end user. |
SCamp FAQs:
|
1. Can I get SCamp in my phone now? Not at the moment, we are still developing our SDK. However, as part of two custom development projects we are currently working on, SCamp will be embedded into a communications app and an extreme sports app. |
2. How are you planning on offering SCamp? SCamp will be offered on an open source licensing model. We really want people to benefit from SCamp and to take ownership of how SCamp’s fantastic features are used. Open source is the best way to achieve this. |
3. Is SCamp another Operating System? No. One of the great things about SCamp is that it utilizes and augments the existing OS and UI. This means the user gets a much more intuitive experience in a setting they are already familiar with. |
4. Do I have to use SCout & SCamp together? Well, technically, no. Both have extremely rich features on their own, but if you truly want to harness the power of SuperConnectivity®, then you really need to have the connection, and communication of context, between them both. |
What do you mean by “context?”
Your context is defined from moment to moment by: where you are, who you are with and what you are doing. As a wireless user, this will include the device you are using, the services you are subscribed to, the network you are on. So, your context might be as simple as: wanting your text messages read out to you whenever you’re driving – which is automatically invoked because you’re using your Bluetooth device. Here’s a simple example of what we mean when we say ‘user-aware’ (or in other words, context):
1. I know you’re about to have a meeting (context indicator: calendar)
2. I know you’re missing a meeting (context indicators: calendar + location)
3. I know you’re on your way to that meeting (context indicators: calendar + location + speed)
View the full set of context indicators