<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Miguel Pérez Colom</title>
    <description>The latest articles on DEV Community by Miguel Pérez Colom (@miguel_prezcolom_34723e).</description>
    <link>https://dev.to/miguel_prezcolom_34723e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2598551%2Faa157b1f-4693-4fa1-956c-64b346e4eb4f.jpg</url>
      <title>DEV Community: Miguel Pérez Colom</title>
      <link>https://dev.to/miguel_prezcolom_34723e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/miguel_prezcolom_34723e"/>
    <language>en</language>
    <item>
      <title>We recorded a 14-chapter video series. It turned out to be our best end-to-end test.</title>
      <dc:creator>Miguel Pérez Colom</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:37:02 +0000</pubDate>
      <link>https://dev.to/miguel_prezcolom_34723e/we-recorded-a-14-chapter-video-series-it-turned-out-to-be-our-best-end-to-end-test-2jbn</link>
      <guid>https://dev.to/miguel_prezcolom_34723e/we-recorded-a-14-chapter-video-series-it-turned-out-to-be-our-best-end-to-end-test-2jbn</guid>
      <description>&lt;p&gt;We set one rule for the EventConductor video series — nothing on screen may be drawn by hand — and that rule turned every chapter into a test of the real product. Recording 14 short chapters surfaced more than a dozen real defects, including one that wasn't a bug in the code at all, but in the story our examples told.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rule: nothing drawn by hand
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://eventconductor.mateu.io" rel="noopener noreferrer"&gt;EventConductor&lt;/a&gt; is an open-source engine for business processes in Java/Spring: you declare the steps in YAML, and it handles retries, compensation, waiting for people, timers and operations. It does a lot, and a single promo video can't show it. So we made &lt;em&gt;EventConductor in N minutes&lt;/em&gt;: 14 chapters of 2–4 minutes, one aspect each.&lt;/p&gt;

&lt;p&gt;The series had three production rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Every screen is the product running.&lt;/strong&gt; The admin console is recorded with Playwright; terminals show real commands with their real output; the IDE is real VS Code with the published extension.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every snippet on screen compiles&lt;/strong&gt; and is the code that produces the screen next to it. A script checks each chapter's excerpts against the repository before rendering.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Claims match the product.&lt;/strong&gt; Opt-in features are called opt-in, stand-ins (a fake hotel, a demo language model) are labelled on screen, and nothing unreleased is shown as available.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The consequence we didn't plan for: if a chapter can't be recorded, something is broken. Every chapter became an end-to-end test that a human would actually watch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the camera caught
&lt;/h2&gt;

&lt;p&gt;The recordings found real defects in the engine, the console and the IDE plugin. None of them showed up in our test suites, because each needed a person looking at the screen to notice.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Found while recording&lt;/th&gt;
&lt;th&gt;Where&lt;/th&gt;
&lt;th&gt;What was wrong&lt;/th&gt;
&lt;th&gt;Fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;An XOR join after a CHOICE&lt;/td&gt;
&lt;td&gt;Engine&lt;/td&gt;
&lt;td&gt;A step fed by a CHOICE ignored its other incoming links; the process finished silently, skipping everything after the join&lt;/td&gt;
&lt;td&gt;Every link judged on its own rule&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;compensateLosers&lt;/code&gt; race&lt;/td&gt;
&lt;td&gt;Engine&lt;/td&gt;
&lt;td&gt;If both branches finished before the join, both were winners and nothing was undone&lt;/td&gt;
&lt;td&gt;Exactly one winner, first to finish&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Start right after boot&lt;/td&gt;
&lt;td&gt;Engine&lt;/td&gt;
&lt;td&gt;The REST API answered before definitions were imported, so a start returned 404&lt;/td&gt;
&lt;td&gt;Definitions load before the web server opens&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Graph editor&lt;/td&gt;
&lt;td&gt;VS Code plugin&lt;/td&gt;
&lt;td&gt;One drag on the canvas rewrote the whole YAML file, dropping comments&lt;/td&gt;
&lt;td&gt;Targeted, comment-preserving edits&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Migrate dialog&lt;/td&gt;
&lt;td&gt;Console&lt;/td&gt;
&lt;td&gt;Taller than the screen: the mandatory Reason and the Preview button were below the fold&lt;/td&gt;
&lt;td&gt;Dialogs fit 720 px; dry run shown inline&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Task inbox&lt;/td&gt;
&lt;td&gt;Console&lt;/td&gt;
&lt;td&gt;The Run button sat past the right edge of a 1920 px page&lt;/td&gt;
&lt;td&gt;Action column first&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Operations tab&lt;/td&gt;
&lt;td&gt;Console&lt;/td&gt;
&lt;td&gt;It only appeared after a manual page reload&lt;/td&gt;
&lt;td&gt;Appears live with the first operation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Process page redraw&lt;/td&gt;
&lt;td&gt;Console&lt;/td&gt;
&lt;td&gt;After an operation the back arrow vanished and buttons reordered&lt;/td&gt;
&lt;td&gt;Redraw renders exactly like a fresh load&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Help text&lt;/td&gt;
&lt;td&gt;Console&lt;/td&gt;
&lt;td&gt;"Recorded with your name" — but without a login the audit says &lt;em&gt;anonymous&lt;/em&gt;
&lt;/td&gt;
&lt;td&gt;Copy that is always true&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compensation rows, attempts, timeout routes&lt;/td&gt;
&lt;td&gt;Console&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;item 0&lt;/code&gt; instead of &lt;em&gt;Room 101&lt;/em&gt;; retries invisible; a timeout route drawn as a &lt;code&gt;false&lt;/code&gt; guard&lt;/td&gt;
&lt;td&gt;Labels, an Attempts column, a real timeout edge&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two more were in the shared UI framework underneath, &lt;a href="https://github.com/miguelperezcolom/mateu" rel="noopener noreferrer"&gt;Mateu&lt;/a&gt;: a page-layout cache that leaked between apps on the same port (fixed and released) and icon-only buttons with no accessible name (filed).&lt;/p&gt;

&lt;h2&gt;
  
  
  The worst bug was in the story
&lt;/h2&gt;

&lt;p&gt;Our flagship example is a hotel booking: approve, book each room, tell the guest. To show sagas, room 900 is always sold out — and the process then cancelled the two rooms it had already booked. Automatically. That is how compensation demos usually go.&lt;/p&gt;

&lt;p&gt;Watching it on screen, it was obviously wrong. No hotel cancels a guest's confirmed rooms because a third one is full. It tells the guest, offers an alternative, and cancels only if the guest says so. An example that undoes a customer's booking on its own doesn't sell a saga engine; it makes people afraid of one.&lt;/p&gt;

&lt;p&gt;So the example changed, and the engine gained what it needed to tell the realistic story:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The rooms step keeps what it booked when one room fails (&lt;code&gt;onIterationFailure: continue&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The process fetches alternatives from the hotel and asks the guest.&lt;/li&gt;
&lt;li&gt;It waits for the answer with a deadline. No answer means a reminder, then the front desk — never a cancellation.&lt;/li&gt;
&lt;li&gt;Only when the guest (or the front desk) cancels does an &lt;code&gt;END&lt;/code&gt; with the new &lt;code&gt;compensate: true&lt;/code&gt; undo every booked room, newest first.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;cancelled-by-guest&lt;/span&gt;
  &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;END&lt;/span&gt;
  &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Cancelled by the guest&lt;/span&gt;
  &lt;span class="na"&gt;compensate&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;   &lt;span class="c1"&gt;# undo what was booked — because the guest decided
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Compensation is the mechanism; who decides to trigger it is your business rule. Automatic all-or-nothing compensation is still there for what really is one technical unit. The same review later caught a payment-deadline example that released an unpaid room on its own; it now goes to the front desk too.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the pipeline works
&lt;/h2&gt;

&lt;p&gt;Everything lives in the repository under &lt;code&gt;media/video-series&lt;/code&gt;, and one command renders a chapter. It is deterministic, so a script change re-renders the chapter.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Narration first.&lt;/strong&gt; Each chapter is a script of scenes with English narration. The length of each scene comes from its narration, not the other way round.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Local, free voice.&lt;/strong&gt; &lt;a href="https://huggingface.co/hexgrad/Kokoro-82M" rel="noopener noreferrer"&gt;Kokoro&lt;/a&gt; runs offline with one fixed voice for the whole series. Subtitles (&lt;code&gt;.srt&lt;/code&gt;) are generated from the same timings, in English and Spanish.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Frame-by-frame capture.&lt;/strong&gt; Playwright drives the real console with the page clock paused (&lt;code&gt;clock.install&lt;/code&gt; + &lt;code&gt;clock.pauseAt&lt;/code&gt;), CSS animations slowed through CDP, and one screenshot per frame at 1920×1080. ffmpeg assembles at 30 fps. No screen recorder, no dropped frames, no timing luck.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Title and diagram scenes&lt;/strong&gt; are plain HTML, rendered the same way.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Source checks.&lt;/strong&gt; Before rendering, a script verifies that every code excerpt still matches the file it claims to come from.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contact sheets.&lt;/strong&gt; Every master is reviewed as a grid of stills before upload: cut-off content, unreadable text, blank frames, and anything that contradicts the product.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The apps run offline against a locally built engine, so what is filmed is exactly the code in the repository.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you make product videos
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ban mock-ups.&lt;/strong&gt; A drawn screen can't fail. A real one fails exactly where your users would trip.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat "can't record it" as a bug report.&lt;/strong&gt; We never worked around the product in a video; we fixed the product and re-recorded.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read your examples as a customer would.&lt;/strong&gt; Our worst finding wasn't in the code: it was a demo that did something no business would accept.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make it reproducible.&lt;/strong&gt; A paused clock and frame-by-frame capture turn a video into a build artefact: change a line, re-render, compare.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Say what's a stand-in.&lt;/strong&gt; A label on screen ("fake hotel: local stand-in", "MCP server: opt-in") costs nothing and keeps the video honest.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most of the time on this series went into fixing the product, not into making videos. Two releases (2.42.0 and 2.42.1) shipped what the camera found.&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch and try it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The series: &lt;a href="https://www.youtube.com/playlist?list=PLJ1h3znLgDAY" rel="noopener noreferrer"&gt;EventConductor in N minutes&lt;/a&gt; — 14 chapters, English, subtitles in English and Spanish&lt;/li&gt;
&lt;li&gt;Start with &lt;a href="https://youtu.be/4gyfGdC5dJ8" rel="noopener noreferrer"&gt;Chapter 1: EventConductor in 3 minutes&lt;/a&gt; or the saga chapter, &lt;a href="https://youtu.be/hp2AEy1vulI" rel="noopener noreferrer"&gt;When a room can't be booked: the guest decides&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Docs and the hands-on workshop: &lt;a href="https://eventconductor.mateu.io" rel="noopener noreferrer"&gt;eventconductor.mateu.io&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Code (open source, MIT): &lt;a href="https://github.com/miguelperezcolom/eventconductor" rel="noopener noreferrer"&gt;github.com/miguelperezcolom/eventconductor&lt;/a&gt; — the video pipeline is in &lt;code&gt;media/video-series&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Latest release: &lt;a href="https://github.com/miguelperezcolom/eventconductor/releases/tag/v2.42.1" rel="noopener noreferrer"&gt;v2.42.1&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>java</category>
      <category>opensource</category>
      <category>testing</category>
      <category>springboot</category>
    </item>
    <item>
      <title>Mateu 3.0 is out: declare a business UI once, run it everywhere</title>
      <dc:creator>Miguel Pérez Colom</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:25:24 +0000</pubDate>
      <link>https://dev.to/miguel_prezcolom_34723e/mateu-30-is-out-declare-a-business-ui-once-run-it-everywhere-21om</link>
      <guid>https://dev.to/miguel_prezcolom_34723e/mateu-30-is-out-declare-a-business-ui-once-run-it-everywhere-21om</guid>
      <description>&lt;p&gt;&lt;em&gt;Open source, Apache 2.0. Write the screens in Java, C# or Python, or as YAML, and Mateu renders forms, CRUDs, wizards, dashboards and the whole app shell on the web, the phone, the desktop and inside Oracle Visual Builder.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;Most business applications end up as two applications. There is the backend, with the model, the rules and the validation. Then there is the frontend, which repeats the model, repeats the validation and adds a build, a framework and a second team to keep it alive. For a back office with forty screens, that second application is most of the work.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mateu.io" rel="noopener noreferrer"&gt;Mateu&lt;/a&gt; removes it. You declare what a screen contains, its fields, rules and actions, and Mateu derives the screen. Version 3.0.0 was released on 15 November 2026 and is now the latest release on GitHub. It is the first release with a stable public API.&lt;/p&gt;

&lt;p&gt;Mateu in three minutes:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/KKYsYGO1LvQ" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  What it looks like
&lt;/h2&gt;

&lt;p&gt;A record, and a class that says "this is a CRUD over it":&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;record&lt;/span&gt; &lt;span class="nc"&gt;Product&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="nd"&gt;@EditableOnlyWhenCreating&lt;/span&gt; &lt;span class="nd"&gt;@NotEmpty&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nd"&gt;@NotEmpty&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nd"&gt;@Min&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nd"&gt;@Stereotype&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;FieldStereotype&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;money&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="kt"&gt;double&lt;/span&gt; &lt;span class="n"&gt;price&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nd"&gt;@NotNull&lt;/span&gt; &lt;span class="nc"&gt;ProductStatus&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;implements&lt;/span&gt; &lt;span class="nc"&gt;Identifiable&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

  &lt;span class="nd"&gt;@Override&lt;/span&gt;
  &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt; &lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="k"&gt;null&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isBlank&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"New product"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nd"&gt;@Title&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Products"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;Products&lt;/span&gt; &lt;span class="k"&gt;extends&lt;/span&gt; &lt;span class="nc"&gt;AutoCrud&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Product&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

  &lt;span class="nd"&gt;@Override&lt;/span&gt;
  &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="nc"&gt;CrudStore&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Product&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;store&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nc"&gt;ProductStore&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="no"&gt;INSTANCE&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;ProductStore&lt;/code&gt; is your data access, an implementation of the &lt;code&gt;CrudStore&amp;lt;Product&amp;gt;&lt;/code&gt; interface (in-memory in the starter, your database in a real app). Add one field to the app shell, &lt;code&gt;@Menu Products products;&lt;/code&gt;, and you have:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a listing at &lt;code&gt;/products&lt;/code&gt; with a search box, filters, sorting and paging;&lt;/li&gt;
&lt;li&gt;a create form at &lt;code&gt;/products/new&lt;/code&gt;, a record page at &lt;code&gt;/products/{id}&lt;/code&gt; and an editor at &lt;code&gt;/products/{id}/edit&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;validation from the Bean Validation annotations, in the browser while the user types and again on the server before anything is saved;&lt;/li&gt;
&lt;li&gt;delete with selection, an app shell with its menu, and deep links that work on reload.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is no frontend code in the project. Episode 2 of the video series goes &lt;a href="https://youtu.be/XgKnmx_5qFM" rel="noopener noreferrer"&gt;from a record to a full CRUD&lt;/a&gt; step by step.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F908yh1ywbzxiz7tyd9bc.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F908yh1ywbzxiz7tyd9bc.jpeg" alt="A listing in the museums demo: search, saved views, column chooser, selection, paging" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;AutoCrud&lt;/code&gt; is one of several archetypes. A class that extends &lt;code&gt;Wizard&lt;/code&gt; becomes a multi-step process, &lt;code&gt;Dashboard&lt;/code&gt; turns &lt;code&gt;MetricCard&lt;/code&gt; fields into a KPI band and &lt;code&gt;@Panel&lt;/code&gt; fields into tiles, and &lt;code&gt;Welcome&lt;/code&gt;, &lt;code&gt;ItemOverview&lt;/code&gt;, &lt;code&gt;Foldout&lt;/code&gt;, &lt;code&gt;CollectionDetail&lt;/code&gt;, &lt;code&gt;CalendarPage&lt;/code&gt; and others cover the rest of a back office. When an archetype does not fit, you build the screen from components yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  The same in C#, Python, or no code at all
&lt;/h2&gt;

&lt;p&gt;Mateu has three server implementations that speak the same wire protocol: Java, C# on ASP.NET Core and Python on FastAPI. The C# and Python versions of the screen above are a &lt;code&gt;Crud&amp;lt;Product&amp;gt;&lt;/code&gt; class with four small methods (fetch, get, save, delete). A shared conformance corpus of screens holds the three to the same JSON, so a renderer cannot tell which language is behind it. &lt;a href="https://youtu.be/fYmefU55Nhc" rel="noopener noreferrer"&gt;Episode 6&lt;/a&gt; shows the three side by side.&lt;/p&gt;

&lt;p&gt;You can also skip code entirely. A screen can be data, in a YAML file under &lt;code&gt;specs/ui&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Listing&lt;/span&gt;
&lt;span class="na"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Products&lt;/span&gt;
&lt;span class="na"&gt;searchable&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
&lt;span class="na"&gt;rowsSource&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;ref&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;products&lt;/span&gt;            &lt;span class="c1"&gt;# an endpoint named once in sources.yaml
&lt;/span&gt;&lt;span class="na"&gt;columns&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;type:&lt;/span&gt; &lt;span class="s"&gt;GridColumn&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;id:&lt;/span&gt; &lt;span class="s"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;label:&lt;/span&gt; &lt;span class="s"&gt;Name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;sortable:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;type:&lt;/span&gt; &lt;span class="s"&gt;GridColumn&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;id:&lt;/span&gt; &lt;span class="s"&gt;price&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;label:&lt;/span&gt; &lt;span class="s"&gt;Price&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;stereotype:&lt;/span&gt; &lt;span class="s"&gt;money&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;sortable:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s"&gt;type:&lt;/span&gt; &lt;span class="s"&gt;GridColumn&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;id:&lt;/span&gt; &lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;label:&lt;/span&gt; &lt;span class="s"&gt;Status&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;dataType:&lt;/span&gt; &lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;sortable:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;products&lt;/code&gt; source can carry sample rows, so a UI works before its API exists. The YAML can be written by hand or by the visual editor that ships with the Mateu plugins for IntelliJ and VS Code. It can be served by a Spring Boot app, or exported as a static bundle and put on a CDN with no backend at all; the bundle calls your REST APIs directly from the browser. The public &lt;a href="https://museums.ec1.mateu.io" rel="noopener noreferrer"&gt;museums demo&lt;/a&gt; is written this way: every screen is YAML. &lt;a href="https://youtu.be/cruaUhcb4yo" rel="noopener noreferrer"&gt;Episode 3&lt;/a&gt; builds one from scratch.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsa2ocn348rctpcfidi0i.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsa2ocn348rctpcfidi0i.jpeg" alt="The home page of the museums demo, declared in YAML" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  One declaration, several places to run it
&lt;/h2&gt;

&lt;p&gt;The declaration says what the screen is; each renderer decides how to draw it. With 3.0 the same screen runs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;on the web&lt;/strong&gt;, with Vaadin components or with Oracle Redwood (JET and Spectra, loaded from Oracle's CDN);&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;in the Mateu phone app&lt;/strong&gt; for iOS (on the App Store) and Android;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;in the Mateu desktop app&lt;/strong&gt; for macOS, Windows and Linux;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;inside your own Oracle Visual Builder app&lt;/strong&gt;, with one element: &lt;code&gt;&amp;lt;mateu-ui&amp;gt;&lt;/code&gt;. I wrote about that one separately: &lt;a href="https://dev.to/miguel_prezcolom_34723e/one-element-a-whole-app-mateu-inside-oracle-visual-builder-4nm6"&gt;One element, a whole app: Mateu inside Oracle Visual Builder&lt;/a&gt;;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;for AI agents&lt;/strong&gt;, over MCP (more on that below).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here is the same record page of the museums demo, drawn by the Vaadin renderer and by the Redwood renderer, from the same YAML and the same server:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzyxf6s1oj90ht1udc0lq.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzyxf6s1oj90ht1udc0lq.jpeg" alt="An artwork page on the Vaadin renderer" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fss9b8821et3mg71htny1.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fss9b8821et3mg71htny1.jpeg" alt="The same artwork page on the Oracle Redwood renderer" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The phone and desktop apps work like a browser for Mateu UIs: you add a UI by its address or a QR code, and its screens draw as native controls. If you need your own branded app instead, both can be built bound to a single UI. &lt;a href="https://youtu.be/4GMoMzi2g6s" rel="noopener noreferrer"&gt;Episode 4&lt;/a&gt; shows one screen on every surface, and &lt;a href="https://youtu.be/nbi6jTDPXC0" rel="noopener noreferrer"&gt;episode 13&lt;/a&gt; shows it inside Visual Builder.&lt;/p&gt;

&lt;h2&gt;
  
  
  Page templates, after Oracle Redwood
&lt;/h2&gt;

&lt;p&gt;Oracle's Redwood design system describes a set of page templates for business apps, and Mateu follows them: welcome page, dashboard, hero search, smart search, collection-detail, general overview, item overview, foldout, guided process, calendar, to-do list, data management and more. In Java you get them by extending an archetype or annotating a page; in YAML a form names its &lt;code&gt;template:&lt;/code&gt;. On the Redwood renderer they become Oracle's own Spectra templates; on the other renderers, Mateu's version of the same layout.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzk8hweu0yfedfax8o58l.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzk8hweu0yfedfax8o58l.jpeg" alt="A dashboard: MetricCards become the KPI band, panels become tiles" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can browse every archetype, template and component, live, in the &lt;a href="https://explorer.mateu.io" rel="noopener noreferrer"&gt;Mateu Explorer&lt;/a&gt;. &lt;a href="https://youtu.be/NwYVkYrT33Y" rel="noopener noreferrer"&gt;Episode 5&lt;/a&gt; walks through the templates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Backends you already run
&lt;/h2&gt;

&lt;p&gt;On the Java side Mateu has adapters for Spring MVC, Spring WebFlux, Quarkus, Micronaut and Helidon MP. An annotation processor generates the controllers at compile time, and the &lt;code&gt;@UI&lt;/code&gt; classes themselves can live in a module that depends only on Mateu's API jar, with no framework in it. Every adapter runs the same parity test suite. On .NET it is an ASP.NET Core package, on Python a FastAPI one.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI agents, when you switch them on
&lt;/h2&gt;

&lt;p&gt;Each Mateu app can expose an MCP server. It is off unless you enable it. When it is on, an agent can list the screens, read them, fill fields and run actions under the same identity and access rules as a user, and it can also write new screens as YAML: the server validates and previews them, and saves them only in development mode. A second, separate switch lets a user pair one open browser tab with an agent, so the agent can push a screen to that tab and to nothing else. The desktop app has its own MCP server for the window that is open, also off by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  Secure and boring in production
&lt;/h2&gt;

&lt;p&gt;Mateu does not authenticate anyone: the caller is whoever your framework (Spring Security, Quarkus, ASP.NET Core and so on) says it is. What Mateu does with that identity is strict by default:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;an action runs only if the screen declared it; anything else is refused;&lt;/li&gt;
&lt;li&gt;fields a user may not see are left out of what the server sends, and fields they may not change are dropped from what it accepts;&lt;/li&gt;
&lt;li&gt;CRUD writes are checked on the server, not only hidden in the UI;&lt;/li&gt;
&lt;li&gt;CORS and MCP are off until you configure them;&lt;/li&gt;
&lt;li&gt;an unexpected error shows the user a reference number, never a stack trace, and the details go to your log under that number.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://youtu.be/lQO07luSlGY" rel="noopener noreferrer"&gt;Episode 7&lt;/a&gt; covers identity and permissions. For day-to-day robustness, the web renderers handle slow and dropped connections (busy controls, safe retries of reads, a clear message instead of a dead screen), the phone app has an experimental offline queue for actions that can wait, there is an accessibility conformance report against WCAG 2.2 in the docs, requests produce OpenTelemetry spans and metrics, and a user on an old tab after a deploy gets a "this app has been updated" notice instead of a confusing error.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Mateu fits
&lt;/h2&gt;

&lt;p&gt;Each piece of this exists somewhere else, and some of it is done very well:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Model-driven UIs from your classes&lt;/strong&gt;: OpenXava and Jmix turn Java entities into business screens, and Django's admin does it for Python models.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low-code platforms&lt;/strong&gt;: Oracle APEX, Visual Builder, Retool or Appsmith build business apps fast, inside their own tool and platform.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Server-driven UI&lt;/strong&gt;: large companies build it in-house so their native apps draw screens described by the server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Java-only web UIs&lt;/strong&gt;: Vaadin lets you build the web UI in Java, component by component.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What Mateu adds is getting all of it from one declaration: written as code in Java, C# or Python or as YAML data; drawn on the web with Vaadin or Oracle Redwood, in native phone and desktop apps and inside Oracle Visual Builder; operable by AI agents under the same rules as a person; deployable as static files when there is no backend. Open source, on the stack you already run.&lt;/p&gt;

&lt;h2&gt;
  
  
  A stable 3.x
&lt;/h2&gt;

&lt;p&gt;From 3.0.0 on, the public Java API keeps binary compatibility across the 3.x line, and every build checks it. The .NET and Python APIs are pinned by their own tests, and the wire protocol stays compatible within the major version. Features still finding their final shape are marked &lt;code&gt;@Experimental&lt;/code&gt;, so you can see what is covered by that promise and what is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting started
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Java&lt;/strong&gt;: create a project from IntelliJ (&lt;em&gt;File › New › Project › Mateu&lt;/em&gt;), from VS Code (&lt;em&gt;Mateu: New Project…&lt;/em&gt;), or with the Maven archetype &lt;code&gt;io.mateu:mateu-archetype&lt;/code&gt;. All three generate from the same starters. Versions come from the BOM, &lt;code&gt;io.mateu:mateu-bom:3.0.0&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;C#&lt;/strong&gt;: the &lt;code&gt;Mateu.*&lt;/code&gt; packages on NuGet, version 3.0.0.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Python&lt;/strong&gt;: &lt;code&gt;pip install mateu-ui&lt;/code&gt; (3.0.0).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Learn by typing&lt;/strong&gt;: the repository has a half-day hands-on workshop in &lt;code&gt;workshop/&lt;/code&gt;, with Java, C# and Python tracks, covering renderers, tests, YAML, AI agents and sign-in.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Docs and quickstarts are at &lt;a href="https://mateu.io" rel="noopener noreferrer"&gt;mateu.io&lt;/a&gt;, the code is at &lt;a href="https://github.com/miguelperezcolom/mateu" rel="noopener noreferrer"&gt;github.com/miguelperezcolom/mateu&lt;/a&gt;, and the release notes are at &lt;a href="https://github.com/miguelperezcolom/mateu/releases/tag/v3.0.0" rel="noopener noreferrer"&gt;Mateu v3.0.0&lt;/a&gt;. Mateu is Apache 2.0.&lt;/p&gt;

&lt;p&gt;If you build back offices, try it on one screen you already have and see how much of it is left to write. Issues and questions are welcome on GitHub.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://medium.com/@miguelperezcolom/mateu-3-0-is-out-declare-a-business-ui-once-run-it-everywhere-82874c42ef2e" rel="noopener noreferrer"&gt;Medium&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>java</category>
      <category>dotnet</category>
      <category>python</category>
      <category>opensource</category>
    </item>
    <item>
      <title>One element, a whole app: Mateu inside Oracle Visual Builder</title>
      <dc:creator>Miguel Pérez Colom</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:24:01 +0000</pubDate>
      <link>https://dev.to/miguel_prezcolom_34723e/one-element-a-whole-app-mateu-inside-oracle-visual-builder-4nm6</link>
      <guid>https://dev.to/miguel_prezcolom_34723e/one-element-a-whole-app-mateu-inside-oracle-visual-builder-4nm6</guid>
      <description>&lt;p&gt;&lt;em&gt;Replace your Visual Builder app's root page with a single component and a complete business app runs inside it — header, menu, listings, record pages, forms, validation — drawn with your app's own Redwood. No frontend code, no iframe.&lt;/em&gt;&lt;/p&gt;




&lt;p&gt;If you build apps in Oracle Visual Builder Studio, you know the trade-off. The page designer is excellent for laying out a page, and every non-trivial business screen still means variables, action chains, service connections and a fair amount of wiring. Multiply that by the forty screens of a back office and the wiring becomes the project.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://mateu.io" rel="noopener noreferrer"&gt;Mateu&lt;/a&gt; takes the other route. It is a model-driven UI system: you declare what a screen &lt;em&gt;is&lt;/em&gt; — a record, its fields and rules, the actions on it — and Mateu renders it. The declaration can be code (Java, C# or Python) or data (YAML). A listing with search, sorting and filters, record pages, create and edit forms, validation in the browser and again on the server: all of it comes from the declaration. No frontend code.&lt;/p&gt;

&lt;p&gt;With Mateu 3.0.0, released on 15 November 2026, those screens can live &lt;strong&gt;inside your Visual Builder app&lt;/strong&gt; — and the shortest way to show it is one line of HTML.&lt;/p&gt;

&lt;h2&gt;
  
  
  The whole app, in one element
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;mateu-ui&lt;/span&gt; &lt;span class="na"&gt;base-url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://museums.ec1.mateu.io"&lt;/span&gt; &lt;span class="na"&gt;shell&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"true"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/mateu-ui&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Put that on your VB app's root page, instead of whatever was there, and press Preview. What you get is not one screen but the whole app the backend declares: its header, its logo, its menu, and every screen behind the menu — with navigation staying inside the component.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgg4e4td3pelmlz0gudx7.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgg4e4td3pelmlz0gudx7.jpeg" alt="The museums app running inside a Visual Builder preview: its own header and menu" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The app in the picture is a public Mateu demo: a museum collection (the Met, SMK and the Cleveland Museum of Art). It is a Mateu app running on a Java server (Spring Boot), and its screens are declared in YAML. Nothing about the component depends on that: the same UI could be declared in Java, C# or Python and served by Spring Boot, Quarkus, Micronaut, Helidon, ASP.NET Core or FastAPI. The component only speaks Mateu's wire protocol.&lt;/p&gt;

&lt;p&gt;Open &lt;em&gt;Explore › Artworks&lt;/em&gt; and the listing is there — search, sortable columns, saved views, column chooser, selection, a "New artwork" action:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcoh64bnfc7nks57vjbm1.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcoh64bnfc7nks57vjbm1.jpeg" alt="The Artworks listing, inside Visual Builder" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Click a row and the record opens inside the component, with its tabs and previous/next navigation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch it: from an empty workspace to a running app
&lt;/h2&gt;

&lt;p&gt;The whole walkthrough is episode 13 of the "Mateu in N minutes" series:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/nbi6jTDPXC0" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Step by step
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Create the web app.&lt;/strong&gt; In a Visual Builder Studio workspace, create a web application as usual (the default template is fine).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Download the component.&lt;/strong&gt; Every Mateu release carries a zip, &lt;code&gt;mateu-ui-&amp;lt;version&amp;gt;.zip&lt;/code&gt;. For this one, take it from the &lt;a href="https://github.com/miguelperezcolom/mateu/releases/tag/v3.0.0" rel="noopener noreferrer"&gt;v3.0.0 release&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Import it.&lt;/strong&gt; In the Components palette, under &lt;em&gt;Custom&lt;/em&gt; (or &lt;em&gt;Integration&lt;/em&gt;), choose &lt;strong&gt;Import Web Component&lt;/strong&gt;, and drop the zip. You can also do it from the navigator: &lt;em&gt;Resources › components › Import&lt;/em&gt;. The component then appears in the palette as &lt;strong&gt;Mateu UI&lt;/strong&gt;, under &lt;strong&gt;Integration&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdffqrrr6vor6i5z0cvs3.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdffqrrr6vor6i5z0cvs3.jpeg" alt="Mateu UI in the Components palette, under Integration" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Replace the root page's content with the one element.&lt;/strong&gt; Open your app's root page (the shell page) in the Page Designer, clear what it has, and drop &lt;em&gt;Mateu UI&lt;/em&gt; on it — or write the element in the Code view.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Set the Backend base URL.&lt;/strong&gt; In the Properties panel, set &lt;em&gt;Backend base URL&lt;/em&gt; to the Mateu backend (&lt;code&gt;https://museums.ec1.mateu.io&lt;/code&gt; for the demo) and &lt;em&gt;App shell&lt;/em&gt; to &lt;code&gt;true&lt;/code&gt;. Until the base URL is set the component has nothing to load, so an empty box on the canvas is expected. Once it is set, the designer canvas already shows the app:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhrxmx22yov0paas9srcj.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhrxmx22yov0paas9srcj.jpeg" alt="The designer canvas showing the museums app, with the component's properties" width="800" height="414"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Preview.&lt;/strong&gt; Run the app. The museums header and menu are there, and every screen works.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Publishing&lt;/strong&gt; is the usual Visual Builder publish: an environment pointing at your Visual Builder instance, then &lt;em&gt;Publish&lt;/em&gt;. The only thing the Mateu backend needs is to allow your app's origin for cross-origin calls (&lt;code&gt;mateu.cors.allowed-origins=https://&amp;lt;your-instance&amp;gt;.oraclecloud.com&lt;/code&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Second use case: one Mateu screen in a page you own
&lt;/h2&gt;

&lt;p&gt;You don't have to hand over the whole app. Leave &lt;code&gt;shell&lt;/code&gt; off and give the component a &lt;code&gt;route&lt;/code&gt;, and it shows that one screen inside a page of your own flow:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;mateu-ui&lt;/span&gt; &lt;span class="na"&gt;base-url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://museums.ec1.mateu.io"&lt;/span&gt; &lt;span class="na"&gt;route&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"artworks"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/mateu-ui&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your VB app keeps its shell, its navigation and its URL; Mateu fills one area of one page. Click a row and the record opens inside the component.&lt;/p&gt;

&lt;h2&gt;
  
  
  Talking to the rest of your page
&lt;/h2&gt;

&lt;p&gt;The component is a regular JET citizen:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Properties.&lt;/strong&gt; &lt;code&gt;route&lt;/code&gt; is written back as the user navigates, so you can bind it to a page variable with a binding expression (double curly braces). &lt;code&gt;params&lt;/code&gt; fills a route's placeholders, &lt;code&gt;initial-state&lt;/code&gt; pre-fills a form, &lt;code&gt;app-context&lt;/code&gt; passes the company, fiscal year or whatever context your app keeps (changing it reloads the screen), and &lt;code&gt;navigation="host"&lt;/code&gt; hands every navigation to your page instead of doing it inside the component.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Events&lt;/strong&gt; your action chains can listen to: &lt;code&gt;mateuNavigate&lt;/code&gt; (cancelable — send the user to another page of your flow instead), &lt;code&gt;mateuTitle&lt;/code&gt;, &lt;code&gt;mateuAction&lt;/code&gt;, &lt;code&gt;mateuMessage&lt;/code&gt;, &lt;code&gt;mateuReady&lt;/code&gt; and &lt;code&gt;mateuError&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Identity.&lt;/strong&gt; The component calls the Mateu backend from the browser, so it passes the identity your app already has: &lt;code&gt;token&lt;/code&gt; for a bearer token, or &lt;code&gt;headers-provider&lt;/code&gt; — a page function asked on every request — for a token that rotates; &lt;code&gt;with-credentials&lt;/code&gt; when the backend shares your SSO cookie. On a 401 the component fires a cancelable &lt;code&gt;mateu-session-expired&lt;/code&gt; event so your app can refresh the token and retry.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The fine print
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One &lt;code&gt;&amp;lt;mateu-ui&amp;gt;&lt;/code&gt; per page.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;With &lt;code&gt;shell="true"&lt;/code&gt; the menu is drawn as a top band. The backend's user menu and notifications are not drawn inside the component yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It is not an iframe and brings no second runtime.&lt;/strong&gt; It runs on your app's own JET, Redwood theme and Spectra components — which is why a Mateu screen looks like the rest of your app.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Licensing, plainly.&lt;/strong&gt; The zip contains only Mateu code, under Apache 2.0. Inside Visual Builder it runs on your app's JET, Redwood and Spectra, under your own Oracle agreement. Nothing of Oracle's is redistributed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why it matters
&lt;/h2&gt;

&lt;p&gt;The screen is declared once. The same declaration that fills your Visual Builder page also runs as a standalone web app, in Mateu's phone app and in its desktop app, and an AI agent can describe and operate it over MCP. Your Visual Builder app keeps doing what it does best — the shell, the flows, the integration with the rest of Oracle Cloud — and the forty business screens stop being forty projects.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Get started:&lt;/strong&gt; &lt;a href="https://mateu.io" rel="noopener noreferrer"&gt;mateu.io&lt;/a&gt; · the component: &lt;em&gt;Design systems › Oracle Redwood&lt;/em&gt; in the docs · release: &lt;a href="https://github.com/miguelperezcolom/mateu/releases/tag/v3.0.0" rel="noopener noreferrer"&gt;Mateu v3.0.0&lt;/a&gt; · source: &lt;a href="https://github.com/miguelperezcolom/mateu" rel="noopener noreferrer"&gt;github.com/miguelperezcolom/mateu&lt;/a&gt; · videos: the "Mateu in N minutes" playlist on YouTube.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://medium.com/@miguelperezcolom/one-element-a-whole-app-mateu-inside-oracle-visual-builder-971e29c8d0fe" rel="noopener noreferrer"&gt;Medium&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>oracle</category>
      <category>java</category>
      <category>lowcode</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
