COMMUNITY
APP PRODUCTION FRAMEWORKS

There are many ways to produce ("build") an app.

This page focuses on what the mydigitalstructure community has found best to consistently and robustly create apps that are fit-for-purpose in a timely manner.

This document is constantly being updated with feedback from the community, as new tools become available and new ideas are formed.

A key to production optimisation is the use of layers to create technical separation-of-concerns, supporting a division-of-labour, enabling a team of people to build the app, covering:

• Organisational needs analysis
• Design
• Produce (Build)

The app production framework that best fits the mydigitalstructure platform is the model-view-controlled architecture - the production processes are based on the layers inherent in this architecture.

PRODUCTION PROCESS

The key to an effective application production process is a clear understand in each step of:

• What you expect - the input.
• What do you expect from me? - the output.
• The skills required to complete the process.

With this understanding; each layer can use the best tools and people skills with complete abstraction from each other.

The skills required within each layer are also dependant on where the app is at in its life-cycle - the two key stages being:

• Start up - initial build.
• On going - incremental improvement.

Given that the mydigitalstructure platform manages the underlying resources the production processes can focus primarily on the View and Controller layers - i.e. the Look and the Feel.

The production process that we find to be most successful uses the continuous-incremental-improvement method - lot's of small iterations; starting with the view and then through to initial production release - and then beyond based on continuous business and user feedback.

We start with the View first; once it is designed and coded,it is then bound via the controller layer to the data (model) layer hosted on mydigitalstructure.