tag:blogger.com,1999:blog-10124852.post7058622957438475672..comments2023-03-17T22:02:34.195+11:00Comments on This is the old ChiefTech blog...: Design considerations for a generic activity stream desktop toolJames Dellowhttp://www.blogger.com/profile/11816163470369202593noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10124852.post-85847767601976856312009-03-10T18:13:00.000+11:002009-03-10T18:13:00.000+11:00Hi James, Congratulations on your new role (annnou...Hi James, Congratulations on your new role (annnounced in today's Australian IT section). <BR/><BR/>Wasn't able to use the chat function above - came up with an Error 404 - but it's probably the firewall issues here.<BR/><BR/>Andrea LaiAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-10124852.post-24908909915546425042009-03-09T11:24:00.000+11:002009-03-09T11:24:00.000+11:00Hi James2 things we learn't back when we built Zap...Hi James<BR/>2 things we learn't back when we built ZapTXT: <BR/>1. Ubiquity: Adoption risk is drastically lowered when using ubiquitous, existing consumption mechanisms (IM, Skype, Email, Mobile etc) that users are already comfortable with vs. a client. I realize this might be a little easier in the enterprise where such things can be centrally managed. <BR/>2. Presence: Probably more important than ubiquity, employees are increasingly mobile and perishable information needs to find them. So there needed to be smart routing to bounce filtered updates from IM to SMS or Phone when a user is away. Desktop apps might have limitations when you need to let the information find the user, not the other way around.Anonymousnoreply@blogger.com