App Design & Development

We design and build the apps your members, customers and staff use, and the platforms behind them: content systems, learning platforms and internal tools. Everything is built for regulated work, and the code and data are in your name from the first release.

How we build an app

Our senior designers and engineers work as your product team, from the first sketch to the release in the app store.

  1. We design with the people who'll use itWe hold short sessions with members, staff or field teams, then give them screens they can tap through on their own phones before anything is built.
  2. Goals become a first releaseWe agree with your leadership which goals the first release serves and how you'll know it works, then break it into small pieces we can build and test quickly.
  3. Built fast, reviewed by a senior engineerWe use AI coding tools to write and test each piece quickly. A senior engineer reads every change before it reaches your app.
  4. A release every week or twoYour team gets a working build every week or two, in your own app store listings and cloud accounts.

When the app is in the way

Teams usually come to us with an app that's in the way. It's slow, or it breaks on the phones people actually carry. It was built on a framework your staff can't maintain. Or it's rented: rebuilt every year, with its data in the vendor's system until the next contract.

Behind the app sit the platforms that feed it, like a content system only one contractor understands, or a learning platform built in-house that strains every time the catalog grows.

At a medical society it's often the meeting app and the courses between meetings. At a medtech company it's the app that trains clinicians on a device. In a healthcare PE portfolio it's the front desk, where staff work around the scheduling software with spreadsheets and a second login.

A designer and a clinician trying a new build on a phone
  • Members and attendees
  • Field and training teams
  • Staff

Designed with the people who use it.

  • iOS, Android and web
  • Code and data in your name

What we build

We design with the people who'll use it, build in your accounts, and keep the old system running until the new one is ready.

  • Apps for members and attendees. We build meeting apps that stay open all year, with the agenda, faculty, maps and the next session during the meeting, then courses, CME tracking and credit evaluation between meetings.
  • Apps for field and training teams. We put product information, training and checklists on a rep's or technician's phone, and keep each person's progress in your own records.
  • Internal tools and portals. We build the queues, forms and dashboards your staff use every day, plus portals where sponsors, practices or customers see their own results.
  • Platforms and content systems. We move and modernize content systems with clean cutovers, so pages keep their addresses and search rankings. For Dermsquared, that was Strapi to Storyblok.
  • Learning systems. We move courses, credits and learner records off fragile homegrown platforms onto ones that scale. For Dermsquared, that was a homegrown platform to Docebo.

What people do in the app, from sessions attended to courses finished, flows into reporting you own through our data science work, so sponsors and leadership see it all year.

Hands testing an app on a phone, with more test phones and screen sketches on the table
44%
of association members say they use their association's mobile app frequently.
Forj, 2025 ↗
A designer sketching phone screens beside an engineer at a laptop
65%
of learner interactions in accredited CME in 2025 were in on-demand courses.
ACCME Data Report, 2026 ↗

What we built for Dermsquared

Dermsquared used to rent its conference app every year. We built it an app it owns, code and data included, with the agenda, faculty, maps, next session and credit evaluation in one place. It's been live year-round since September, with learning on the web and in the app between meetings.

The platforms moved with it. The same team built a new API behind the web and the app, moved the content system from Strapi to Storyblok, and moved the courses from a learning platform built in-house to Docebo. We rebuilt the most important paths first and let content that was due to expire run out, so there was never one big, risky switch.

Its support tickets are down 80%, and the first release went from concept to production in three months. The Dermsquared case study walks through the work.

Dermsquared's learning site on a laptop and a phone, with a video session and the lessons beside it
They didn’t just build what we asked for. They understood what we were trying to accomplish and helped us get there.
Andrew DouglasCDTO, Dermsquared

Who we build it for

Societies and CME providers, the training teams at medtech companies, and specialty physician groups.

Questions we hear

  • We already have an app. Do you start over?

    Only if we have to. We start with the screens that cause the most trouble and replace them one at a time, so people keep using the app the whole way through.

  • We're under contract with our current platform.

    That's fine. We plan back from the date it ends and start on your data while the old platform is still running, so the new one is ready that day.

  • Why not buy something off the shelf?

    Often you should, and we'll tell you when. We build when the available tools would force your team to change how they work, or when you'd be paying for a whole platform to use one feature.

  • Can our staff change the app themselves?

    Yes. Sessions, faculty, courses and announcements are edited in a content system your staff run, so a change doesn't wait on us.

  • Who owns the code?

    You do, from day one, under your own accounts: the repositories, the app store listings and the data. If you hire your own team later, they start from working code.

More capabilities

We'd love to chat.

Bring what's slow, rented or stuck. You'll leave with what we'd build first and how long it takes.

Book a call