SCamp is intelligent middleware that makes the
device officially “smart” by interoperating legacy apps, newly added apps and the existing UI
SCamp will augment the device interface, apps and behavior with real-time contextual intelligence. In other words, SCamp makes apps “user-aware” and allows them to operate intuitively. See an example of how SCamp will make service delivery smart.
Like SCout, SCamp is standards-agnostic. This means developers can concentrate on mashing-up fantastic apps and not on the burdensome task of integration. Find out more about how SCamp and BREW® MP will make developers’ lives a whole lot better…
To top it all off, SCamp will be available as open source!
Key product features of SCamp:
1. Provide a consistent layer within the device;
2. Expose valuable data across all apps;
3. Learn how the user operates the device and adapt service delivery based on context, location and preferences.
SCamp’s six most FAQs:
1. Can I get SCamp in my phone now?
Not at the moment, we are still developing our SDK.
2. When will there be an SDK?
Planned for Q2, 2010.
3. 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.
4. Is SCamp another OS?
No. One of the great things about SCamp is that it utilizes and augments the existing OS and UI. So the users gets a much more intuitive user experience in a setting they are already familiar with.
5. 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.
6. Do I have to use SCout & SCamp together?
No. Both have extremely rich features on their own, and both will individually improve user experience. 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.