We just released the latest version of tibbr, private social networking, for our android and ios native mobile applications.
In this release we have introduced new functionality, which continues our mantra of “create not convert.” In short, this means our engineering and user experience teams conceptualize, design and create each feature in our native apps specifically for the mobile experience instead of converting browser functionality or experiences.
So why is this important? Allow me to take a step back and paint a complete picture. tibbr is sharply focused on delivering real business value. We design every element of the platform to make employees more productive in every dimension, from sharing knowledge to discovering experts and information. Considering that 56% of tibbr usage in our customer base actually occurs in our native mobile applications, we have to continually innovate to deliver on one of our key goals: getting work done faster.
For example, as part of the latest release we introduced some experience improvements around the way we handle tibbr posts that include photos attachments:
● Photo attachment thumbnails are pre-fetched, so that they are already loaded when a user arrives at the post.
● A user can like a photo or tap to view comments related to the photo right from the photo preview, then one-touch download to save the photo to the device—cutting out extra steps or taps between scrolling and preview modes.
Zoning into one example it might all seem simple. However, when you expand this approach across the entire mobile experience for every interaction you realize the time and effort that our engineering and user experience teams are embarking on to deliver on our goal.
To see all the items that have been included in this latest release please visit the respective Google Play Store or Apple App store.
