Here's another "mind map" that I hope will help developers understand what are the implications of Platform Security on the Symbian Signed process. To me it is self-explanatory but I would happily answer any questions you might have on the topic.  (More)

Still looking for an answer to this question? The new release of Carbide.c++ comes with the "Capability Scanner" tool, a static code scanner that will identify the APIs used in your code, map them against a database of known APIs and their capability requirements and then provide you will a balance of what you have and what else should be added.  (More)

A background note first: I wrote this post on 09.03.2008, right after ending the talk on this discussion board thread. It was visible for a few minutes but then I took it back, with the hope that I am wrong, and Jeepy/Domi will not go ahead with his plan. But he did, and now so do I. (More)

No media hype, no cool videos and no amassing press releases. Not yet anyway :) But yes, the S60 3rd Edition SDK, supporting Feature Pack 2 (aka S60 3.2 SDK) is out and waiting for you to download it. (More)

A small bit of news collected from the Carbide.c++ Beta group: the original Carbide.++ release had version number 1.3 build 23 but starting with 14.03.2008 the download package contains the new build 24. No details have been provided about what bugs have been fixed in this silent update but I'm sure there must be some so do check the release notes and download the package (or the other way around).

Download Carbide v1.3 at http://www.forum.nokia.com/carbide_cpp.

So, what else is Jason Calacanis doing when not teaching others the startup 101? (More)

Does anyone know why this application cannot be found anywhere for download, despite the huge amount of requests received from eager phone owners? (More)

Don't worry, this is not yet another long article about what Platform Security is and why is it the second best thing ever, after the sliced pizza of course. O wait, that's the iPhone. Ok, ... the third!  (More)

You know it and I know it, the SDK documentation can be better. In many ways. But maybe the most critical issue is the way the returned errors, leave codes and panics are "documented" is really mind-bugling. One frequent statement is something like "If something goes wrong the method will leave with a system wide error code". Great, like I could not say that by just seeing the nice method name. (More)

Isn't it fun when people seem to have a lot of fun screaming that, well, ... it's no fun? (More)