Oracle Low-Code Landscape: APEX, VBCS, and VBS Explained
The three primary options in the Oracle ecosystem for building modern user interfaces are Oracle APEX, Visual Builder (VBCS), and Visual Builder Studio (VBS). My goal in this post is to clarify how these tools fit into the enterprise application landscape and how they align with the Redwood Design System.
APEX
Oracle APEX (Application Express) is a low-code platform that resides natively within the Oracle Database. This makes it first choice for data-intensive applications.
Modernizing Oracle EBS: APEX is the tool for building responsive “bolt-on” modules. You can replace aging Oracle Forms with modern, intuitive interfaces without modifying the core EBS source code.
Custom Application Development: If your business logic lives in an Oracle Database, APEX is the fastest path to a secure, scalable app. It is ideal for replacing complex spreadsheets or building internal apps.
Data Visualization: APEX excels at creating interactive reports and complex dashboards that provide real-time insights directly from the source data.
VBCS (Visual Builder): The API-First Cloud Tool
Visual Builder is a cloud-native, JavaScript-based platform (leveraging Oracle JET) designed for applications that primarily consume REST APIs.
Extending Oracle Fusion Applications (SaaS): VBCS is the preferred tool for adding custom screens or workflows to Oracle Fusion (ERP, SCM, or HCM). It ensures your extensions maintain the look and feel of native Fusion pages.
Standalone Cloud Apps: For applications that need to orchestrate data across various cloud services and external APIs (beyond just Oracle), VBCS provides a robust, responsive environment.
Mobile Development: VBCS offers strong capabilities for creating Progressive Web Apps and hybrid mobile applications.
VBS (Visual Builder Studio): The DevOps Engine
VBS is more than just a development tool; it is Oracle’s comprehensive, cloud-based DevOps and lifecycle management platform.
Centralized Management: It provides Git repositories for version control of APEX, VBCS, Java, and other codebases.
CI/CD Pipelines: VBS automates the build, test, and deployment phases, ensuring consistent, error-free releases across your low-code projects.
Collaboration: It integrates issue tracking, agile boards, and code review tools to streamline team workflows.
The choice isn’t about which tool is “better,” but which is right for your architecture:
APEX: Choose this to maximize your Oracle Database investment and modernize EBS.
VBCS: Choose this to extend Oracle Fusion Cloud and build API-driven, cloud-native interfaces.
VBS: Use this as a foundational platform to manage the lifecycle of all Oracle development projects.
The Redwood Design
The Redwood Design System is Oracle’s modern UI/UX standard. While APEX allows you to incorporate Redwood-inspired themes (via Universal Theme), VBCS/VBS is built from the ground up to generate “Redwood-native” experiences.
By providing templates directly within these tools, Oracle ensures that customer extensions are visually similar to the core Fusion product. This “standardization” is what allows for Upgrade Safety. Unlike the heavy customizations of the EBS era, Fusion extensions are built as metadata layers and thus ensuring upgrade safety.
I imagine Oracle chose “Redwood” to resonate with their iconic Redwood Shores headquarters—creating a user experience as consistent and enduring as their Redwood Shores campus!
Phenomenal explanation! The way you broke it down with practical use cases made it so easy to understand. Huge thanks for the hard work you put into sharing this knowledge.