Full App Redesign

This app was stuck in development hell for about 7 years, I was brought on to clean-up what they had and polish the design for delployment

Main Client Goal: turn their working prototype into a deploy-ready polished design

Disciplines
UX to improve the genral user experiance
UI custom made assets
Brand Strategy guidance to get their app ready
Deliverables
Full design Audit with imporvment recommendations
user flows and prototyes
costom artwork icons and symbols, and app website
recommendatons for next steps with legal, launghing, promoting, and managing comunity chats
Timeline
5 months
Process
Full design Audit with imporvment recommendations
user flows and prototyes
costom artwork icons and symbols, and app website
recommendatons for next steps with legal, launghing, promoting, and managing comunity chats
Why they wanted a designer

Unlocking Their Potential

Problem: This project had been in development for seven years, trapped in a cycle of feature additions without a cohesive user experience strategy.

My role was to perform a comprehensive audit of the existing build, identify critical usability failures, and polish the design for a successful public deployment. The core features were all present, but they were hidden behind inconsistent UI, poor information architecture, and visual clutter that prevented users from understanding the app's value.

Screenshot 1: The app's homepage suffers from terrible visual hierarchy and contrast. The user's attention is drawn to unimportant decorative elements, while the primary action drivers are unclear and visually weak.Screenshot 2: The community chat interface presents just dense blocks of text. It is completely unclear if a user is in a private chat, a group, or who will see their response, destroying any sense of context or conversation.Screenshot 3: The categories page is a long, undifferentiated list of random themes with no visual organization or grouping. It is cognitively overwhelming and difficult to scan or navigate.Screenshot 4: The feedback screen after finishing a quest is dominated by a lengthy survey. 70% of the screen asks for information that is never used again in the app, creating a jarring and pointless user experience.Screenshot 5: The timeline uses an odd horizontal layout unsuitable for a phone screen. Large photos and elements are crammed into a single fighting row, making the content feel cramped and inefficient.Screenshot 6: A critical screen like the challenge prompt uses low-contrast white text on a light blue background, making it difficult to read. The reason for the user's choices is also unclear, adding to the confusion.
Discovery

Strategic Audit: From Diagnosis to Solution

My design audit categorized critical failures by severity, providing a clear roadmap for the redesign. Each finding directly informed a key strategic solution in UX and brand identity.

Design audit slide ranking "Unclear Task Support" as High Impact. It critiques how the app asks for information that is never used again and fails to narrate what is important or which actions are most valuable to the user.Design audit slide ranking "Data Visualization" as High Impact. It points out how reports and templates prioritize layout over content, creating a clarity problem where the hierarchy says "I am a timeline" instead of "this information is important."Design audit slide ranking "Unclear Action Cues" as Medium Impact. It highlights the undefined rhythm and pacing of quests, making it difficult for users to integrate the app into their daily habits and understand time commitment.Design audit slide for "Mental Models," rated Medium Impact. It shows how quest categories are illogically grouped (e.g., dog, animal, plant, bacteria) and span inconsistent scales (solo, community, world), recommending a reorganization into consistent intensity levels.Design audit slide highlighting a critical UI failure: color contrast ratios largely below 2.0, far failing the WCAG 4.5:1 minimum standard. This was ranked as a high-impact, catastrophic failure.Design audit slide for "Text Visual Scan," rated Low Impact. It notes that long category names get truncated with ellipses and will cause scrolling/zooming issues with accessibility font scaling, recommending shorter, scannable names.

Design Audit Findings

Catastrophic Failures (High Impact)

  • Finding: Unclear task support & abysmal color contrast (< 2.0) violated WCAG and destroyed usability.
  • UX Solution: I rearchitected the onboarding to only ask for essential information and implemented a high-contrast, AA-compliant color palette with light/dark mode.
  • Brand Solution: The new playful yet accessible color scheme (pink, mint, orange) replaced the stressful, low-contrast UI, making the brand feel supportive, not broken.

Structural Failures (Medium Impact)

  • Finding: Illogical mental models mixed categories (e.g., dog, animal) and scales (solo vs. world), creating cognitive dissonance.
  • UX Solution: I introduced a consistent intensity scale for quests (small, medium, large). New users start with small, solo-able quests; larger community-based quests unlock after building skills and connections.
  • Brand Solution: The new 7 thematic categories (Explore, Share, Play, etc.) are logical, scannable, and reinforced with custom icons containing hidden hearts, making the system feel cohesive and intuitive.

Polishing Enhancements (Low Impact)

  • Finding: Long category names truncated and failed visual scanning, especially with accessibility text scaling.
  • UX/Brand Solution: I established a clear typography hierarchy and renamed all categories to single, powerful words (e.g., "Play," "Explore"). This worked hand-in-hand with the new icons to ensure quick recognition and scannability for all users.
UX design

Onboarding Flow

A case study showcasing a complete redesign of a tedious and inequitable onboarding process for a health app, transforming it into an equitable, low-friction experience that respects the user's time and partnership.

Orignial Design

A series of eight screenshots demonstrating the app's original tedious onboarding process: intro, survey, tutorial, and mandatory sign-up. This sequence represents a significant front-end investment required before a user can even try the app to see if it's valuable to them.

The original onboarding suffered from two core failures:

  • A Deep Violation of User Expectations: In a modern app ecosystem, users have a built-in mental model for how onboarding should work. They expect a 'try before you buy' experience—a chance to quickly assess an app's value before investing significant time. Forcing users through a long, mandatory process before any interaction violated this fundamental expectation, creating immediate resentment and drop-off.
  • The 'Why Now?' Problem: The extensive survey asked deeply personal questions at the worst possible moment: before the user understood the app's benefit or trusted the platform. This felt invasive and random because the user couldn't see how this data would be used to improve their experience. It was a tax with no visible return on investment, making it feel useless from the user's perspective.
A series of eight screenshots demonstrating the app's original tedious onboarding process: intro, survey, tutorial, and mandatory sign-up. This sequence represents a significant front-end investment required before a user can even try the app to see if it's valuable to them.Original role selection: Two unclear icons with the ambiguous text "Which role are you?" providing no context for the choice.

Early Prototype

The first redesign draft simplifies the process. It keeps role selection and a simplified spine injury section, then immediately lets the user try the app via an active tutorial instead of passive instructions. Sign-up is made optional and moved out of the onboarding flow, allowing users to experience basic functionality without commitment.

My redesign was guided by core principles of cognitive psychology and modern UX:

  • Leverage Existing Mental Models: I assumed users are experts in using apps. The interaction, picking and finishing quests, is a familiar pattern. The onboarding didn't need to teach how to use the app; it needed to sell why this app was valuable for their specific partnership.
  • The Principle of Least Effort: The goal was to minimize the barrier to the first moment of value. By making sign-up optional and front-loading the active tutorial, the app respects the user's time and intelligence, allowing them to engage on their own terms.
  • Just-In-Time Information: This draft began the crucial shift away from asking all questions upfront. It introduced the concept of gathering information only when it's needed to unlock a specific, desired feature, making the request feel relevant rather than random.
An early redesign draft that simplifies the process. It keeps role selection and a simplified spine injury section, then immediately lets the user try the app via an active tutorial instead of passive instructions. Sign-up is made optional and moved out of the onboarding flow, allowing users to experience basic functionality without commitment.

Final Design

The final prototype solves a major UX failure: inequity between partners.

Instead of only the disabled partner filling out a lengthy survey about their body, both partners are treated equally. Both can select disabilities they struggle with. The clinical terms "care partner" and "patient" are replaced with the partners' actual names and the equitable roles of "Supporter" and "Groover," allowing them to define their partnership based on their strengths. The survey only appears when a feature actually needs it.

The final prototype wasn't just a usability fix; it was a strategic alignment with the company's long-term vision to support all types of partnerships, not just spinal injury.

  • From Binary to Spectrum: The old model of "Care Partner" and "Patient" was a rigid binary that failed to capture the nuanced reality of how partners support each other. My solution of "Supporter" and "Groover" is fluid. Anyone can be a supporter in one area (e.g., physical tasks) while being a groover in another (e.g., neurodiverse planning). This flexibility was essential for scalable growth.
  • Solving the 'Why Now?' with Purpose: The survey was no longer a pointless tax. It became a key to community and relevance. The data directly filters users into community chats (e.g., "Physical Disability Supporters" or "Neurodiversity Groovers"). Now, users understand the why: sharing their challenges connects them to a tailored support network. The question is no longer "Why are you asking this?" but "Which community do I want to join?"
  • The Qualitative Result: The new flow transforms the onboarding from a bureaucratic hurdle into an empowering setup ritual. Users aren't just providing data; they are curating their own experience and defining how they want to give and receive support within the app's ecosystem. This directly builds trust and investment in the platform from the very beginning.
The final prototype onboarding: three clean screens that quickly communicate the app's purpose as a science-backed research project, followed by a welcome. This establishes value immediately with minimal friction.
The final prototype solves a major UX failure: inequity between partners. Instead of only the disabled partner filling out a lengthy survey about their body, both partners are treated equally. Both can select disabilities they struggle with. The clinical terms "care partner" and "patient" are replaced with the partners' actual names and the equitable roles of "Supporter" and "Groover," allowing them to define their partnership based on their strengths. The survey only appears when a feature actually needs it.

In-App Chats

The original app used a single, confusing interface for personal notes, partner chats, and global communities. This created a high risk of users accidentally sharing private medical information publicly.

My redesign introduces distinct visual characters for each communication type, creating clear mental models and preventing critical errors.

Personal Journal

The personal journal function was redesigned for clarity and utility. I implemented a vertical layout optimized for mobile scrolling, consolidating the timeline and note-taking features into a single, coherent history.

A key user request was to track how quests affected their mood (a beloved feature from the old system that was previously isolated and disconnected). The new journal integrates mood recording directly alongside the quest's symbol and name.

Critically, it only displays the information the user provides; it removes the frustrating blank template for photos, presenting their data in a pleasant, streamlined way. Furthermore, entries are color-coded by quest type, allowing users to visually scan their history to identify patterns and habits in their well-being at a glance.

Screenshot 2: The community chat interface presents just dense blocks of text. It is completely unclear if a user is in a private chat, a group, or who will see their response, destroying any sense of context or conversation.Screenshot 5: The timeline uses an odd horizontal layout unsuitable for a phone screen. Large photos and elements are crammed into a single fighting row, making the content feel cramped and inefficient.The redesigned personal journal seamlessly combines the timeline and notetaking features. Users can now add photos, rate quests with a star, and write notes all in one vertical, scrollable history to track patterns and trends.A close-up of the new journal entry editing screen, showing how a user can update their personal history with text, photos, and ratings after completing a quest.

Community Connections

The community feature is fundamentally about constructing and maintaining human connection. The partner chat is more than just texting; it's a dedicated space for relationship-building. Partners can give specific feedback on quests and see which ones each other favorited, providing immediate, non-verbal insight into what truly affected their significant other.

The global communities are designed to leverage a built-in advantage: creating a safe place to ask questions that might not get time in a clinical setting. These spaces are moderated by clinicians who recommend the app to their patients, adding a layer of medical oversight. This allows for intervention—guiding users to a hospital or crisis center when necessary—ensuring accountability and keeping people safe when they are most vulnerable. Ultimately, these communities provide a rare and crucial outlet: a place to get advice from others who share the same point-of-view, to vent frustrations in a healthy way, and to process difficult emotions without the risk of lashing out at a partner or turning to self-harm.

The community connections hub, styled similarly to Discord or Microsoft Teams. The user's partner chat is pinned to the top for easy access. Vertical circles on the left show avatars for active chats.The focused view of the private partner chat. The interface looks like a standard text message exchange, with the partner's name and avatar clearly at the top. This familiar model makes it easy to discuss which quests are working.The view of global, topic-based communities. The user is highlighted in a "Macular Degeneration" chat for supporters, with a "Sensory Disabilities" tag showing why they were added. This is based on their onboarding survey.The focused view of a global community chat, designed like a Reddit or Discord thread. The title "Macular Degeneration" and "Supporters" tag are clear. Users can heart comments, see reply counts, and expand threads to participate. The top bar clearly labels it "Community Feed".

Accessibility

Accessibility wasn't a feature in this app; it was the foundation of the experience. Our target audience was a couple navigating the complexities of disability together, striving to maintain their relationship beyond the dynamics of caregiving. If the app itself was inaccessible—if it was confusing, frustrating, or required interpretation—it would become just one more thing that eroded the diabled parners independence and forced the other partner into a caretaker role.

Therefore, our usability had to be flawless. The design needed to be so intuitive, so clear, and so engaging that using the app felt like a fun, shared activity—a highlight of their connection, not a burden. This commitment to radical clarity and multi-modal understanding directly fueled our solutions.

Cognitive Accessibility Multi-Inputs

The redesigned categories screen, demonstrating a multi-input UI for enhanced cognitive accessibility. Each category is represented by three elements: 1. A thematic symbol (e.g., a heart for 'Sharing is Caring'), 2. A distinct color and value contrast, and 3. A simple, action-oriented title. This triple-redundancy supports users with different processing preferences, including those with brain injuries, by engaging multiple pathways of understanding.

One of the key accessibility challenges was ensuring the interface was usable for individuals with cognitive differences, including those with brain injuries common alongside spinal cord injuries. My solution was a multi-input UI system for core actions.

Each category uses three distinct cues:

  • A symbolic icon for visual processors.
  • A unique color/value for those who differentiate by contrast.
  • A simple, action-oriented title ("Explore," "Sharing is Caring") for text-based processors.

This triple-redundancy ensures that if one cognitive pathway is compromised, others are available to successfully communicate the option's purpose. This creates a more robust, forgiving, and inclusive experience for every user, embodying the principle of Universal Design.

Sensory Accessibility Contrast

While the multi-input system solved for cognitive clarity, the visual interface itself posed significant physical barriers. The original design used low-contrast colors and problematic color pairings that caused eye strain and were illegible for users with low vision or astigmatism.

Our redesign tackled this on two fronts:

  • Enforcing Contrast: We implemented a strict color palette that met WCAG AA standards across all text and interactive elements.
  • Providing Autonomy: We gave users a choice between a light and dark theme, allowing them to select the contrast environment that best suited their individual visual needs, transforming accessibility from a mandate into a user-controlled feature.
The original homepage demonstrates critical accessibility failures. It uses a light blue background with low-contrast white text that is too thin and small. It also shows a menu with a black background and light purple text that also fails contrast ratios. Black backgrounds can cause pupil dilation, making text appear blurry for users with astigmatism.The finalized, accessible color palette chosen for the redesign. Each color pair has been tested to meet or exceed WCAG AA contrast ratios of 4.5:1, ensuring legibility for users with low vision or color blindness.The redesigned homepage in light mode. It uses the new accessible color palette with high-contrast, large text on a neutral background, successfully meeting WCAG AA standards. The layout is clean and clear.The redesigned homepage in dark mode, offering the same high-contrast, accessible layout with a dark theme. Providing both light and dark mode gives users autonomy to choose the contrast configuration that is most comfortable for their visual needs, reducing eye strain.

Physical Accessibility Dexterity & Strength

Completing the accessibility trifecta, the final overhaul addressed physical accessibility. The original design placed critical navigation buttons at the top of the screen, a difficult reach that requires significant grip strength and precise dexterity. I relocated the entire navigation system to a bottom navigation bar.

This strategic move serves three key purposes:

  • One-Handed Use: It places every primary function within the natural 'thumb zone,' making the app fully operable with one hand.
  • Leveraging Strength: It utilizes the hand's stronger muscles for stability, reducing fatigue for users with weaker grip strength.
  • Applying Fitts's Law: The targets are not only larger but also spaced farther apart, providing a larger margin of error. This is critical for users with conditions like quadriplegia, where fine motor accuracy can be impaired, ensuring that every action is intentional and successful.

This change transforms the app from a physically demanding tool into an effortless extension of the user, ensuring that motor impairments are not a barrier to connection and support."

Designing Beyond Compliance (ADA and WCAG 2.2 AA)

For me, accessibility isn't a separate checklist to be applied at the end of a project. It is the foundational principle upon which all good design is built. ADA and WCAG 2.2 AA guidelines represent the bare minimum legal and technical requirements. My goal is to not just meet these standards, but to far exceed them by designing experiences that are inherently intuitive, flexible, and usable for everyone.

My approach integrates core accessibility principles directly into the architecture of the product:

  • Clarity Over Complexity: I design self-explanatory interfaces that don't rely on supplemental ARIA tags or alt text to convey critical meaning. The important ideas are baked into the core user experience, making them available to all users by default.
  • Cognitive Empathy: My designs prioritize reducing cognitive load through consistent patterns, clear information hierarchy, and predictable workflows. This benefits everyone, especially users with cognitive disabilities, ADHD, or those who are simply distracted or stressed.
  • Universal Usability: By building for the broadest range of human ability and context from the very first sketch, I create solutions that are more robust, elegant, and user-friendly for all. This results in a higher standard of usability that often renders basic compliance a natural byproduct, not the primary goal.

The designs in this case study aren't just "WCAG compliant"; they are crafted to provide a seamless and superior experience that acknowledges the vast spectrum of how people see, think, and interact with the world around them.

brand strategy

The Brand Identity

The client's initial direction used a common 'handicap' style: blocky, stick-figure people in solid colors. This directly contradicted their core mission: to avoid infantilizing users and to see them as people first, not their disabilities.

I advocated for a more organic, dynamic direction that focused on the universal theme of balance in all relationships (romantic, familial, and platonic). This shift placed their love and connection at the forefront, moving decisively away from clinical terminology and imagery.

Logo Exploration

An important theme in their brand was treating both partners as equals by not infantilizing the disabled partner or treating the caretaker partner as a babysitter.

This logo shows that by having the fish with the full tail and fish with the weaker tail both creating the heart, as a metaphor for both partners showing up in the relationship in the ways that they can.

The other metaphor is that with chronic conditions, there is an ebb and flow of good and bad days. So the fish swim with the currents and adjust as needed to restore balance when they can like yin/yang.

Logo concept sketch exploring a yin-yang inspired flow within a circle. Two bodies create a heart shape from the negative space between them, symbolizing partnership and balance.Mood board for organic brand direction. Contains images of flowing flowers, sunsets, and dresses to capture the dynamic, natural, and ever-changing essence of human relationships.Evolution of the brand's color palette. The original direction of stark purple and red is shown next to the chosen softened, more romantic valentine palette of purple and pink.Testing various custom-drawn fish logo variations alongside different typography treatments for the brand name to find the most harmonious pairing.A logo variation within a perfect circle, with two bodies flowing into one another and a heart formed positively in the center. This was rejected for its poor scalability in solid black or white.An early, more realistic fish logo concept with subtle heart shapes formed by the bodies. This was rejected due to its complex edges, which created too much visual noise for a functional logo.

Handcrafted UI for a Human Feel

To further distance the brand from a sterile, clinical feel, I created all UI assets by hand. This intentional imperfection provides an organic, playful quality that reinforces the app's human-centric purpose.

Each of the seven theme category icons contains a hidden heart and features a darker, more solid body for consistent visual weight and better contrast. This small, discoverable detail reinforces the core message of love and connection in every activity.

Hand-drawn icon for "Partner Quest": two puzzle pieces fitting together to form a hidden heart shape, symbolizing building something together.Hand-drawn icon for "Exploration": a map with a winding path that leads to a heart-shaped destination.Hand-drawn icon for "Play": a classic game controller with its wire coiled into a subtle heart shape.Hand-drawn icon for "Self-Improvement": a flexing fish with six-pack abs and hearts floating around its muscles.Hand-drawn icon for "Gratitude": a collage of small hearts forming one larger heart shape.Hand-drawn icon for "Self-Reflection": a brain swimming alongside bubbles, some of which are shaped like hearts.Hand-drawn icon for "Acts of Service": a gift box with a heart-shaped ribbon.

The navigation system continues the brand's fun, nautical theme with custom icons, creating a cohesive and immersive world for the users to explore together.

Custom nautical-themed "Home" icon: a simple house shape.Custom nautical-themed "Quests" icon: a message in a bottle.Custom nautical-themed "Community" icon: a globe tilted on its axis.Custom nautical-themed "Timeline" icon: a stopwatch.Custom nautical-themed "Dares" icon: a sand dollar.Custom nautical-themed "Settings" icon: a ship's gear or steering wheel.An alternative "Dares" icon not used in the final design: a treasure chest.

Branding Direction

Throughout the branding process, I presented the client with a range of directions, from more conservative to openly playful.

At every decision point, from color samples to shape language, they consistently gravitated toward the option that was the most fun, bright, and full of whimsy. This unanimous and enthusiastic choice validated our strategy to move decisively away from clinical imagery and toward a brand that celebrates joy and connection.

The result is a cohesive identity system of playful icons, a vibrant palette of pink, mint, and orange, and organic shapes that together create an experience that feels less like a medical tool and more like a shared adventure.

The final, polished Support Groove logo: two stylized fish, one with a full tail and one with a weaker tail, swimming together to form a heart shape.The final vibrant color palette: playful bright pink, mint green, and orange, chosen to evoke fun and energy.A stamp icon for a solo quest: a green potion in a round bottle.A stamp icon for a quest finished together: a pink potion in a heart-shaped bottle.
The new dashboard, featuring color-coded quest categories and a prominent orange "Dare" button as the primary action.A confirmation screen showing the new quest categories, each represented by their distinct brand color and custom icon.
Prototype

Results and Next Steps

Building the high-fidelity prototype allowed us to see our solutions interact as a whole system, revealing new insights and defining what to test with users next.

Prototype Insights: Enhancing Clarity & Control

A key insight was shifting from simply stating a change occurred to explaining its meaning and giving the user control.

  • Before: A message would just say "You linked with partner" or "Role changed."
  • After: The UI now summarizes what happened, what you did, and what it's called. For example: "You just linked with Alex! They've tagged themselves as a 'Groover' for physical mobility. You can adjust these connection settings anytime." This provides immediate understanding and a clear path for future action.
Original "You linked with partner" screen: A generic confirmation message with no personalized details.Redesigned connection screen: Clearly states "You just linked with [User Name]" and displays their avatar and self-selected tags, providing immediate personal confirmation.Original role selection: Two unclear icons with the ambiguous text "Which role are you?" providing no context for the choice.Redesigned onboarding summary: Explains the consequence of chosen tags: "Now you can go into community chats for Supporter and Groover." It visually highlights the user's tags in dark (Supporter) and light (Groover) colors.

We reinforced that all engagement is opt-in, transforming obligation into agency.

  • Before: Quests and dares were presented with unclear commitment levels and vague themes.
  • After: The design now makes the type of challenge crystal clear before acceptance. It's easy to see the theme (e.g., "Play") and understand what to expect, allowing users to choose activities that align with their energy and interests.
Original dare screen: Unclear header and description, making it confusing what the user is agreeing to do.Redesigned dare screen: Clearly labels the type of dare and provides a prominent "Reject" button, giving the user clear options and control.Original quest selection: A list of categories with inverted visual hierarchy, making it hard to distinguish between themes and specific quests.Redesigned quest selection: Each quest is clearly defined by its theme color and icon, a descriptive title, and a "Try" button. The layout allows users to easily "Pick a different one."

Outcomes: Confidence & Reignited Passion

The most significant outcome was a complete renewal of the team's belief in their project.

  • From Stuck to Shippable: After 7 years in development hell, the client finally feels they have a resolved, shippable product. The design provided the clarity and confidence needed to move forward.
  • Reignited Excitement: The client's enthusiasm was reawakened. Seeing the polished, playful, and professional prototype made the project feel real and tangible—something they could genuinely imagine in the app store.
  • A Cohesive Brand Identity: The evolution from the old, generic logo and name to the new "Support Groove" brand with its meaningful fish icon reflects the app's transformed purpose: to be a supportive, balanced, and joyful experience for all partnerships.

Next Steps: The prototype is now ready for formal user testing, focusing on the new onboarding flow, the clarity of the quest categories, and the overall usability of the partner connection features.

2 stick figures creating a heart in the middle with negative spaceThe final, polished Support Groove logo: two stylized fish, one with a full tail and one with a weaker tail, swimming together to form a heart shape.