Bard mobx router

Bard mobx router

  • Github

›About Bard router

About Bard router

  • Philosophy
  • Getting started

Router and routes

  • Route specific hooks
  • Router hooks

React UI Components

  • <Route/>
  • <Link/>

Plugins

  • Scroll plugin
  • Window title plugin
  • Html5 history plugin

How to's

  • How-to's / FAQ

Philosophy

You can always fix a bug in a library, but a bad architecture will turn your entire project into Hell.

With that in mind, I have been on a never ending quest to find a simple but effective architecture to easily build mobx / react apps in particular. The journey so far has lead me to the following three points for a happy developer experience.

App architecture design fundamentals

Note: these principles can be applied to any kind of software, Bard router was made to allow such implementations in a react / mobx context.

Clean architecture by Robert C. Martin (Uncle Bob)

“By separating the software into layers, and conforming to The Dependency Rule, you will create a system that is intrinsically testable, with all the benefits that implies.”

Link to Robert site

Decouple state and UI by mobx author

"Strategies for dealing with routing, data fetching, authentication and workflow testing without the UI layer."

Link to Michel Weststrate article

App shell architecture

"An application shell (or app shell) architecture is one way to build a Progressive Web App that reliably and instantly loads on your users' screens, similar to what you see in native applications."

Link to developer.google.com

Getting started →
  • App architecture design fundamentals
    • Clean architecture by Robert C. Martin (Uncle Bob)
    • Decouple state and UI by mobx author
    • App shell architecture
Bard mobx router
Docs
Getting Started
Community
Who is using this?Chat on Gitter
More
GitHub
Copyright © 2023 Aodev