Why We Built QQQ
Use shared metadata and framework actions to reduce repetitive application work.
Updated for the QQQ 4.0 release review on September 10, 2026.
Repeated business application work
Business applications repeatedly need record forms, validation, data access, permissions, processes, and navigation. QQQ brings those concerns into a metadata-driven Java framework so application code can focus on the behavior specific to its domain.
Metadata with extension points
Tables and processes are explicit metadata objects. Typed actions and backend interfaces connect them to storage and execution. Java steps, customizers, and module interfaces remain available when the application needs behavior beyond the built-in paths.
The 4.0 boundary
The 4.0 work establishes the major-version API contract, consolidates middleware packages, removes deprecated APIs, and updates the first-party sample, starter, and QBit templates. The release status and migration guide records the actual availability and upgrade requirements.
The framework is one part of an application. Authentication configuration, business rules, deployment, recovery, and component licensing still need deliberate decisions. Start with the runnable sample and prove one workflow at a time.
