loop+ iOS
Application (Beta)


Wheelchair users are at risk of injury due to unhealthy seating habits, often unaware of developing issues because they can't feel or communicate discomfort. loop+ uses sensor pad technology to monitor pressure and movement, providing continuous visibility into seating behaviours. This also benefits support teams, allowing allied health professionals to easily track and document client behaviour outside of the clinic, improving care and speeding up insurer assessments for necessary equipment.


 

The loop+ device being fitted into a wheelchair. The chair on the left shows how un-intrusive the pad is when fitted.

Frame 427320931.png
 

Role

As the sole designer for the iOS app, I led the end-to-end design process, influencing product decisions, shaping the brand’s visual direction, and creating a scalable design framework.

The Approach

Field data from a prototype provided clear direction for the app, focusing on two key functions:

Pressure Map - Provides real-time pressure and position tracking
Event log - Logs daily activities and tracks pressure over time

Overlaying these data sets helps users and their support team identify pressure patterns and potential risk areas.

 

Early concepts for the Event logging - figuring out the types of content we may need to display in the app.

 

Rectangle 22 (2).png
 

Creating Engagement

As the design took shape, a key concern was user engagement—how to ensure daily app usage. Since users were new to the concept, understanding how the app fit into their lifestyle required releasing basic functionality quickly to gather insights.

Process

We adopted a build-measure-learn approach, aiming to release a working prototype (Beta) quickly. Deliverables focused on key user needs, driving a staged release plan. With 3-week sprint cycles, it took about 6 sprints to reach the first prototype. Embedding design into development sprints facilitated clear visibility and improved team collaboration.

 

Events and Pad views

 

What Were Users Saying?

The first beta release (0.2.0) allowed pre-selected users to test the app over two weeks, focusing on both hardware and software experience.

Slow event logging – Users found it took too long to add events on the go, leading to retrospective logging and inaccurate data.

Usability challenges – Less tech-savvy users struggled to understand the app's features and how to use it effectively.

Lack of actionable feedback – Users felt the app did not provide enough meaningful output or guidance.

As a result usage declined over time, highlighting the engagement issue.

 
Rectangle 22 (4).png

 “It's the data that shows me what times of day I’m typically most at risk which is important to me. Maybe seeing this in graphs, where the risk may increase until I do a pressure relief, Or how many times throughout the day I’m over a threshold.”

loop+ Tester

 

Next Steps 

To improve engagement, we introduced a summary page providing a daily snapshot of key metrics, like idle vs. active times and positioning. Over time, we added user-defined goals and pressure management features. Following the build-measure-learn process and addressing UAT feedback after each release, we reached a point where we were confident in releasing the product to market.

 
 

Replay event screen and the first cut of the summary screen ready for release.

 
 

Building A Design System

My goal was to create scalable tools and processes, with a focus on building a design system for consistency and efficiency. This system included styles, components, patterns all with guidelines, allowing new designers to quickly integrate.


 

Figma design system

 

Capturing Post Release User Feedback

As sales grew, we set up Fibery to centralize user feedback from multiple sources, including our CRM, in-app messaging, and the CX team’s field conversations. Each month, I synthesised this data to uncover insights and identify recurring user needs, which influenced product planning.

 

One “Hunch” created in Fibery off the back of 10 seperate references. This was used to drive product planning for future releases.