Monday 15 September 2014

OS as a Design Pattern

For a while now, I have been thinking and tinkering with the concept of using operating system principals in a browser framework. The purpose and motivation behind this are: -

  • Scalability for the software: Many we applications are built as a single solution with lots of developer changing code before a build process pulls it all together. This makes large scale deployment hard and large scale development even harder, as it is very easy to trip over each other. 
  • Reduction in boiler plate code: Web Apps require a certain amount of boiler plate code to enable them work, which is then repeated over and over again. Frameworks can help but these tend to be more focused on the UI.  
  • Improved integration: Web Apps deployed within an organisation struggle to communicate with each other and end up relying on adhoc solutions that are susceptible to breaking. 
  • Security: Web Apps hosted in a portal style can easily scrape information from each other, especially if the developer has used global namespace to store information. 
  • 3rd party integration: It is very difficult / impossible for a developer to create a small "app" for integration into a larger product. 

The vision would be something similar to FaceBook / the now defunct iGoogle, which allow 3rd parties to develop secure Apps to be hosted in a larger suite. Obviously the afore mentioned products are large, complex and unavailable for businesses to buy, but would it be possible to develop a similar solution, to allow business to run a platform that can then be customised for/by each individual via an web app market?

Over the next few months I plan to investigate this concept, in design and code, to make a working example and provide the source code open source. I welcome any thoughts and feedback you may have.

No comments:

Post a Comment