Edit history

Earlier versions of Web-Container-Based/Embedded Apps (Bot-like Extensions), newest first.

Current version | Edited by Rex
Changes
https://feedback.fluxer.com/p/929Removed: ### Notes (optional)Removed: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing discussions and didn't find a duplicate.Removed:
Show

Web-Container-Based/Embedded Apps (Bot-like Extensions)

Problem

Disclaimer: English isn't my main language. Currently we have Bots to cusomize our community experience like in Discord. But Bots are restricted to just posting stuff without great UI representation. Like that many Bots are a bit hard to use or use external Dashoboards as UI Helper.

Proposed solution

Introduce “Embedded Apps” (similar to bots) that run inside a web container. As a developer, I could build a lightweight web app that runs within this container. Initially, the existing API would cover most use cases, and over time you could provide predefined UI components (e.g. user panels, navigation elements) to simplify development and ensure consistency. As a community owner, I could create an “App Channel” that renders the web container and displays a selected app directly within the channel. I’ve also seen the suggestion about adding new channel types. With embedded apps, many of those use cases could be implemented by the community itself as web apps. Later, the most popular or performance-critical features could be integrated natively for better optimization. https://feedback.fluxer.com/p/929
Edited by Rex
Changes
I’ve also seen the suggestion about adding new channel types. With embedded apps, many of those use cases could be implemented by the community itself as web apps. Later, the most popular or performance-critical features could be integrated natively for better optimization.Removed: https://github.com/orgs/fluxerapp/discussions/321Added: https://feedback.fluxer.com/p/929### Notes (optional)
Show

Web-Container-Based/Embedded Apps (Bot-like Extensions)

Problem

Disclaimer: English isn't my main language. Currently we have Bots to cusomize our community experience like in Discord. But Bots are restricted to just posting stuff without great UI representation. Like that many Bots are a bit hard to use or use external Dashoboards as UI Helper.

Proposed solution

Introduce “Embedded Apps” (similar to bots) that run inside a web container. As a developer, I could build a lightweight web app that runs within this container. Initially, the existing API would cover most use cases, and over time you could provide predefined UI components (e.g. user panels, navigation elements) to simplify development and ensure consistency. As a community owner, I could create an “App Channel” that renders the web container and displays a selected app directly within the channel. I’ve also seen the suggestion about adding new channel types. With embedded apps, many of those use cases could be implemented by the community itself as web apps. Later, the most popular or performance-critical features could be integrated natively for better optimization. https://feedback.fluxer.com/p/929

Notes (optional)

No response

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.
Original by Rex
Show

Web-Container-Based/Embedded Apps (Bot-like Extensions)

Problem

Disclaimer: English isn't my main language. Currently we have Bots to cusomize our community experience like in Discord. But Bots are restricted to just posting stuff without great UI representation. Like that many Bots are a bit hard to use or use external Dashoboards as UI Helper.

Proposed solution

Introduce “Embedded Apps” (similar to bots) that run inside a web container. As a developer, I could build a lightweight web app that runs within this container. Initially, the existing API would cover most use cases, and over time you could provide predefined UI components (e.g. user panels, navigation elements) to simplify development and ensure consistency. As a community owner, I could create an “App Channel” that renders the web container and displays a selected app directly within the channel. I’ve also seen the suggestion about adding new channel types. With embedded apps, many of those use cases could be implemented by the community itself as web apps. Later, the most popular or performance-critical features could be integrated natively for better optimization. https://github.com/orgs/fluxerapp/discussions/321

Notes (optional)

No response

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.