I just thought I’d put up a quick post on Yasu progress, mostly because I’ve come to the point that I must admit to myself that it’s not going to be possible to roll functionality for both Jaguar/Panther and Tiger systems into one neat little package. There are just too many differences between the two to make it work well together. So with that, development on the version for Jaguar/Panther (1.0.3) is now officially frozen. There will be no further changes to that release for those systems.

However, now that I’m free to run amok in Tiger goodness without the burden of coding for previous systems, I’ve been able to work all sorts of coolness – like dialing in honest to goodness keychain support for those who begged for it, as well as fortifying the authentication routines to a level that’s even better than before. There’ll be some other cool (exclusive) features that many will enjoy, too. Just wait and see.

Which brings me back to a previous point. With the amount of work that’s going into this project, I’ve changed my mind (again) about the whole nagware thing. Yep, that’s right. Version 2 of Yasu is going to require a personalized registration code. The app won’t be crippled in any way, it’s just going to nag you to buy a license every fifth time you launch it. Some will be able to live with getting nagged, others will feel compelled to purchase. Either way, it’s cool. With a price point of a meager $5, and free upgrades, I think it’s a pretty fair deal. For those who don’t think so, I’m willing to accept the fact that having to lay cash out is going to turn you off to Yasu. It’s a bummer, but that’s just something I’m going to have to live with.

By the way, if you’ve donated in the past, be looking for me to contact you through email about getting you a registration code shortly before the official release. It’s just my way of saying thanks for your past support.