Building Software: MVP, Mobile, Web and Migration

This hub is for the person who will be technically accountable for the thing that gets built — a CTO, a tech lead, an operations head who has become the de facto product owner.

The decisions covered here are the ones that are expensive to reverse: how much belongs in a first release, whether mobile means an app or a responsive web page for people wearing gloves on a shop floor, what to do with fifteen years of data in a system whose vendor no longer answers email, and where an integration will break at three in the morning.

The lens stays the same as everywhere else on this site: what changes for the business. A stack choice matters because of hiring, maintenance and how quickly a change request becomes a deployment — not because of what is fashionable. An architecture decision is a business decision with a technical vocabulary.

Where we hold an opinion, it comes from having built and maintained these systems for clients in manufacturing, distribution and services. Where the honest answer is "it depends", the posts say what it depends on, which is more useful than a recommendation that ignores your constraints.