The Unhappiness with Yammer: API Changes and Authentication Frustrations

ARE YOU A DEVELOPER who relies on Yammer for enterprise communication? Have you faced challenges due to frequent and unexpected changes in their APIs? In this article, we explore some common frustrations experienced by app developers who integrate with Yammer, with a focus on the issue of API changes and authentication. By sharing our personal experiences, we hope to offer insights that might help you navigate similar challenges more effectively.

1. API Changes and Their Impact

One of the most frustrating aspects of working with Yammer is the tendency for the platform to make subtle yet impactful changes to their APIs. These changes can cause disruptions in the functionality of integrated apps, leading to several issues for both new and existing users. For instance, in a recent case, Yammer altered its authentication flow to rely more heavily on cookies. This change had significant implications:

New users were unable to log in to the app, despite the app itself being functional. This created a barrier to entry for potential users and could hinder the app's growth.

Existing users, however, whose authentication tokens were still valid, were able to continue using the app. This was a temporary relief but highlighted the need for a more robust solution.

The change also complicated the process for users who wished to add a second account within the app. This was particularly frustrating for power users who required multiple accounts for different business units or departments.

2. Workarounds and Fixes

Despite the challenges, our team has worked diligently to address these issues. Our current version of the app now includes the following solutions to mitigate the negative impacts of the API changes:

For New Users: We have implemented a mechanism that checks for and automatically refreshes expired authentication tokens. This ensures that new users can log in without any hassle.

For Existing Users: We have added a feature that allows users to easily add a second account by linking it to their existing account. This simplifies the process for those who require multiple accounts.

However, it's important to note that these fixes have been necessary because of the changes made by Yammer, and it's likely that similar issues will arise again in the future. The frequency and unpredictability of these changes can be quite disruptive to app development and user experience.

3. Lessons and Recommendations

Based on our experiences, here are a few recommendations for other developers using Yammer in their apps:

Regular Monitoring: Stay vigilant and regularly check for updates to the Yammer API documentation. This can help you anticipate and prepare for potential changes.

Graceful Degradation: Design your app to handle unexpected changes gracefully. Implement error handling mechanisms that can catch and manage API breaks without completely crashing the app.

Users First: Communicate clearly with your users about any changes or issues that arise. Providing transparent and timely communication can help maintain user trust and loyalty.

While Yammer's changes may cause immediate frustration, taking a proactive and user-centered approach can help mitigate these issues and ensure a smoother experience for everyone involved.