Currently I am prototyping a web-based, collaborative approach which provides basic building blocks and allows the end-user to create and modify their own application in realtime as they use it through a plugin system, using a simple and configurable input/output system to configure data flow between plugins/panes/components.
My hypothesis is that a more modular approach is the next emergent layer of productivity. A collaborative workflow synced between multiple devices and users in realtime, with an in-app repository for new components and workflow layouts. Think foobar2k but for productivity. Google Apps on crack, where users can modify the application itself in realtime in addition to context.
The problem with other solutions is they solve one thing really well and then rely on a plugin system to fill the gaps. I'd rather see what an approach where each component does something simple but is a greater part of a larger, bespoke workflow. bash-utils for GUI-oriented, networked productivity. Currently, we have to rely on non-realtime, multi-application workflows with rigid, non-transparent data pipelines. Creating a cohesive workflow requires significant specialization, while also locking you in to a specific, non-malleable workflow dictated by app developers.
Comments
Currently I am prototyping a web-based, collaborative approach which provides basic building blocks and allows the end-user to create and modify their own application in realtime as they use it through a plugin system, using a simple and configurable input/output system to configure data flow between plugins/panes/components.
My hypothesis is that a more modular approach is the next emergent layer of productivity. A collaborative workflow synced between multiple devices and users in realtime, with an in-app repository for new components and workflow layouts. Think foobar2k but for productivity. Google Apps on crack, where users can modify the application itself in realtime in addition to context.
The problem with other solutions is they solve one thing really well and then rely on a plugin system to fill the gaps. I'd rather see what an approach where each component does something simple but is a greater part of a larger, bespoke workflow. bash-utils for GUI-oriented, networked productivity. Currently, we have to rely on non-realtime, multi-application workflows with rigid, non-transparent data pipelines. Creating a cohesive workflow requires significant specialization, while also locking you in to a specific, non-malleable workflow dictated by app developers.
Hoping it turns out to be a useful paradigm.