Let's say I have an enterprise application out of which I want to pull some data for display in a widget. Obviously, that data is going to be secured, so two things need to happen: first, my widget canvas needs to support secure data access, and second, I need to trust my widget engine to access my enterprise applications on my behalf.
Desktop-based widget engines like KlipFolio and Skinkers are already used for delivering sensitive data. They support encrypted, password-protected data retrieval, and they store encrypted credentials on the user's machine.
While other widget platforms have focused on offering increasingly GUI-rich interfaces, KlipFolio has concentrated on keeping things small, consistent, and secure. We're not about running Yet another Clock Widget (YACW) on your desktop; rather, it focuses on providing a very small, efficient dashboard to save you time and effort.
We target our product for the every-day users, but we've built it secure enough for deployment both internally and externally by corporations to access sensitive data, such as our recent use of KlipFolio Branded for American Express.
We're glad that Richard and Charlie are pointing out that security of the platform is important for business uses of a widget.
