Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
New Developer
dwischer
Posts: 51
Registered: ‎09-15-2009
My Device: Not Specified

Blackberry OS Technical Papers

Hi,

 

i am writing my bachelorthesis about mobile application development and one part of my thesis is the description of the Blackberry OS. But i cant find any good ressources about the Blackberry OS and its technical background. Maybe someone here has some good information about the Blackberry OS.

I would be really thankfull.

 

Regards,

Daniel

Developer
dpreussler
Posts: 212
Registered: ‎07-18-2008
My Device: Storm 9550

Re: Blackberry OS Technical Papers

Its not very technical but there is a nice history article here:

http://www.berryreview.com/2009/02/12/the-history-of-rim-the-blackberry-smartphone-part-1-the-origin...

which has some additional links.

You should also try searching the patent database. I know that at least there are technical descriptions about COD format and its history patented.

 

 

You probably know this one already?

http://terrencebarr.wordpress.com/2009/09/30/dont-panic-mobile-developers-guide-to-the-galaxy/

 

If your problem was solved, please mark answer as "Accepted solution"
If your want to thank, click the "kudo" symbol
___________
visit me: http://mobilejavadevelopment.blogspot.com/
visit the Berlin BlackBerry Developer Group: http://berlinblackberrydevelopers.blogspot.com/
Developer
rcmaniac25
Posts: 1,805
Registered: ‎04-28-2009
My Device: Z10 (STL100-4)-10.2.1.3253, Z10 (STL100-3)-10.3.1.997 Dev OS, Z30 (STA100-5)-10.3.1.997 Dev OS, Passport (SQW100-1)-10.3.0.1418, PlayBook (16GB)-2.1.0.1917

Re: Blackberry OS Technical Papers

I never saw those articles, they are pretty cool.

---Spends time in #blackberrydev on freenode (IRC)----
Three simple rules:
1. Please use the search bar before making new posts.
2. "Like" posts that you find helpful.
3. If a solution has been found for your post, mark it as solved.
--I code too much. Well, too bad.