A look at the technical nature of creating a peer learning experience. We have this concept of web components sitting on the safe network and ‘Dapps’ being just an instant pulling together of a peer/user experience and accompany functionality. We don’t envision discrete pre-built single purpose Dapps, maybe just ‘templates’ to help with the bootstrapping of a JIT (just in time) experience. For example, a component for charting data sitting on the safenetwork could be used in multiple Dapps (regardless of framework or UI tools used). If we don’t have to repeat ourselves then we can push forward new innovations quicker than the cloud stack.

We are still looking for solutions and ideas on how to implement this (or to debate if this makes any technical to economic sense i.e. pro and cons of this thinking). Modular is a key design feature. We have come across https://single-spa.js.org/ and see this as a step in this direction. A networked implementation would the next step. For the new release of the DIY HealthScience Toolkit https://github.com/healthscience/diyhstoolkit we would like to experiment with this way of thinking. Right now we have chosen vue.js with the goal of making the code more modular and building the components on the fly ( like they are doing here from the cloud https://markus.oberlehner.net/blog/distributed-vue-applications-loading-components-via-http/ 2 )

Written by

HealthScience in the hands and hard drives of the people

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store