MedTech app development

Mobile app development backed by 25 years in MedTech.

JonWard Studios develops working prototypes and minimum viable products (MVPs) for MedTech teams. A project can pair the working app with a regulatory strategy, design and development file, usability engineering file, testing, and source-code handoff.

The expected workflow moves onto a device quickly for review, testing, demonstrations, and the next development or investment decision.

Discuss a MedTech app
25 years

Medical-device regulatory and quality experience

150+

Successful FDA 510(k) submissions overseen

Two build levels

Prototype or MVP.

The right build depends on the workflow, intended users, near-term milestone, and what the app needs to demonstrate.

01 / Prototype5 business days · target

One primary workflow.

A simpler design and build for concept review, workflow testing, demonstrations, or an investor meeting.

  • Primary app workflow from start to finish
  • Working mobile prototype
  • Concept and workflow testing
  • Internal review, demonstrations, or investor meetings
02 / MVP15 business days · target

Agreed core workflows.

A broader working build for evaluation, testing, demonstrations, or fundraising.

  • Agreed core workflows connected in one app
  • Working mobile MVP
  • Customer or beta use
  • Evaluation, testing, demonstrations, or fundraising

Client review and testing builds are provided through Apple TestFlight. Both build levels include the agreed tests and project records. Delivery targets begin after the scope and required project inputs are agreed.

MedTech project records

Software and records developed together.

The file contents reflect the product, intended use, agreed build, and stage of development.

01

Baseline regulatory strategy

Developed from the concept inputs and intended use.

02

Design and development file

Agreed requirements, design, risks, traceability, testing, cybersecurity, and release records.

03

Usability engineering file

Usability records developed with the build.

04

FDA and ISO requirements

Applicable FDA device-software and cybersecurity guidance and relevant ISO 13485 design and development requirements.

The resulting records can be carried into future development and premarket submission work.

Depending on the agreed scope, the completed build and records may be ready for formative or summative usability testing.

Development path

Concept inputs to handoff.

01

Define the build.

Confirm the intended user, expected workflow, milestone, and required project inputs.

02

Design the app.

Map the screens, interactions, requirements, and data for the agreed workflow.

03

Build, test, and document.

Develop the working app alongside its design, development, regulatory, usability, and test records.

04

Review and hand off.

Complete the final review and receive the source repository and project files.

Further development and regulatory application work can be scoped separately if requested.

Start with the concept

Tell us what you want the app to do.

Share the intended user, expected workflow, near-term milestone, and what the prototype or MVP needs to demonstrate.

Contact Jon