Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
06-20-2012 07:29 AM - edited 06-20-2012 07:29 AM
First of all, if this is not the proper place to pose this question, please redirect me to a better one
I'm beginning to develop an app which will take me quite some time due to its complexity, but to make it really usefull and widespread I'm planning to release it across all the BB devices: bb smartphones - playbook - bb10
I have, however, 2 big question marks and would like some clarification on how to go about with it, so that I don't waste time in doings things which later can not be used or won't work as expected:
Thanks very much
06-20-2012 07:40 AM
06-20-2012 08:10 AM
I am hopeful, though less than optomistic that what already exists on the BES/ActiveSync side of things can be brought over to the Consumer side. RIM Cloud Serivces should handle this, and it should be included in some push to users of existing BBs.
To be clear I am hoping, not making any informed statement.
06-20-2012 08:27 AM
Are contacts & calendar data the only type of data being considered here?
For 1) it seems like you are describing a classic cloud-based service, where web APIs can serve as the mechanism for transferring data between devices (not just BB, but other platforms too including desktop, of course).
A direct communication channel may eventually be possible through a custom Bluetooth extension. No one has created one yet for BB smartphones, and we don't yet have the architecture in place for 3rd party extensions on BB10 (soon I hope), but I would expect if these pieces were in place, you may be able to transfer data between paired devices.
Both have their pros and cons. A cloud service may be easier to maintain and apply changes to, as well as being easier to use from a user's perspective. However the perceived security may be a concern for users ("What are you doing with my contacts / calendar data?").
For 2) the data would need to be serialized in a format supported by the given sync mechanism. Whether that is text-based (JSON / XML) or binary.
06-20-2012 08:46 AM
If you're hoping of something like an "iCloud" API, where apps can easily store data and access it accross devices: sadly there hasn't been anything announced yet by RIM - at least according to my knowledge.
06-20-2012 09:32 AM - edited 06-20-2012 09:32 AM
Thank you all for the replies.
Adam, let me just clarify better what I mean with nr 2.
Right now the PlayBook has native calendar and contacts, and at the same time, connects via bridge with the BB contacts and calendar.
My question is, when these APIs are in place, what exactly are we going to access? the native or the bridge?
That's why I have this doubt about sync'ing.
PS - Yes I guess I only need contacts and calendar data, but that's a guess, the future will tell these 2 are the most important ones, otherwise the user would have to be duplicating info