Skip to main content

Transforming Domino into a Social Collaboration Platform, Part 3 - Teaching an Old Dog To Do New Tricks

Transforming Domino into a Social Collaboration Platform, Part 1 - Where Do We Begin?
Transforming Domino into a Social Collaboration Platform, Part 2A - Experimentation
Transforming Domino into a Social Collaboration Platform, Part 2B - Experimentation

So now that we had all the tools and capabilities to create our social collaboration tool, what should be build? We wanted to build a SMB solution similar to IBM Connections or Yammer, a small business solution that utilized the power of enterprise technology.

So we were all set with our mighty tools in hand and created our new social collaboration solution.  Like all application development, how a designer/developer thinks is not how users thinks. We developed our first version in early 2013 and users shot it down!!! How there they? But the true set in. 

From our discussions with our clients and watching how they worked, they were not interested in a general social collaboration tool, but a focused solution that provided only the tools that they needed for their tasks in hand.  Effective communities or groups were no more than 20 to 50 individuals and in most cases under 10 not hundreds or thousands.  Therefore, we had no interested in recreating a general social collaboration tool.

Instead, our goal was to build a community-centric solution not an individual focused solution, a purposeful social collaboration solution that allowed users to manage focused tasks for which communities were created.  As a result, things like activities are tracked only within the context of the community not the individual.  This seems anti-socially compared with Facebook and others, but the reality is that unless there is a purpose that drives the need for social collaboration, users will most likely not use it.  In a large enterprise environment, there are other driving factors that define things differently so solutions like IBM Connections are more appropriate.

So what were the important things that clients wanted?
  • Create and share content in a community/group environment
  • Allow members with the appropriate access to create, publish, and organize content within folders environment
  • Ability to create open or restricted communities
  • Ability for members with the appropriate access to comment on published content within the community
  • Ability to control email notification when content is published
  • Ability to create restricted sub-communities within a community and allow only certain community members access
  • Control who had the ability to create communities so that community creep would not occur.
  • Ability to find and locate content with a community
  • Ability for community members to send messages to each other in a private environment.
  • Regardless of whether the community member was an internal or external user, they had the same capabilities and features when assigned the appropriate rights
  • Ability to tailor the solution with different add-on capabilities controlled by the community manager
  • Full management of the solution using a web interface
  • Keep their content and information secure and private
  • Desktop and mobile device access.
  • Extensible API
  • Simple, easy to user interface
  • Minimalistic environment to reduce the clutter
  • Activity-based trigger workflow
  • Ability to incorporate the solution into other applications

So back to the drawing board we went. After another year of redevelopment and many redesigns and architecture changes, we now have version 2!  It has something new, something borrowed, and something old, iPhora Foundation + Domino/XWork + Integrated Business Framework.  iPhora Touch 2 is finally here.

Next time,

Transforming Domino into a Social Collaboration Platform, Part 4 - The Results So Far


Anonymous said…
I think you made a right decision creating a community focused solution. You need to define your niche.

Sadly to see that Notes's Teamroom is not being enhanced nowadays

Popular posts from this blog

The iPhora Journey - Part 8 - Flow-based Programming

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

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select

The iPhora Journey - Part 3 - Creating an Integrated UI Framework

The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework There are many ways to create the user interface (UI) for a web application. The HTML page could be created on the server and then pushed out. It could be static with the data generated on the page by the server with JavaScript, providing a more dynamic experience, or the server could generate new HTML content to update portions of the web page. XPages or PHP are good examples of this. Another method is to have the web page partially generated by the server and have JavaScript build the rest of the HTML by pulling data from the server via an API. This is the approach used in the Single Page Application (SPA) model. In all cases, it is still dependent on the web server technology being using.  As mentioned previously in this blog, XPages is dependent on complete integration between form and document, which e