title: How to implement micro-frontends with dedicated Native Apps Team?
body: <p>(Asking for a friend ;-) )</p>
  
  <p>I'm working with Web (react) and Mobile (IOS, Android) teams. And I find that even with a microservices architecture we end up always doing duplicated work at the front end/client level. <strong>How to implement a microfrontends architecture that reduces duplication of frontend work but still provides a high quality experience for native clients?</strong></p>
  
  <h2>more context:</h2>
  
  <p>I've read Cam Jackson's <a href="https://martinfowler.com/articles/micro-frontends.html" rel="noreferrer">microfrontends article</a> and browsed <a href="https://micro-frontends.org/" rel="noreferrer">Michael Geers' microfrontends blog</a>. And I realise that we are closer to the Microservices pattern:</p>
  
  <p><a href="https://i.stack.imgur.com/M8SJX.png" rel="noreferrer"><img src="https://i.stack.imgur.com/M8SJX.png" alt="microservices arch"></a></p>
  
  <p>Than the Microfrontends one:</p>
  
  <p><a href="https://i.stack.imgur.com/yoUTQ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/yoUTQ.png" alt="microfrontends"></a></p>
  
  <p>This is mostly due to <a href="https://en.wikipedia.org/wiki/Conway%27s_law" rel="noreferrer">Conways law</a>. Even with dedicated teams that own a full product we still have dedicated teams only for IOS and Android native work. 
  Every new discrete piece of functionality, even with a clear bounded context at the API/Service level, ends up being fragmented into multiple different front end implementations of the same feature/component mostly to support Native Apps(that demand that every component that runs in the native apps has to be native). That got me thinking of implementing micro-frontends. 
  In an ideal world there wouldn't be any dedicated native apps teams and ios and android developers would integrate the corresponding product teams (as described in the image above). But that isn't an option.</p>
  
  <p>Given that our web app has the same look and feel as the mobile app. Is it a good idea to create a single web component as part of the microfrontend and consume it in the native apps with embedded webviews? Would that be considered a microfronends architecture? What are the drawbacks from that approach?</p>
  
  <p>That way the same team that builds the responsive web component will be responsible for that feature end to end. And leave only the core user journeys and native specific features (like AR and barcode scanning) to run as native components.</p>