<?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: Andrea</title>
    <description>The latest articles on DEV Community by Andrea (@andreatrygit).</description>
    <link>https://dev.to/andreatrygit</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F421539%2Fabd18fbd-d96c-4da2-a7fd-916efbbb145f.jpeg</url>
      <title>DEV Community: Andrea</title>
      <link>https://dev.to/andreatrygit</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/andreatrygit"/>
    <language>en</language>
    <item>
      <title>Is this horrible?</title>
      <dc:creator>Andrea</dc:creator>
      <pubDate>Tue, 03 Nov 2020 12:43:39 +0000</pubDate>
      <link>https://dev.to/andreatrygit/is-this-horrible-3phi</link>
      <guid>https://dev.to/andreatrygit/is-this-horrible-3phi</guid>
      <description>&lt;p&gt;Hi, I'm exploring a new idea about UI dev. &lt;br&gt;
Here my cent about microfrontends.&lt;br&gt;
I am explicitly calling for comments on this before eventually commencing writing the code (probably in Svelte).&lt;br&gt;
The question is:&lt;br&gt;
What if one deploys single ui widgets to different pages (a là microfrontend but in an extreme fashion) and uses iframes to compose a page?&lt;br&gt;
Single components would communicate through postMessage API in a message passing style.&lt;br&gt;
Code would be (again) wisely decoupled from presentation (modern ui framework did the opposite) and dev people would also gain a total decomposition of the deployment: no need to rebuild/redeploy huge parts (a whole SPA, some pages in SSR,...) when you just touched a button onclick.&lt;br&gt;
Regarding decoupling, I plan to deploy, as said, simple atomic ui widgets on different pages.&lt;br&gt;
Think to them as this one: button.example.com or in the same spirit int-input.example.com&lt;br&gt;
Each one would be parameterizable through url query like so: &lt;br&gt;
int-input.example.com/?min=5&amp;amp;max=10&lt;br&gt;
This way the component itself would receive kind of "URL props".&lt;br&gt;
Then, each conponent would emit and respond to predefined messages sent to and coming from sendMessage API through the containing iframe.&lt;br&gt;
It is just in the parent iframe that you would wire the logic in the form of a finite state machine, i.e. mapping state therein defined to actions and reactions to messages.&lt;/p&gt;

&lt;p&gt;That's it, please comment on this.&lt;br&gt;
Technically harsh comments are welcome!&lt;/p&gt;

&lt;p&gt;Thanks to Dev-ers!&lt;/p&gt;

</description>
      <category>ux</category>
      <category>microfrontend</category>
      <category>iframe</category>
    </item>
  </channel>
</rss>
