Skip to content

One platform for web, mobile, and partners.

A healthcare education platform had outgrown its original architecture. We rebuilt it around a shared API and automated the move from the old database.

Project:ACP DecisionsA past project. The story describes the work delivered and the technology used at the time.

The problem

Features had accumulated and been retired without removing their old code. New development was slow and error prone. The API had been bolted onto the web application, making it harder to support an iOS app and deliver content to partner systems.

A developer and a wheeled service robot distributing shared video content to web, mobile, and hospital systems.

What we built

We worked with ACP to compare the options, then rebuilt the platform around an API used by both the web and mobile applications.

  • Removed obsolete features and standardized ad hoc configuration.
  • Built a Symfony REST API and an Angular web application.
  • Created migration components to convert the old database automatically.

What changed

One set of content. More ways to deliver it.

The shared API made it easier to keep web and iOS features aligned and deliver content through partner implementations, including EMR experiences. Removing the accumulated feature debt also made further development easier.

The technical decisions

Why rebuild?

The existing application’s structure was limiting the business: mobile support and partner content delivery needed to become core capabilities. The rewrite addressed those constraints together.

Migration was part of the product.

Moving to a new structure also meant preserving existing data. Automated conversion components supported that transition rather than relying on a manual migration.

Let’s talk

Have a similar problem?

A rough idea is enough. We’ll work out the next step together.

Tell us what you need