Flower Docs
  • OpenFlower overview
    • The "Hello World" tutorial
  • Videos
    • OpenFlower in 100 seconds
  • 🆕Setup and run
    • Cloud & Private Cloud
    • Self-hosting
      • Access local database or API
      • Google Cloud Platform
      • Heroku
      • Migration from Openblocks
      • Update MongoDB Versions
      • OpenFlower Version Update
      • Traefik loadbalancer
      • SMTP Server
    • Security
  • 🏨Workspaces & Teamwork
    • Workspaces
    • Members and Groups
    • Permissions for Resources
    • OAuth
      • KeyCloak
      • Google
      • GitHub
      • Generic OAuth Provider
    • Query library
    • OpenFlower Marketplace
  • ✨Build Applications
    • Create a new App
      • Modules
      • Version and Release Management
    • App Editor
      • Visual Components
        • Common Component Settings
        • File upload
        • Charts and graphs
        • Image
        • Option lists
        • List View
        • Drawer
        • Google Maps
        • Table
        • Messages / Toast
        • Calendar
      • Date handling
      • Bulk Editing
      • Layers
      • Data selection & Javascript
      • Use Markdown
      • Keyboard shortcuts
    • App Navigation
    • App Interaction
      • Event handlers
    • Themes & Styling
      • Design an efficient and user-friendly form
      • Customize Styles
      • Component Styling Possibilities
  • 🚀Connect your Data
    • Data source basics
    • Data sources in OpenFlower
      • APIs as Datasource
        • REST API
        • GraphQL
        • Google Sheets
      • SQL Databases
        • MySQL
        • MariaDB
        • PostgreSQL
        • Microsoft SQL Server
        • Oracle
      • NoSQL Databases
        • MongoDB
        • CouchDB
        • DynamoDB
      • InMemory Databases
        • Redis
      • File Storages
        • S3 File Storage
      • BigData & OLAP
        • Big Query
        • Snowflake
        • ClickHouse
        • Elasticsearch
      • Websocket Datasource
    • Query basics
      • Bind Query Data to Components
      • Query library
  • 🪄Workflows
    • n8n Integration
  • 💫Business Logic in Apps
    • Write JavaScript
      • JavaScript query
      • Temporary state
      • Transformers
      • Data responder
      • Built-in JS functions
  • 🙌Publish Apps
    • Share an App
    • Publish an App
    • Embedd an App
      • Embed Apps in React
      • Native embed SDK
        • Build the SDK from Source
  • 🔥OpenFlower Extension
    • Opensource Contribution
      • Develop UI components for Apps
      • Develop Data Source Plugins
    • Use third-party libraries in Apps
      • Day.js Date handling
      • Import your own JavaScript Library
    • Custom component
    • OpenFlower Open REST API
Powered by GitBook
On this page
  1. Publish Apps

Embedd an App

PreviousPublish an AppNextEmbed Apps in React

Last updated 7 months ago

OpenFlower's ability to run apps natively within other web apps addresses many of the challenges businesses face in today's digital landscape. It offers a holistic solution that caters to diverse needs, from enhancing a company's online presence to providing specialized functionalities and ensuring a consistent user experience across platforms.

By allowing apps to run both in the browser and natively within other web apps, OpenFlower offers unparalleled flexibility. Developers and businesses can choose the best deployment method based on their specific needs, whether it's a standalone web app, an integrated module within a larger system, or a feature within a mobile app.

Content Management Systems (CMS) are widely used to manage and publish content on the web. With OpenFlower's SDK, businesses can directly integrate custom apps into their CMS platforms. This means they can enhance their websites with specialized functionalities without having to rely on third-party plugins or extensive custom development.

Integrating apps directly into websites or web apps ensures a seamless user experience. Users won't need to switch between different platforms or interfaces; everything they need is available within a single unified environment.

By leveraging OpenFlower's capabilities, businesses can reduce the costs associated with developing separate apps for different platforms. They can build once and deploy everywhere, whether it's on their website, CMS, or as a native mobile app.

The OpenFlower platform likely simplifies the app development process, enabling rapid prototyping and deployment. This speed is further enhanced when integrating apps directly into existing systems, as there's no need for extensive integration work.

One of the challenges businesses face is maintaining consistency across various platforms. With OpenFlower's approach, the same app can be deployed in multiple places, ensuring a consistent look, feel, and functionality.

By allowing apps to be published across various platforms, businesses can reach a broader audience. Whether users interact with the app on a company's website, within a web app, or on their mobile device, they get the same functionality and experience.

As technology evolves, the lines between web apps, websites, and native mobile apps are blurring. By adopting a platform like OpenFlower that bridges these gaps, businesses are better positioned to adapt to future technological shifts and user behavior changes.

After the blue section and before the FAQs you see (or not to see so obviously) a native embedded OpenFlower APP in a website. This is not an IFrame - but a native embedding, which creates the HTML elements of the OpenFlower App in the HTML hierarchy of the Website.

🙌