Hi all, I would like to follow up on this discussion. Thank you, Arun and Devanshu, for supporting the idea.
To help move the discussion forward, I would like to make the proposal more concrete and proactively address some of the questions that may arise. 1. Why not use ofbiz-plugins? The ofbiz-plugins repository contains optional components that are installed and run as part of an OFBiz deployment. *A *PWA is different: - It has its own frontend build system and dependencies. - It is built and deployed independently from the OFBiz server. - It communicates with OFBiz through REST APIs. - It may be hosted on a different server or domain. - It may have its own release cadence and version compatibility requirements. Keeping standalone frontend applications inside ofbiz-plugins could blur the boundary between server-side OFBiz components and independently deployed API clients. The proposed separation would therefore be: - ofbiz-framework: Core framework, business applications, services and reusable APIs - ofbiz-plugins: Optional server-side OFBiz components - Proposed PWA repository: Standalone frontend applications consuming OFBiz APIs Any backend services or APIs required by a PWA would continue to be contributed to ofbiz-framework or, where appropriate, ofbiz-plugins. 2. Proposed repository name I propose the following name: apache/ofbiz-pwa The repository description could be: “Standalone Progressive Web Applications built on Apache OFBiz APIs.” 3. One repository containing multiple applications I propose initially maintaining all official OFBiz PWAs in a single repository. This would be a monorepo containing multiple independently deployable applications, not one large application containing every OFBiz workflow. An illustrative structure could be: apps/ production-run/ picking/ receiving/ packages/ api-client/ authentication/ ui/ shared-config/ docs/ Each application would have its own source code, dependencies, tests, build configuration and documentation. Shared packages should be introduced only when there is a genuine need across multiple applications. A single repository would make the applications easier to discover and would provide common contribution, testing and documentation practices. If the number or size of applications grows significantly, the community could later reconsider whether some applications should move into separate repositories. 4. Frontend framework I do not propose restricting the entire repository to a single frontend framework. Different applications may have different requirements, and contributors may have experience with different technologies. However, this should not mean that every application uses a different stack without a clear reason. Each application should be internally consistent, document its technology choices and reuse existing approaches or shared packages where practical. Common expectations around licensing, security, authentication, API usage, testing and documentation should apply across the repository regardless of framework. Shared packages such as API clients and authentication helpers could remain framework-neutral where practical, while UI packages may be specific to a particular framework. 5. Initial applications The Production Run and BOM Management PWAs could be the first application contributed to the repository. It would help us establish the initial repository structure, contribution guidelines, CI process and API compatibility conventions. Other manufacturing applications could be added incrementally as they become ready. I would especially appreciate feedback on the following: - Does ofbiz-pwa seem like the appropriate repository name? - Does maintaining multiple independent PWAs in one repository make sense initially? - Are the proposed boundaries between framework, plugins and PWAs clear? - Are there release, governance or contribution concerns we should address before creating the repository? If there is general agreement on the direction, we can summarize the decisions and coordinate with the PMC on the repository-creation process. Thanks, Divesh Dutta www.hotwaxsystems.com On Mon, Jul 13, 2026 at 9:57 AM Devanshu Vyas <[email protected]> wrote: > Hello Divesh, > > +1 for maintaining a separate repository for the PWA apps. > > Thanks & Regards, > Devanshu Vyas. > > > On Wed, Jul 8, 2026 at 2:59 PM Arun Patidar <[email protected]> > wrote: > > > Hi Divesh, > > > > +1 for creating a dedicated repository for Apache OFBiz-based PWA > > applications. > > > > > > Thanks, > > Arun Patidar > > > > > > On Wed, Jul 8, 2026 at 10:45 AM Divesh Dutta < > > [email protected]> > > wrote: > > > > > Hi all, > > > > > > As a follow-up to the discussion on the Production Run PWA, I would > like > > to > > > propose creating a dedicated repository for PWA applications built on > top > > > of Apache OFBiz. > > > > > > The idea is to keep the OFBiz framework, business applications, > plugins, > > > services, and REST APIs in their existing repositories, while > maintaining > > > frontend applications that consume those APIs in a separate repository. > > > > > > PWAs have their own development lifecycle, build tooling, dependencies, > > and > > > release cadence. > > > They are deployed independently from an OFBiz server and can be > developed > > > using different frontend technologies depending on the use case. > Keeping > > > them in a dedicated repository would allow the frontend ecosystem > around > > > OFBiz to evolve independently while keeping a clear separation between > > > backend and frontend concerns. > > > > > > Such a repository could eventually host applications such as: > > > > > > > > > - Manufacturing PWAs (Production Runs, BOM, Routing, MRP) > > > > > > > > > - Fulfillment PWAs (Picking, Packing) > > > > > > > > > - Inventory PWAs (Receiving, Cycle Counting) > > > > > > > > > - Other API-driven frontend applications built on Apache OFBiz > > > > > > > > > This would also provide a common place for sharing frontend libraries, > > API > > > clients, authentication helpers, UI components, and documentation where > > > appropriate. > > > > > > I am interested in hearing the community's thoughts on whether a > > dedicated > > > repository for Apache OFBiz PWAs would be a good long-term direction. > > > > > > Thanks > > > -- > > > Divesh Dutta > > > www.hotwaxsystems.com > > > > > >
