From b5bde1b70c4f395cad90ad9d35f137e591eb4a70 Mon Sep 17 00:00:00 2001 From: MarianRapahel <73583313+MarianRaphael@users.noreply.github.com> Date: Mon, 10 Jul 2023 11:58:01 +0200 Subject: [PATCH] Q3/4 Plan --- src/handbook/product/plan.md | 81 ++++++++++++++------------------ src/handbook/product/strategy.md | 2 +- 2 files changed, 37 insertions(+), 46 deletions(-) diff --git a/src/handbook/product/plan.md b/src/handbook/product/plan.md index d1d20b30f5..ea4298330d 100644 --- a/src/handbook/product/plan.md +++ b/src/handbook/product/plan.md @@ -3,9 +3,7 @@ navTitle: Plan --- # Product Plan -## Background - -Our [Product Strategy](./strategy.md) sets out 4 pillars that our product work is focussed around. +Our [Product Strategy](./strategy.md) sets out 5 pillars that our product work is focussed around. ## Planning @@ -17,58 +15,51 @@ We use three project boards to plan and track our work. The detailed planning process can be found [here](../development/releases/planning.md) -## Principles +## High Level Strategy Implementation for Q3/Q4 2023 + +Our high-level strategy implementation plan serves as a broad outline of the key focus areas for each strategy pillar we will be tackling over the course of the next six months. The points mentioned here are just an overview, and for more granular details on each initiative, we recommend referring to our roadmap. + +The progress bars presented adjacent to each category are rough estimates, offering an initial glance at the projected level of completion for each category's feature set. These are not precise calculations, nor do they represent the current status of each strategy pillar. It's important to note that at the start of every new product plan cycle, these progress bars reset to a lower level, reflecting the onset of new development and implementation stages. For detailed updates on the actual status of each project, please keep an eye on our [release blog posts](https://flowforge.com/blog/releases/). + +### Advancing Enterprise-Readiness +![](https://geps.dev/progress/30) + +- [High availability & Scalability](https://github.com/flowforge/flowforge/issues/1678) + +- Improve DevOps Pipelines + +- [VPN support for Instances](https://github.com/flowforge/flowforge/issues/1570) + +- [Introduce Value Layer Model](https://github.com/flowforge/flowforge/issues/2167) + +- [Implement Organization as addtional hierachy level](https://github.com/flowforge/flowforge/issues/2338) + -#### Convention over configuration +### Node-RED Deployments at the Edge (Device Management) +![](https://geps.dev/progress/0) -We want the default configuration of FlowForge to be the best user experience for -the majority of users. +- [Device can be managed indepedently from Instances on Apllication level](https://github.com/flowforge/flowforge/issues/2334) -Every new option we add to the platform, whether for an administrator or end-user, -represents another choice they have to deal with. This increases the cognitive burden -of using the platform and can have a negative impact on user experience. It also -increases the engineering cost to develop and test features where there are many -possible combinations to consider. +- [Grouped Device Deployments](https://github.com/flowforge/flowforge/issues/1509) -For every feature we add that has some scope for configuration, our starting point -in the design is to **identify the right configuration and hard-code it in**. +### Enhanced Integration Capabilities +![](https://geps.dev/progress/0) -This removes the choice from users' hands and minds. It does not prevent us from -choosing to make it more configurable in the future if user-feedback/business-needs -requires it. +- [Official Support for slected Node-RED nodes](https://github.com/flowforge/flowforge/issues/1901) -Where there is a strong case to expose an option to the end user, it should still -be provided with a sensible default value where possible that removes the need -for the user to set it themselves. This gives users the ability to customise -the option if/when they are ready to. But the default value should be the right -answer for most users. +- [Costum NPM Module registry](https://github.com/flowforge/flowforge/issues/217) -Some configuration options cannot be defaulted - the user has to do make a choice. -For example, setting up email on the platform. The UX around these options must -be carefully considered to help the user get to the right choice with a minimum -of effort. +- [Visibilty of different palette catalogues in Node-RED](https://github.com/node-red/node-red/issues/4057) -Node-RED provides a lot of configuration options. We should not assume they are all -candidates to be exposed to FlowForge users. For example, options to customise the -editor appearance should be reserved options that we determine the right values for -to ensure a consistent user experience across FlowForge instances. -Options that have an impact on the behaviour of flows will need to be considered -on a case-by-case basis. But the starting point should always be to pick the right -default and only expose to the user if absolutely necessary. +### Data Visualization & Analytics +![](https://geps.dev/progress/5) +- Version 1.0 of the Node-RED Dashboard successor, with a comparable feature set like [Node-RED Dashboard](https://github.com/node-red/node-red-dashboard) and the possibility to extend features for Enterprise and Analystics scenarios. -See also: [Convention over Configuration on Wikipedia](https://en.wikipedia.org/wiki/Convention_over_configuration). +### User-Friendly Low-Code Approach +![](https://geps.dev/progress/0) -## Open Source & Enterprise +- [Immersive Node-RED experience](https://github.com/flowforge/flowforge/issues/2246) -We offer a number of ways that users can run the FlowForge product, we will -always offer an open source version that has the core features. Features that -offer higher business value or permit users to share across larger groups will -be offered as part of our paid enterprise proposition. Our managed FlowForge -offering is public and will generally include all features that are available -but may not offer certain features such as SSO where integration is required -between the platform and an enterprise. We will offer customers the ability to -have a dedicated managed instance if thats is a deployment model they require. -A more detailed breakdown of the pricing and split between our Open Source and -Enterprise Editions is on the [pricing principles](pricing.md) page. +- First out of the box IIoT Solutions template (e.g. ANDON for Node-RED) \ No newline at end of file diff --git a/src/handbook/product/strategy.md b/src/handbook/product/strategy.md index a7b4b60b97..9fc1421e6c 100644 --- a/src/handbook/product/strategy.md +++ b/src/handbook/product/strategy.md @@ -32,7 +32,7 @@ FlowForge's commitment to a low-programming approach via Node-RED, complemented ### User-Friendly Low-Code Approach -FlowForge is built upon the strength of Node-RED's user-friendly, low-code approach, positioning us well within the IIoT market. We believe Node-RED provides the best foundation, but we're committed to not only utilizing its existing capabilities but also contributing to its upstream improvement. By refining Node-RED and adding enhancements, we aim to create an even more intuitive, powerful, and accessible platform. This will enable end-users to swiftly and intuitively build applications, reducing the dependency on expert programmers and democratizing IIoT application development. +FlowForge is built upon the strength of Node-RED's user-friendly, low-code approach, positioning us well within the IIoT market. We believe Node-RED provides the best foundation, but we're committed to not only utilizing its existing capabilities but also contributing to its upstream improvement. By refining Node-RED and adding enhancements, we aim to create an even more intuitive, powerful, and accessible platform. This will enable end-users to swiftly and intuitively build applications and reducing the dependency on expert programmers. ----