๐—•๐—น๐—ผ๐—ด ๐Ÿฐ -๐—ข๐—ฟ๐—ฎ๐—ฐ๐—น๐—ฒ ๐—”๐—ฃ๐—˜๐—ซ ๐Ÿฎ๐Ÿฒ.๐Ÿญ: ๐—™๐—ฟ๐—ผ๐—บ ๐—–๐—ผ๐—ฑ๐—ฒ ๐˜๐—ผ ๐—œ๐—ป๐˜๐—ฒ๐—ป๐˜ – ๐—ง๐—ต๐—ฒ ๐—™๐˜‚๐˜๐˜‚๐—ฟ๐—ฒ ๐—ผ๐—ณ ๐——๐—ฒ๐˜ƒ๐—ฒ๐—น๐—ผ๐—ฝ๐—บ๐—ฒ๐—ป๐˜

As part of my #OracleAIWorld London tour series, this blog captures key insights from the Oracle APEX session led by Simon Hunt.

๐—ช๐—ต๐—ฎ๐˜ ๐—ถ๐—ณ ๐—ฏ๐˜‚๐—ถ๐—น๐—ฑ๐—ถ๐—ป๐—ด ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐˜€ ๐—ป๐—ผ ๐—น๐—ผ๐—ป๐—ด๐—ฒ๐—ฟ ๐˜€๐˜๐—ฎ๐—ฟ๐˜๐—ฒ๐—ฑ ๐˜„๐—ถ๐˜๐—ต ๐—ฐ๐—ผ๐—ฑ๐—ฒ, ๐—ฏ๐˜‚๐˜ ๐˜„๐—ถ๐˜๐—ต ๐—ถ๐—ป๐˜๐—ฒ๐—ป๐˜?
Instead of focusing on how to build something, we express what we want and the system begins to take shape around that intent. With #OracleAPEX, this is already becoming real.

You describe your data model, and schemas are generated. Describe your application, and pages begin to form. Describe your query in plain English, and SQL is created.

A big part of enabling this shift is #APEXLang.
It is human-readable, defines applications as files, integrates naturally with version control and something AI can understand and generate.
That changes the role of development itself. Applications are no longer just written. They are interpreted, evolved, and co-created with AI.

Another key concept was ๐—ฆ๐—ฝ๐—ฒ๐—ฐ ๐˜๐—ผ ๐—–๐—ผ๐—ฑ๐—ฒ.
You start with requirements even a simple structured document. From there, schema definitions are generated, a blueprint is created, and that flows directly into an application.

The distance between idea and execution is shrinking and so the gap between business and engineering begins to disappear.

For smaller applications, you can move quickly from intent to application. But enterprise systems need more than speed – they need governance, structure, and repeatability.
Spec-to-code introduces that balance, ensuring AI-driven development remains controlled and reliable.

Another critical piece is ๐—ฐ๐—ผ๐—ป๐˜๐—ฒ๐˜…๐˜. With RAG, AI pulls directly from enterprise data – SQL queries, functions, and structured datasets. This makes responses accurate, relevant, and continuously up to date.
๐Ÿ‘‰ AI moves from guessingโ€ฆ to knowing.

One of the most impactful demonstrations was around ๐—ป๐—ฎ๐˜๐˜‚๐—ฟ๐—ฎ๐—น ๐—น๐—ฎ๐—ป๐—ด๐˜‚๐—ฎ๐—ด๐—ฒ ๐—ฟ๐—ฒ๐—ฝ๐—ผ๐—ฟ๐˜๐—ถ๐—ป๐—ด. You simply say: โ€œgroup by region and show totalsโ€ and the report updates instantly.
No menus. No SQL. No dependency.
AI understands intent, while APEX ensures structured and reliable execution.

Another important shift is how ๐—ฐ๐—ผ๐—ป๐˜ƒ๐—ฒ๐—ฟ๐˜€๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐—ฎ๐—น ๐—”๐—œย embedded directly into applications. AI is no longer an add-on. It becomes part of how applications work.

At a platform level, ๐—ข๐—ฟ๐—ฎ๐—ฐ๐—น๐—ฒ ๐——๐—ฎ๐˜๐—ฎ๐—ฏ๐—ฎ๐˜€๐—ฒ ๐Ÿฎ๐Ÿฒ๐—”๐—œย plays a key role bringing AI into the database with vector search and annotations, enabling smarter, context-aware apps.

AI is no longer something we add – itโ€™s being woven into how systems are built, closing the gap between business and technology.
๐Ÿ‘‰ Oracle APEX is leading this shift moving development from writing code to expressing intent, from effortโ€ฆ to expression.

Looking forward to the release and canโ€™t wait to start building applications in this new way.

Leave a comment

Let’s connect

Archives

Recent Posts