Does anyone have a comparsion chart of the features and benefits between Quickr versus Sharepoint. I am visiting a new customer next week. I could not locate anything like that.
After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era). But in the last decade, there a...
Comments
http://www.duffbert.com/duffbert/blog.nsf/d6plinks/TADF-7LY5CC
You saw Ed's recent post from this week I am sure as well.
If Integration is important, we integrate better to SP.
What the customer wants to do is important as well as Quickr can bring a company into Web 2.0 better than SP but again context is the issue.
I try to provide an ROI of 90 days or less for Quickr projects. Sharepoint can involve hardware and infrastructure costs depending on how they want to roll it out.
Replication for remote locations might be a good selling point as well as Quickr with DAOS can reduce network traffic and disk space usage.
Thanks for the information. I must have missed these two posting. I need to take a look.
Richard
Unless I missed something, neither posting really cover a comparison between SharePoint and Quickr.