Our work

Case study

Connecting a wellness app with reporting

We worked across a Unity wellness app, a Node.js API and a React reporting dashboard. The work connected activities and journaling in the app with records and summaries that could be reviewed outside it.

How the workflow fits together.

  1. 01

    App activities and journaling

  2. 02

    API and stored records

  3. 03

    Dashboard reporting

The workflow

The app combined interactive activities, journal prompts and activity tracking. The reporting dashboard brought information from those experiences into a separate web interface, including journal responses and activity summaries.

Our contribution

We worked across the Unity experience, the backend and the React dashboard. The journaling workflow loaded journal records and saved responses through API calls. Dashboard components displayed those responses, while backend reporting assembled information from activity and tracking records.

The engineering approach

Unity handled the interactive app; Node.js and Hapi provided the API layer. MongoDB aggregation prepared activity summaries for reporting, and React with Chart.js supported the dashboard. Keeping reporting preparation in the backend gave the app and dashboard a shared source of application data.

We present selected work anonymously to respect client confidentiality and protect sensitive business and technical information. Each example describes the relevant engineering contribution while keeping identifying details private. Schedule a call to discuss relevant experience.

Back to the project overview

Have something in mind?

Tell us about the workflow you want to improve.

Start a conversation