There's certainly scope for development of Apt to include more Treo features. I never had a Treo (well, only briefly) so never got round to that. Many of those things would not be too complicated to add, but of course it requires someone familiar with C and PalmOS.
I had intended to get a Treo and thence have some motivation to do this work, but then I was seduced by the Android Developer Challenge 2, and to be honest I'm glad I've moved on.
As a developer, it's nice to work with a modern development platform and OS, and a class-based language. I've actually written a 'next generation' Apt for Android: tasker.dinglisch.net.
This is as good a place as any to again thank all the people that gave me so much input and support for Apt; I've been able to use many of the suggestions and criticism to come up with e.g. a much better UI experience. I was also inspired to 'take a step back' and generalize away from application- based customization to 'context based customization', where an application is a context, but so is a time, a place, an event etc. and any combination of these can trigger a 'Task' (macro).
As far as Pgr's comment about 'freer platforms', I think I can compare PalmOS and Android quite authoritatively after my recent projects :-)
Android has total application insulation: for security reasons, it's not possible to intercept or inject (most) events while the user is interacting with a particular application. Hence Apt on PalmOS allows a much greater degree of control than Tasker on Android (inserting into fields, tapping buttons etc).
In addition, Android is quite restrictive about customization of hardware buttons.
However, aside from those Android is remarkably open and Tasker can do a lot of the things that Apt can do, plus an awful lot that it can't. Really cool is stuff like tilting the phone right to advance the music player etc.
Hope this post was of interest to some :-)
Pent