Difference between revisions of "BerrySync Planning Notes"
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Admon/obsolete}} | ||
| + | |||
{{BerrySync}} | {{BerrySync}} | ||
| − | == To Do== | + | == Major Dates == |
| + | - none yet - | ||
| + | |||
| + | |||
| + | == To Do == | ||
=== RESEARCH === | === RESEARCH === | ||
*[http://supportforums.blackberry.com/t5/Testing-and-Deployment/BlackBerry-Applications-and-code-signing-Start-to-Finish/ta-p/445848 Code Signing] (added May 3rd) | *[http://supportforums.blackberry.com/t5/Testing-and-Deployment/BlackBerry-Applications-and-code-signing-Start-to-Finish/ta-p/445848 Code Signing] (added May 3rd) | ||
| Line 11: | Line 17: | ||
*How the existing crypto works (added May 5th) | *How the existing crypto works (added May 5th) | ||
*How data is stored on the device (added May 5th) | *How data is stored on the device (added May 5th) | ||
| + | *Is there a Blackberry unique id per device, can we use it to do a sort of server 'whitelist' to simplify user connections? | ||
=== MAKE/DO === | === MAKE/DO === | ||
| Line 19: | Line 26: | ||
*Setup Git / make sure you can connect to rome (added May 5th) | *Setup Git / make sure you can connect to rome (added May 5th) | ||
*Make sure you can access Trac and know how to use it (added May 5th) | *Make sure you can access Trac and know how to use it (added May 5th) | ||
| − | |||
== Ideas List == | == Ideas List == | ||
Latest revision as of 19:41, 26 January 2014
This page may be obsolete.
It contains historical information.
It contains historical information.
About BerrySync | Links, Resources | Planning Notes
Contents
Major Dates
- none yet -
To Do
RESEARCH
- Code Signing (added May 3rd)
- Code Signing is NOT REQUIRED for full device use on the simulator
- Code Signing is REQUIRED for full physical device use: "Research In Motion® (RIM) must track the use of sensitive APIs noted as signed when used by applications for security and export control reasons. If you use these controlled classes or methods in your applications, your application must be signed with a key or a signature provided by RIM before you can load the application .cod files onto the BlackBerry® smartphone"
- Using the BB Browser (added May 5th)
- what you can send to it, what you can get from it, embedding in other aps, etc
- How to get data to and from sync servers (added May 5th)
- How the existing crypto works (added May 5th)
- How data is stored on the device (added May 5th)
- Is there a Blackberry unique id per device, can we use it to do a sort of server 'whitelist' to simplify user connections?
MAKE/DO
- Class Diagram (added May 5th)
- UI Mockups (added May 5th)
- Demo implementing the Crypto (added May 5th)
- Demo connected to server successfully (added May 5th)
- Setup Git / make sure you can connect to rome (added May 5th)
- Make sure you can access Trac and know how to use it (added May 5th)
Ideas List
- BlackBerry WebWorks
- Web works is a tool to emulate browser operations within a Blackberry App via webkit rendering engine without invoking the native browser, it is limited to Blackberry OS 6.0 and above.
Existing FF Home Class Descriptions
- Weave Keys
- Stores and makes cryptography keys
- Crypto Utils
- Sync server information and utility functions
- Encryption and decryption functions
- Fetcher
- push and pull to sync server functions
- KeyChain
- iPhone keyChain wrapper
- NSurl_unicode
- Utilities to format url for iPhone NSurl
- Stockboy
- Singleton
- Checks users data and freshens it
- Utilizes fetcher, storage, cryptography utilities
- Store
- Local storage of encrypted information
- SQLite
- Utility
- Platform object return
- Platform string return
