The moment this becomes acute: a developer joins a team that runs OFBiz, Tobago, or another Apache framework and spends their first two weeks just figuring out how the project is structured and where things live in the interface — not because the system is fundamentally complex, but because the UI gives no guidance. Multiple complaints specifically name new learners struggling with project structure and how data flows from the database to the screen. This isn't a documentation problem; the Apache docs exist. It's a contextual guidance problem — nobody is explaining what to do next inside the interface where the user actually is.
The gap persists because Apache projects don't have UX teams, and the people who know the system well enough to write good walkthroughs are the same engineers who've already internalized it and no longer feel the pain. The companies deploying these frameworks have no clean way to build interactive onboarding without forking the UI source — so they resort to PDF guides, screen recordings, and Confluence pages that go stale the moment anything changes.
What's missing is a way for internal teams to author and maintain step-by-step in-app guidance that overlays on any web-based Apache UI — OFBiz, Tobago, Cocoon — without modifying the underlying application. The walkthroughs need to survive minor UI changes without breaking, which means they have to be resilient to DOM shifts, not brittle CSS selectors.
This is a business and not a feature because every company running these tools has ongoing staff turnover. The need to onboard someone new to OFBiz or Tobago doesn't happen once — it happens every time someone new joins the team, every time a module is upgraded and the UI shifts, and every time a department expands to a new part of the system. The alternative is a senior developer spending days shadowing a junior through the interface, which is a real and recurring cost.
What to build
Build a browser-extension-delivered walkthrough authoring tool that lets internal teams record step-by-step UI flows on any self-hosted web application, stores those flows with resilient element targeting (text content and ARIA labels rather than CSS selectors), and replays them as contextual overlays for new users — with an admin dashboard showing where users drop off.
Where to start
Start with OFBiz specifically and offer pre-built walkthrough templates for the five most common OFBiz workflows (creating a sales order, receiving inventory, generating an invoice, adding a customer, running an AR report) — so the first customer gets value on day one without authoring anything, which eliminates the cold-start problem.
The hard part
Element targeting that survives UI updates across Apache framework upgrades is genuinely hard — CSS-selector-based tools break constantly, and building a targeting strategy robust enough that customers don't churn when OFBiz updates its templates requires significant early investment in the targeting engine before the product feels reliable.
How it makes money
Annual subscription per company, priced by number of walkthrough authors (not viewers), since the authoring seat is the scarce resource and viewer usage is unlimited — expansion revenue comes from teams adding authors as they build out more internal training content.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Java Web Frameworks.
More ideas in Java Web Frameworks