Microsoft Exchange’s Public Folders natively on any device
Conception, Branding, Website
Conception, Branding, Website
Microsoft Exchange offers a lovely feature called Public Folders, which allows companies to create a single pool of contacts, calendar events, etc. and share them amongst employees. Outlook natively supports these features, and it integrates nicely. Even better, access to these shares is managed via Active Directory, so IT has full control.
A client approached the IT team at Immense Networks wanting to access this data on their mobile devices. While a user’s contacts, emails, and calendars sync flawlessly with nearly any device, Public Folder synchronization is a lacking feature of ActiveSync.
So, we looked for solutions.
Other companies have developed solutions to this problem; most require users to download a 3rd party app on their device, then it forces them to use that app rather than the device’s native Contacts and Calendar apps. This was cumbersome and unacceptable.
We wanted to integrate Public Folders natively into a device’s core experience.
We only found a single product on the market which worked natively on a user’s device, called numbered. This initially seemed great, but further inspection revealed 2 terrible things:
This is terrible for so many reasons. What if a company is using Office 365? What if they don’t have their own Exchange server? What if an IT company has a server with 200 separate company Exchange accounts on it?
So, Outlook hits Public Folders natively, other devices hit a subfolder with duplicates of Public Folder data, and we’re supposed to trust that numbered will sync it all with no issues. This seemed overengineered.
Our search continued for an acceptable solution to recommend to our clients, but the inevitable conclusion was clear: the only way to give our clients the experience they deserved was to build it ourselves.
The idea was simple. We would build a dedicated web service to extend ActiveSync’s functionality to include Public Folder data. We would then authenticate against Exchange servers as individual users, which would limit access to Public Folders based on that user’s permissions. We then wrap everything in a subscription-based SaaS and start promoting it.
Immense was in a unique position to test the service with select IT clients, eventually get them on a monthly retainer for it, then ultimately offer it to the masses.
While backend developers were building a functional prototype, I pursued selling a magnificent product. The name pfsync came so naturally, and the remaining discovery snowballed from there.
pfsync would be an extension of the ActiveSync protocol, filling in the gaps to offer the user a truly native experience regardless of device. This bond with ActiveSync served as inspiration for pfsync’s identity, right down to the green color scheme.
I created something reminiscent of the ActiveSync logo from the Windows XP era, which I felt would resonate with this product’s primary userbase – passionate IT professionals who have likely been in this game for while.
There is no point in denying that I was inspired by GoDaddy’s sign in flydown. I wanted this single container to accomplish 3 specific goals:
The remainder of the page addresses each concern that potential customers may have, complete with simple graphics and honest copy.
Building a subscription-based web application is complicated, requiring everything from branding, to scalability, to credit card processing, to testing, to tech support, to…
This project is still being ironed out, but it’s been an educational ride so far.