Ask HN: Has anyone solved reproducible deployment of native mobile platforms?

For the last several years, our team has been working on one question: does every new native mobile platform really need to be a new development project?

We used to develop social and business platforms as separate projects, and kept running into the same problem: much of the work had to be done again each time. So we tried to change the process itself — from repeatedly developing new platforms to creating them from an engineering system we had already built.

We developed and patented an approach that we've now used for more than 250 native apps published on the App Store and Google Play.

A new platform, together with its backend, can be deployed on the owner's own server in up to 24 hours. The platforms can have different functionality, structure and branding, while the common parts don't have to be developed again for every project.

Now we'd like to ask the engineering community: has anyone else solved this problem differently? Are there other approaches to reproducibly deploying independent native mobile platforms that we should know about?

If you've built something similar, are working on the same problem, or think we're approaching it the wrong way, we'd be interested to hear about it.