I was watching Craig Cmehil’s Friday morning report and he said a lot of really good things about AIR. Craig is a big fan and it’s always great to have someone like him doing some community evangelism for us, so thanks Craig. But he has a frustration. He doesn’t like how we do AIR certificates.
I didn’t know much about certificates before looking at how they work in AIR. As you probably know, if you want to sign your AIR applications, you need to get a Thawte certificate to do so. But there’s a problem (sort of). Thawte doesn’t allow you to get an individual certificate. They only let you get one if you have a company. I’m not entirely sure why that is, but I assume that it has something to do with liability. The pain of getting a certificate caused Craig to question whether or not it was even valuable to get a certificate. He said that he used 3-4 AIR applications and that most of them weren’t signed.
Signing is a really important part of the AIR process because it creates a contract between the user and the developer. But because AIR makes it so easy to build desktop applications, I can understand the frustration of not being able to get an individual certificate. So for those of you out there building AIR applications as individuals, I want to see if that’s preventing you from signing your apps. If we had a way to get individual certificates, would you sign those apps?
TweetRelated posts: