@ZucchiniZe and I had a conversation about Big Room's features today.
This was the design we have currently settled on.
You can see the left hand side, a traditional chat platform... While on the right there is blank space for the "Management" tools
We have decided to make Big Room more of a community platform, than a singular application. The left hand side is going to be a place for organisations to customise heavily. Some may use it for service monitoring, some may use it for pretty graphs... Some might use it for everything! It is a section which allows organisations to fulfil their own needs. It is practically impossible for a single rigid product to fit each and every organisations targets, so we are being flexible and fluid.
Extensions should be modular and defined programmatically. Behaviour should be constructed over a JSON/RPC API.
@ZucchiniZe and I had a conversation about Big Room's features today.
This was the design we have currently settled on.
You can see the left hand side, a traditional chat platform... While on the right there is blank space for the "Management" tools
We have decided to make Big Room more of a community platform, than a singular application. The left hand side is going to be a place for organisations to customise heavily. Some may use it for service monitoring, some may use it for pretty graphs... Some might use it for everything! It is a section which allows organisations to fulfil their own needs. It is practically impossible for a single rigid product to fit each and every organisations targets, so we are being flexible and fluid.
Extensions should be modular and defined programmatically. Behaviour should be constructed over a JSON/RPC API.