14 DAY TRIAL // Canadian mobile phone maker Research In Motion launched its official BlackBerry Developer's Blog on Tuesday. Aimed mainly at the BlackBerry developer community, the new blog should provide compelling and informative content, the company says, while also adding that the BlackBerry Developer's Blog comes as part of the BlackBerry Developer Zone experience.
To get the blog started, there are already some posts published there, one announcing the release of new BlackBerry Web Development Tools, including the BlackBerry Web Development Plug-in for Eclipse and the BlackBerry Plug-in for Microsoft Visual Studio, while another one talks about BlackBerry location-based services (LBS).
According to RIM, the BlackBerry Developer’s Blog will be focused on three different areas, described as follows:
- Technical Discussion and Insights – Including best practices for BlackBerry development, code snippets, and general technical information on how to make applications users will come back to time and again. - Market Insight – Discussions of trends and opportunities in mobile development and mobile applications that RIM sees from breathing the mobile industry every single day. - Developer Engagement – We have substantial plans to get more engaged with our regional and local developer communities all around the world, from Australia to Argentina and everywhere in-between. We will be using the BlackBerry Developer’s Blog to communicate events in your region and opportunities to meet other BlackBerry developers.
The Canadian phone maker, as many of you might already know, has recently launched a software portal for its BlackBerry devices, caller the App World. Following the release of Apple's App Store for the iPhone, a wide range of mobile phone makers also came up with their own application stores, RIM being one of them. Given the tight competition, it was expected for the company to come up with a solution to attract developers on its side. Those who would like to access the newly launched BlackBerry Developer's Blog should head here.