We want to thank everyone who joined the Clamr! 2010 user community during version 1.0′s lifetime.
Your usage patterns, feedback and yes – complaints too 
– helped us make what is an outstanding release of Clamr! 2010. We took every single user request and placed it into our product backlog and then sprinted like mad people to deliver as many improvements as possible.
There’s still a couple coming in an incremental release in a few months, but almost 80% of the user requests we had for version 1.0 are in there.
Just some of the highlights of the release:
- A completely redesigned look and feel and experience. We’ve delivered real-time text messaging inside a revamped Clamr! phone. Now when you text or call a contact, you see all the activities you’ve done with them on your Google Voice number (including messages and voicemails) on the phone as well.
- We’ve added a feature called Clamr! Call Sense where a user can select an email thread in Microsoft Outlook and extract all the telephone numbers automatically and present them inside Clamr! Phone to call or text. And since the Clamr! Phone now shows messages for numbers or contact selected, you’ll see the text and calling conversation that took place alongside your email conversation. Very cool feature.
- We enabled attaching a file through Clamr! to a single recipient text (file storage and delivery are free when you subscribe!)
- We completely redid the Clamr! Broadcast text scheduler and removed the dependency on the Outlook calendar which significantly improved performance and reliability.
- We now handles multiple sign-in with Google Voice which was a limitation in version one of Clamr! 2010. Now you can have multiple sign-in activated on your Google Account and Clamr! 2010 functions perfectly.
- And lastly, a billion optimizations.
We do a lot of WPF/Silverlight development here at ManageScope and we’ve been working with the Facebook C# SDK in *****, our new product that’s inflight. And yes — no comment.
We recently ran into an issue with WPF’s WebBrowser not handling #’s introduced by Facebook in URIs during the authentication process. There’s been some good discussion on workarounds … host Winforms (which for WPF proponents like me is disappointing) … distribute your FB app secret and use “code” instead of “token” on responsetype and then exchange the code for a token. Smart thinking, but I wasn’t really satisfied with either solution.
So for community commentary and/or usage, I thought we’d share what we did to resolve this issue. We decided to use AwesomiumSharp and Awesomium’s WebControl in-place of the WebBrowser control from Microsoft.
A little background … when you’re using WebBrowser in WPF, you’re using Internet Explorer. There are many great products from Microsoft, but I’ve never included Internet Explorer among them. Not only do I have to use a browser I’m not fond of, but I’m stuck using whatever version of IE the user has installed on their deck. Not a great experience if you have users like we do who thought a recent upgrade from IE6 was awesome (just poking fun, guys!).
Awesomium on the other hand uses the Chromium project as its basis. And for those of you who are Chrome users, you know the elegance and speed that Chromium provides since you’re using the same foundation. And these kind and extremely talented gentlemen at Awesomium have also worked to provide a .NET wrapper around this Chromium base as well as a pre-rolled WebControl that replaces the functionality of WebBrowser. There are a ton of great things to say about this product … but they say it better here.
Long story short, the issue went away immediately and we were getting our access token without distributing our app secret or hosting the Winform’s browser. Not to mention we got a better control for creating integrated client and Internet experiences and we’re using something other than IE under the hood. If you’re developing in WPF, check it out.
The best calling, texting and file transfer solution for Outlook 2010 just got even better. We’ve just released a new version of Clamr! 2010 that allows you to use Gmail Chat as your phone for calling! No need for a separate phone number – e.g. Skype, mobile, desk – and no reason to leave Outlook 2010 and your keyboard in order to actually take the call.
Download the latest version of Clamr! 2010 on the Download & Buy page. Install the new client and service. Enable your Gmail Chat (click the photo to go to the Gmail Chat instructions site) and then set your forwarding number in Clamr! 2010 Options to “Gmail Chat — username@gmail.com”.
Now all your calls will be handled with Gmail Chat (for free, we might add) and you can use your computer speakers and microphone to handle your calls.
Also — for those of you who use non-US date formats locally … we now support non-US date formats as well.
Enjoy the sweetness of Clamr! And stay tuned as we add more features and functionality …
Clamr! 2010 has been listed as of today in the Google Apps Marketplace and the Microsoft Office Marketplace.
Google Apps Marketplace is the directory for Google Apps add-ons and extensions and provides a forum for customer feedback on experiences with respective products.
If your organization is considering Google Apps as a possible alternative to Microsoft Office Servers (e.g. Exchange or SharePoint), I’d highly encourage you to peruse what is growing to be a very robust offering of products and services that would significantly enhance your company’s experience with Google Apps.
Clamr! 2010 for Outlook 2010 … Free calls, free texts, free broadcast texts, free voicemail management and file transfers with Google Voice in Outlook 2010.