Dynamico

<p align="center"> <img width="150" src="https://user-images.githubusercontent.com/6004537/58460249-e6fb7600-8135-11e9-80c7-49fa170cbc2e.png" /> </p> <h1 align="center">Dynamico</h1> <div align="center">

A remote (web-like) code push work-flow for continuous delivery of specific features native or web.

</div>

Try it out

• Getting Started
• Tutorial

What Dynamico does best

<p align="center"> <img src="https://user-images.githubusercontent.com/13674505/71442794-21e77b80-2710-11ea-85e5-9cd4c4d836d9.png" /> </p>

Why?

<!-- In the growing web of today, when frameworks are constantly changing and it seems hard to keep track of the new trends and -->

Native & Web

• Client and server framework agnostic

  • Client core and server driver are plugable by design - choose your own frontend framework (or go vanilla) and your own server and components storage

• Blazing fast feature delivery

  • Continuous Delivery for features
  • Avoid publishing new app version for every feature
  • Allow micro-frontend workflow
  • Remove the hassle of knowing the internals of the host application

• Reduces bundle size

  • Faster app build time
  • Simpler app build proccess
  • Shorter stores app reviews (Mobile only :pray:) learn more here

• De-monolith-ization 🤯

  • Team independent feature development, test & release
  • Seperates core main features from lazy-loaded dynamic flows
  • Eliminates pull-requests rebase push race
  • Reduces repository size and complexity
  • Share components across multiple apps

• Specific feature version management

  • Caches locally and updates immidiatly
  • Smart host dependencies resolution

When?

Dynamico allows a remote code push work-flow for continuous delivery of specific features.

Native

• Whenever you're using a js based library to create a native app (e.g React Native, Electron, etc..)

Web

• When you want to avoid a monolith
• When many developers work in a single repository and need to iterate fast

Future thoughts

• Micro-frontends framework
• JSON based configuration that your PM can write and decide what components to show
• Config based feature rollout and A/B testing

Roadmap

• Analytics

Native stores complience

Apple appstore

• This framework, when used properly, complies with section 3.3.2 of the developer agreement and actually encourages safer patterns than the alternatives:

Except as set forth in the next paragraph, an Application may not download or install executable code. Interpreted code may be downloaded toan Application but only so long as such code: (a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store, (b) does not create a store or storefront for other code or applications, and (c) does not bypass signing, sandbox, or other security features of the OS.