Demo Apps

The Demo Apps team in FlowFuse is where all of our demo apps live — a first-class asset alongside the PoV Workbook and the FlowFuse Trial Environment.

It is publicly available by design. A prospect can find a use case relevant to them and explore it from the front end; the Demo then becomes a walk through the backend of a use case they have already seen. Because each app is a different use case, the team as a whole shows that FlowFuse is truly a platform for solving many use cases — not a single tool.

Publishing criteria

Every app contributed to the Demo Apps team must meet these criteria:

  1. Hosted on the Demo Apps team. The app lives in the Demo Apps FlowFuse team, not a personal instance or a one-off environment.
  2. A PoV doc for the use case. Every contributed use case has a PoV workbook defined that showcases FlowFuse's value over Node-RED — what the platform adds beyond the flows themselves.
  3. Built with the app delivery methods. The app uses one or both of FlowFuse's app delivery methods.
  4. Conforms to an app pattern. The app follows one of the app patterns in the Application Guide — a hardware app or a software app.
  5. Uses the App Registry UI node. The app must use the App Registry UI node so it connects to the rest of the demo-apps ecosystem and is discoverable from the other demo apps.
  6. A built-in architecture page. The app must include an architecture page that is the PoV doc visualized on the front end of the app — so a prospect exploring the front end sees the same architecture the PoV describes.

Together these make each demo app self-describing: a prospect arrives at a use case, sees its architecture and value on the front end, and the sales Demo picks up from there in the backend.