CASE STUDY:

Wellness Native App

Offered as a premium health benefit to clients' employees, "WellTrack^*" represents a data rich application designed to encourage the wholistic wellness of participants.

^*This case study represents actual work but may include changes to logos, terms, and names due to NDA agreements.

STARTING POINT

Old, outdated user interface based on prepackaged theme

Upon login, users of the original WellTrack client portal were greeted with: "This application works best on desktop or tablet." Beyond a poor first impression, users weren't engaged. At the time, more than 50% of online activity relied on mobile devices. WellTrack was forcing potential adopters to work around the app – not with it.

A generic, theme-based user interface had been purchased through a third party marketplace, known for providing widget-based UI. This led to dynamic and diverse health data being presented in boring, text-centric pages. The unflattering presentation created obstacles for current clients, sales staff, and overall growth of the business. the robust functionality and aspirational goals of WellTrack were shackled by substandard UI and an old-fashioned focus on desktop-first thinking.

Objectives:

Beyond a visual cleanup, and a refreshed brand, WellTrack needed all of their new technologies to encourage user interaction – a key metric monitored by WellTrack clients. The new interface needed to support:

Appointment creation, cancellation, suggestions, and reminders
Live video appointments using Twilio SDK
Health data aggregation via API, manual entry, and proprietary algorithms
Dynamic and realtime data visualization
Chat capabilities with notifications

GATHERING REQUIREMENTS

The WellTrack native app development began with a series of meetings including:
- Initial vision-casting session with stakeholders
- Review of user-provided criticisms, and general feedback
- Discussion around participating demographics, and key areas of opportunity
Initial development requirements were outlined to establish project scope, timeline, and budget
Work began to audit the current portal, articulate concrete expectations, and flesh out user personas in a Participant Portal Planning document (link below)

View the Planning document

WIREFRAMES and PROTOTYPES

Once development requirements had been established, work began on low-fidelity wireframes
After a series of presentation and refinement meetings, low-fidelity wireframes were shared with the development team to confirm feasibility
Once final approval of low-fidelity wireframes was achieved, work on a high-fidelity prototype began
One-on-one user testing sessions were conducted on the near-complete prototype, and appropriate revisions were implemented
Upon completion of the prototype, it was shared with all stakeholders for approval

Old, outdated user inteface based on prepackaged theme

DEVELOPMENT PROCESS

Upon stakeholder approval of high-fidelity prototypes, design system files were finalized and initial development began
I implemented the front end development, and turned around the restyled applications within three weeks
Once the web app had front end was complete, (aside from support tasks) I pivoted to flesh out a css-rich design system to support the native app development
I worked to support a contact Xamarin developer's translation of the web app to a fully fuctional native application
Six weeks prior to launch, all stakeholders were provided a dev version of the application for testing, and internal QA processes
Upon delivery, the final native and web apps were met with renewed excitement from stakeholders and stakeholder clients
Interactions per user increased significantly (more than double) during and after completion of this revitalization process