App Development Best Practices-3 (Build, Feature preview and Deploy pipelines)

If you haven’t yet read the previous articles in this series, you can find them at

App Development Best Practices-1 (Version Control) - Record our changes

App Development Best Practices-2 (Version Control Extended) - Structured Changes, Helps communicating

We need a way for our app to be delivered to users. Since this is a web app that are developing, to deliver this web app we need to host it on some server. But before delivering we need to make sure everything is working fine. And even before everything works fine we need a way

• to see/verify what we are building is according to expectations,
• show and get feedback on what we are building.

We can run the code locally on our machines and continuously see the effect of the changes we make. But that is only local to us. Let us say for example a product owner or a designer or another developer wants to see the work in progress feature that you are developing and wants to provide feedback. For another developer, may be it is easier as they can checkout our branch and run it locally but for other stakeholders it is cumbersome and not ideal. We could build our code and deploy it manually to a server and let the other stakeholders about it. But we make a zillion changes during the development of a feature . It will be cumbersome and inefficient to manually build and deploy. That is where deployment pipeline…