Ray

View other case studies

Ray | March 2024
Ray | March 2024
Ray | March 2024

Launching a brand-new app to the marketplace from the ground up

Launching a brand-new app to the marketplace from the ground up

Launching a brand-new app to the marketplace from the ground up

What is ray?
What is ray?
What is ray?

Ray is a lifestyle app that aims to help users build confidence and self-awareness through daily interactive affirmations, and a community focused on well-being.

Ray is a lifestyle app that aims to help users build confidence and self-awareness through daily interactive affirmations, and a community focused on well-being.

Ray is a lifestyle app that aims to help users build confidence and self-awareness through daily interactive affirmations, and a community focused on well-being.

A new user joining Ray

Affirmation flow

My role
My role
My role

Led the UX strategy and design: delivering user flows, wireframes, high-fidelity screens, and prototypes that facilitated its launch in Summer 2024.

I worked on a team with a Lead Brand designer and the 2 co-founders.

Led the user experience strategy and design: delivering user flows, wireframes, high-fidelity screens, and prototypes that facilitated its launch in Summer 2024.

I worked on a team with a Lead Brand designer and the 2 co-founders.

Led the UX strategy and design: delivering user flows, wireframes, high-fidelity screens, and prototypes that facilitated its launch in Summer 2024.

I worked on a team with a Lead Brand designer and the 2 co-founders.

impact/outcomes
impact/outcomes
impact/outcomes

Executed strategic initiatives aligned with the founders’ vision, delivering design assets that enabled developers to launch the app in summer 2024

Executed strategic initiatives aligned with the founders’ vision, delivering design assets that enabled developers to launch the app in summer 2024

Executed strategic initiatives aligned with the founders’ vision, delivering design assets that enabled developers to launch the app in summer 2024

timeline
timeline
timeline

8 weeks

8 weeks

8 weeks

tools
tools
tools

Figma

Figma

Figma

how we got there

Learn & discover

  • Understand the user base

  • Extending the branding into a digitial environment

  • Comp analysis

Define & align

  • Define the primary objective of the app

  • Establish use cases

  • Define user journeys

Ideate & design

  • Sketch out wireframes

  • Ideate on auditory animations

  • Clickable high- fidelity prototype

Package & deliver

  • Production ready specs

  • Style guide and component library

  • Digital brand kit

how we got there

how we got there
how we got there

Learn & discover

  • Understand the user base

  • Extending the branding into a digitial

  • Comp analysis

Define & align

  • Define the primary objective of the app

  • Establish use cases

  • Define user journeys

Ideate & design

  • Sketch out wireframes

  • Ideate on auditory animations

  • Clickable high- fidelity prototype

Deliver & impliment

  • Production ready specs

  • Style guide and component library

  • Digital brand kit

Learn & discover

  • Understand the user base

  • Extending the branding into a digitial

  • Comp analysis

Define & align

  • Define the primary objective of the app

  • Establish use cases

  • Define user journeys

Ideate & design

  • Sketch out wireframes

  • Ideate on auditory animations

  • Clickable high- fidelity prototype

Deliver & impliment

  • Production ready specs

  • Style guide and component library

  • Digital brand kit

A new user joining Ray

Affirmation flow

A new user joining Ray

Affirmation flow

Learn & discover

Standing out in the marketplace

Standing out in the marketplace

Standing out in the marketplace

While the market has proven the effectiveness of daily affirmation apps—like Headspace, I Am, and Motivation—the founders of Ray were targeting the gap in how users interact with their affirmations.

Enter Ray: where affirmations are spoken aloud, supported by the collective audio of the Ray community. This concept draws from ancient practices such as Buddhist and Hindu mantras, Japanese Shingon Buddhism, and Native American rituals, which emphasize how speaking or chanting together amplifies energy, fosters unity, and deepens connection.

While the market has proven the effectiveness of daily affirmation apps—like Headspace, I Am, and Motivation—the founders of Ray were targeting the gap in how users interact with their affirmations.

Enter Ray: where affirmations are spoken aloud, supported by the collective audio of the Ray community. This concept draws from ancient practices such as Buddhist and Hindu mantras, Japanese Shingon Buddhism, and Native American rituals, which emphasize how speaking or chanting together amplifies energy, fosters unity, and deepens connection.

While the market has proven the effectiveness of daily affirmation apps—like Headspace, I Am, and Motivation—the founders of Ray were targeting the gap in how users interact with their affirmations.

Enter Ray: where affirmations are spoken aloud, supported by the collective audio of the Ray community. This concept draws from ancient practices such as Buddhist and Hindu mantras, Japanese Shingon Buddhism, and Native American rituals, which emphasize how speaking or chanting together amplifies energy, fosters unity, and deepens connection.

Designing for people seeking personal growth

Designing for people seeking personal growth

Designing for people seeking personal growth

We identified the Ray user as someone who is:

We identified the Ray user as someone who is:

We identified the Ray user as someone who is:

Pursuing self-growth

Pursuing self-growth

  • Looking for tools to to improve their life and find peace

  • Looking for tools to to improve their life and find peace

Time-sensitive

Time-sensitive

  • Looking for quick interactions, during buys days

  • Looking for quick interactions, during buys days

Seeking connection

Seeking connection

  • Looking to engage more than just reading or scrolling

  • Looking to engage more than just reading or scrolling

Diverse age, yet tech savvy

Diverse age, yet tech savvy

  • Ranging from young professionals to older individuals comfortable with mobile devices

  • Ranging from young professionals to older individuals comfortable with mobile devices

I used this information about our users to make sure the experience:

  • is quick and very easy to use

  • lends itself to emotional engagement

  • is exciting to come back to

I used this information about our users to make sure the experience:

  • is quick and very easy to use

  • lends itself to emotional engagement

  • is exciting to come back to

I used this information about our users to make sure the experience:

  • is quick and very easy to use

  • lends itself to emotional engagement

  • is exciting to come back to

Pursuing self-growth

  • Looking for tools to to improve their life and find peace

Time-sensitive

  • Looking for quick interactions, during buys days

Seeking connection

  • Looking to engage more than just reading or scrolling

Diverse age, yet tech savvy

  • Ranging from young professionals to older individuals comfortable with mobile devices

Aligning brand with interface design

Aligning brand with interface design

Aligning brand with interface design

Once we understood the user, the lead brand designer and I worked in parallel to approach the experience design, identifying themes of:

  • Calm and mindfulness: Soft gradients, serene colors that evoke peace

  • Nature: imagery or illustrations that connect with nature, especially the sun (“ray”)

  • Motivation: Positive content and language that create action and purpose

  • Playful simplicity: Approachable friendly images and type, while clean and minimal

Once we understood the user, the lead brand designer and I worked in parallel to approach the experience design, identifying themes of:

  • Calm and mindfulness: Soft gradients, serene colors that evoke peace

  • Nature: imagery or illustrations that connect with nature, especially the sun (“ray”)

  • Motivation: Positive content and language that create action and purpose

  • Playful simplicity: Approachable friendly images and type, while clean and minimal

Once we understood the user, the lead brand designer and I worked in parallel to approach the experience design, identifying themes of:

  • Calm and mindfulness: Soft gradients, serene colors that evoke peace

  • Nature: imagery or illustrations that connect with nature, especially the sun (“ray”)

  • Motivation: Positive content and language that create action and purpose

  • Playful simplicity: Approachable friendly images and type, while clean and minimal

Learn & discover

Learn & discover

Define & align

Prioritizing features for launch

Prioritizing features for launch

Prioritizing features for launch

I prioritized what to work on with the founders based on the timelines, goals, and requirements for an MVP launch. Starting with the core affirmation experience as the highest priority, to set the tone for the rest of the experience.

I prioritized what to work on with the founders based on the timelines, goals, and requirements for an MVP launch. Starting with the core affirmation experience as the highest priority, to set the tone for the rest of the experience.

I prioritized what to work on with the founders based on the timelines, goals, and requirements for an MVP launch. Starting with the core affirmation experience as the highest priority, to set the tone for the rest of the experience.

  • Core affirmation flow, including:

    • Visual for community audio

    • Design and interaction of record button

  • Demo mode (onboarding)

  • Sign-up flow

  • Landing page

  • Core affirmation flow, including:

    • Visual for community audio

    • Design and interaction of record button

  • Demo mode (onboarding)

  • Sign-up flow

  • Landing page

now
now
  • Sharing & social experience

  • Marketing material

  • Account pages and configuration

  • Sharing & social experience

  • Marketing material

  • Account pages and configuration

next
next
  • Gamification and habit tracking

  • Additional lifestyle content

  • Gamification and habit tracking

  • Additional lifestyle content

later
later
  • Core affirmation flow, including:

    • Visual for community audio

    • Design and interaction of record button

  • Demo mode (onboarding)

  • Sign-up flow

  • Landing page

now
  • Sharing & social experience

  • Marketing material

  • Account pages and configuration

next
  • Gamification and habit tracking

  • Additional lifestyle content

later

Mapping the experience

Mapping the experience

Mapping the experience

I created a detailed user flow, mapping out the full experience of a user, from initial download and sign-up, to the core affirmation flow, and finally the ability to share the experience.

I created a detailed user flow, mapping out the full experience of a user, from initial download and sign-up, to the core affirmation flow, and finally the ability to share the experience.

I created a detailed user flow, mapping out the full experience of a user, from initial download and sign-up, to the core affirmation flow, and finally the ability to share the experience.

We used this flow to align on the new user onboarding experience- identifying the order in which certain moments should occur, such us:

  • The “demo” mode taking place before any sign-up screens, so the user can experience how it works

  • The order and placement of necessary user permissions required

  • The transition from sign-up to existing user

We used this flow to align on the new user onboarding experience- identifying the order in which certain moments should occur, such us:

  • The “demo” mode taking place before any sign-up screens, so the user can experience how it works

  • The order and placement of necessary user permissions required

  • The transition from sign-up to existing user

We used this flow to align on the new user onboarding experience- identifying the order in which certain moments should occur, such us:

  • The “demo” mode taking place before any sign-up screens, so the user can experience how it works

  • The order and placement of necessary user permissions required

  • The transition from sign-up to existing user

Define & align

Define & align

The main challenge was going to be introducing this unique auditory experience in a way that is quick to learn, and engaging to use.

The main challenge was going to be introducing this unique auditory experience in a way that is quick to learn, and engaging to use.

The main challenge was going to be introducing this unique auditory experience in a way that is quick to learn, and engaging to use.

Ideate & design

Designing for engagement and simplicity

Designing for engagement and simplicity

Designing for engagement and simplicity

The affirmation screen should direct the user to a new focused space, and set the tone of their experience

The affirmation screen should direct the user to a new focused space, and set the tone of their experience

The affirmation screen should direct the user to a new focused space, and set the tone of their experience

What needs to take place in this experience

What needs to take place in this experience

What needs to take place in this experience

  1. The user will need to record their voice, which will be added to collective group. This means we’ll need:

    1. Clear audio: programming, and we can prompt users for best practice

    2. Proper pacing of the affirmation: Visual guidance

    3. Screening for inappropriate language: Back end programming (AI)


  2. The user will hear the community voice: which means we'll need visual feedback

  1. The user will need to record their voice, which will be added to collective group. This means we’ll need:

    1. Clear audio: programming, and we can prompt users for best practice

    2. Proper pacing of the affirmation: Visual guidance

    3. Screening for inappropriate language: Back end programming (AI)


  2. The user will hear the community voice: which means we'll need visual feedback

  1. The user will need to record their voice, which will be added to collective group. This means we’ll need:

    1. Clear audio: programming, and we can prompt users for best practice

    2. Proper pacing of the affirmation: Visual guidance

    3. Screening for inappropriate language: Back end programming (AI)


  2. The user will hear the community voice: which means we'll need visual feedback

Keeping this in mind, the first approach I took was to create a page that was a hybrid lander and affirmation page, to keep users oriented, while maintaining the focus on the affirmation.

The reason for the hybrid page is so that users that enter the app from a push notification can skip directly to this page and start the affirmation, while users that go through a standard app launch, would land on a home page first.

Keeping this in mind, the first approach I took was to create a page that was a hybrid lander and affirmation page, to keep users oriented, while maintaining the focus on the affirmation.

The reason for the hybrid page is so that users that enter the app from a push notification can skip directly to this page and start the affirmation, while users that go through a standard app launch, would land on a home page first.

Keeping this in mind, the first approach I took was to create a page that was a hybrid lander and affirmation page, to keep users oriented, while maintaining the focus on the affirmation.

The reason for the hybrid page is so that users that enter the app from a push notification can skip directly to this page and start the affirmation, while users that go through a standard app launch, would land on a home page first.

Personalized greeting and motivational message

Personalized greeting and motivational message

Personalized greeting and motivational message

Start button reachable by thumb

Start button reachable by thumb

A form of audio visualization to represent the community voice

A form of audio visualization to represent the community voice

Today’s affirmation front and center

Today’s affirmation front and center

Today’s affirmation front and center

The idea was that as the user starts the affirmation a visual shift would take place on the screen to represent a visual shift in their mind.

The idea was that as the user starts the affirmation a visual shift would take place on the screen to represent a visual shift in their mind.

The idea was that as the user starts the affirmation a visual shift would take place on the screen to represent a visual shift in their mind.

Everything except the affirmation begins to fade away.

Everything except the affirmation begins to fade away.

Record button changes state to give visual feedback

Record button changes state to give visual feedback

A new shade of color fills the screen in pace with the length of the affirmation, to representing the sun rising

A new shade of color fills the screen in pace with the length of the affirmation, to representing the sun rising

Affirmation becomes a karaoke style text to ensure the user follows the same pace as the community voice

Affirmation becomes a karaoke style text to ensure the user follows the same pace as the community voice

In the front and back of this experience would be a home page, and a post- affirmation page.

In the front and back of this experience would be a home page, and a post- affirmation page.

In the front and back of this experience would be a home page, and a post- affirmation page.

Home page

Home page

Affirmation flow

Affirmation flow

Post-affirmation flow

Post-affirmation flow

The home page welcomes users, provides the daily affirmation, and could feature a tracker to encourage engagement. The Post affirmation page celebrates completion, encourages sharing, and promote the next day’s affirmation.

The home page welcomes users, provides the daily affirmation, and could feature a tracker to encourage engagement. The Post affirmation page celebrates completion, encourages sharing, and promote the next day’s affirmation.

The home page welcomes users, provides the daily affirmation, and could feature a tracker to encourage engagement. The Post affirmation page celebrates completion, encourages sharing, and promote the next day’s affirmation.

What will this actually look like?

What will this actually look like?

The first concept I explored was a combination of a button that also would animate to visualize the community voice- in the style of a spinning record, parallel the idea of vinyl record playing, possibly in an abstract form that could match the intonation and peaking audio levels of speech.

The first concept I explored was a combination of a button that also would animate to visualize the community voice- in the style of a spinning record, parallel the idea of vinyl record playing, possibly in an abstract form that could match the intonation and peaking audio levels of speech.

The initial deep blue scheme represented the pre-sunrise stage of the morning, and would shift in color after completing the affirmation- but across the experience it created a colder feeling. So as the branding evolved to a warmer color palette, I adjusted the screen design to match that, also lowering the button back down to an accessible placement

The vinyl record strayed a bit from the concept, leaning too much into a music. After various other explorations, the brand designer and I landed on the idea of a sun as a the button- as this better aligned with the name of the app, Ray.

The vinyl record strayed a bit from the concept, leaning too much into a music. After various other explorations, the brand designer and I landed on the idea of a sun as a the button- as this better aligned with the name of the app, Ray.

The vinyl record strayed a bit from the concept, leaning too much into a music. After various other explorations, the brand designer and I landed on the idea of a sun as a the button- as this better aligned with the name of the app, Ray.

While pressing, the button would glow to indicate it’s recording and the affirmation starts

While pressing, the button would glow to indicate it’s recording and the affirmation starts

The sun rays would act as sound waves for visual feedback of the community voice

The sun rays would act as sound waves for visual feedback of the community voice

Changing the interaction to “while pressing,” also removed the need for a “stop” or “complete” button, simplifying the user effort.

Changing the interaction to “while pressing,” also removed the need for a “stop” or “complete” button, simplifying the user effort.

Changing the interaction to “while pressing,” also removed the need for a “stop” or “complete” button, simplifying the user effort.

The initial deep blue scheme represented the pre-sunrise stage of the morning, and would shift in color after completing the affirmation- but across the experience it created a colder feeling. So as the branding evolved to a warmer color palette, I adjusted the screen design to match that, also lowering the button back down to an accessible placement

The initial deep blue scheme represented the pre-sunrise stage of the morning, and would shift in color after completing the affirmation- but across the experience it created a colder feeling. So as the branding evolved to a warmer color palette, I adjusted the screen design to match that, also lowering the button back down to an accessible placement

What will this actually look like?

The first concept I explored was a combination of a button that also would animate to visualize the community voice- in the style of a spinning record, parallel the idea of vinyl record playing, possibly in an abstract form that could match the intonation and peaking audio levels of speech.

Giving users a demo

Giving users a demo

Giving users a demo

Letting users interact with the product to get a taste of it, is the best way to show why this product is unique. Since this demo would be the first interaction with this experience it needed to convey:

  • How to press the button and speak along to the text

  • That users would hear the community audio while recording

  • That microphone permission was needed to access their voice

Letting users interact with the product to get a taste of it, is the best way to show why this product is unique. Since this demo would be the first interaction with this experience it needed to convey:

  • How to press the button and speak along to the text

  • That users would hear the community audio while recording

  • That microphone permission was needed to access their voice

Letting users interact with the product to get a taste of it, is the best way to show why this product is unique. Since this demo would be the first interaction with this experience it needed to convey:

  • How to press the button and speak along to the text

  • That users would hear the community audio while recording

  • That microphone permission was needed to access their voice

My initial design provided explanations before users began the demo affirmation for two reasons:

Seamless Experience: Once the user presses and holds the record button, I didn’t want to interrupt their flow with permission requests or instructions

Permission Request: We needed to request microphone permissions before the user started recording. Explaining why permission is requested increases it’s acceptance by 12%, and up to 81% if the reason is compelling (Nielsen Norman Group).

However, because this page can easily be skipped, we decided to shift to a more interactive approach, and provide explanations right on the affirmation page to help with orientation.

My initial design provided explanations before users began the demo affirmation for two reasons:

Seamless Experience: Once the user presses and holds the record button, I didn’t want to interrupt their flow with permission requests or instructions

Permission Request: We needed to request microphone permissions before the user started recording. Explaining why permission is requested increases it’s acceptance by 12%, and up to 81% if the reason is compelling (Nielsen Norman Group).

However, because this page can easily be skipped, we decided to shift to a more interactive approach, and provide explanations right on the affirmation page to help with orientation.

My initial design provided explanations before users began the demo affirmation for two reasons:

Seamless Experience: Once the user presses and holds the record button, I didn’t want to interrupt their flow with permission requests or instructions

Permission Request: We needed to request microphone permissions before the user started recording. Explaining why permission is requested increases it’s acceptance by 12%, and up to 81% if the reason is compelling (Nielsen Norman Group).

However, because this page can easily be skipped, we decided to shift to a more interactive approach, and provide explanations right on the affirmation page to help with orientation.

Or

Or

Or

Or

Or

Or

I explored different styles of an onboarding experience, but ultimately they each felt too long to get through. We shortened this in a few ways:

  • We decided, that we didn’t need the this demo mode to actually record the user’s voice, so we could remove that permission from this process- and move that to the first real affirmation

  • We could move some of this information earlier to an onboarding screen or carousel before the demo

I explored different styles of an onboarding experience, but ultimately they each felt too long to get through. We shortened this in a few ways:

  • We decided, that we didn’t need the this demo mode to actually record the user’s voice, so we could remove that permission from this process- and move that to the first real affirmation

  • We could move some of this information earlier to an onboarding screen or carousel before the demo

I explored different styles of an onboarding experience, but ultimately they each felt too long to get through. We shortened this in a few ways:

  • We decided, that we didn’t need the this demo mode to actually record the user’s voice, so we could remove that permission from this process- and move that to the first real affirmation

  • We could move some of this information earlier to an onboarding screen or carousel before the demo

That left us with a small set of on screen instructions, accompanied by a simplified single tooltip that That left us with a small set of on screen instructions, accompanied by a simplified single tooltip that only appears after a delay of the user not starting the affirmation.

That left us with a small set of on screen instructions, accompanied by a simplified single tooltip that That left us with a small set of on screen instructions, accompanied by a simplified single tooltip that only appears after a delay of the user not starting the affirmation.

That left us with a small set of on screen instructions, accompanied by a simplified single tooltip that That left us with a small set of on screen instructions, accompanied by a simplified single tooltip that only appears after a delay of the user not starting the affirmation.

Converting users

Converting users

Converting users

One of the founder requirements was to launch the app as paid subscription rather than a freemium model. So for me, the focus of the sign-up flow was to soften the transition to the paywall, reducing friction points along the way, and ensuring users felt the value of what they are paying for.

One of the founder requirements was to launch the app as paid subscription rather than a freemium model. So for me, the focus of the sign-up flow was to soften the transition to the paywall, reducing friction points along the way, and ensuring users felt the value of what they are paying for.

One of the founder requirements was to launch the app as paid subscription rather than a freemium model. So for me, the focus of the sign-up flow was to soften the transition to the paywall, reducing friction points along the way, and ensuring users felt the value of what they are paying for.

Increasing the likelihood of accepting permission requests

Increasing the likelihood of accepting permission requests

Increasing the likelihood of accepting permission requests

Permission requests, like those for notifications, can often feel intrusive to users, but in this case they enhance the user experience. I implemented primer screens before each request to explain why the app was asking for permissions and how it benefits the user- which can increases it’s acceptance by 12%, and up to 81% if the reason is compelling (Nielsen Norman Group).

Permission requests, like those for notifications, can often feel intrusive to users, but in this case they enhance the user experience. I implemented primer screens before each request to explain why the app was asking for permissions and how it benefits the user- which can increases it’s acceptance by 12%, and up to 81% if the reason is compelling (Nielsen Norman Group).

Permission requests, like those for notifications, can often feel intrusive to users, but in this case they enhance the user experience. I implemented primer screens before each request to explain why the app was asking for permissions and how it benefits the user- which can increases it’s acceptance by 12%, and up to 81% if the reason is compelling (Nielsen Norman Group).

Highlighting features to increase value

Highlighting features to increase value

Highlighting features to increase value

To show users additional value, I included a screen with instructions for adding widgets and a screen that promoted sharing affirmations with social groups,

To show users additional value, I included a screen with instructions for adding widgets and a screen that promoted sharing affirmations with social groups,

To show users additional value, I included a screen with instructions for adding widgets and a screen that promoted sharing affirmations with social groups,

Although these are extra steps and screen in the flow, my assumption is that they provide a positive benefit, and create excitement for users to help encourage subscription once they get to that step.

Although these are extra steps and screen in the flow, my assumption is that they provide a positive benefit, and create excitement for users to help encourage subscription once they get to that step.

Although these are extra steps and screen in the flow, my assumption is that they provide a positive benefit, and create excitement for users to help encourage subscription once they get to that step.

Payment & celebration

Payment & celebration

Payment & celebration

The payment screen itself uses social proof by highlighting the number of users in the community, features the value propositions of the app, and features a relatable message to connect with potential subscribers.

The annual subscription is labeled with a badge as the “best value” option because it does offer saving. It was also important to communicate how to cancel the subscription. To protect users, it should be just as easy to cancel as it is to sign up.

The payment screen itself uses social proof by highlighting the number of users in the community, features the value propositions of the app, and features a relatable message to connect with potential subscribers.

The annual subscription is labeled with a badge as the “best value” option because it does offer saving. It was also important to communicate how to cancel the subscription. To protect users, it should be just as easy to cancel as it is to sign up.

The payment screen itself uses social proof by highlighting the number of users in the community, features the value propositions of the app, and features a relatable message to connect with potential subscribers.

The annual subscription is labeled with a badge as the “best value” option because it does offer saving. It was also important to communicate how to cancel the subscription. To protect users, it should be just as easy to cancel as it is to sign up.

Social proof

Social proof

Value proposition

Value proposition

Transparency and trust

Transparency and trust

Highlight savings

Highlight savings

Reliability and human touch

Reliability and human touch

Feedback and validating merssage

Feedback and validating merssage

Fun animation to match the mood and tone of the app

Fun animation to match the mood and tone of the app

Card and CTA to encourage engagement

Card and CTA to encourage engagement

Sharing and social engagement

Sharing and social engagement

Sharing and social engagement

From the landing screen, the share option is the primary action a user is directed to take.

From the landing screen, the share option is the primary action a user is directed to take.

From the landing screen, the share option is the primary action a user is directed to take.

The share modal slides up, and presenting users with a carousel of social assets to choose from that features their affirmation of that day- allowing them to personalize it to the style that suites them. The most popular sharing platforms are surfaced as a part of this screen for easy access.

The share modal slides up, and presenting users with a carousel of social assets to choose from that features their affirmation of that day- allowing them to personalize it to the style that suites them. The most popular sharing platforms are surfaced as a part of this screen for easy access.

The share modal slides up, and presenting users with a carousel of social assets to choose from that features their affirmation of that day- allowing them to personalize it to the style that suites them. The most popular sharing platforms are surfaced as a part of this screen for easy access.

What does the receiver experience?

What does the receiver experience?

What does the receiver experience?

I designed out the experience that hsould happen when a Ray asset is shared with a link attached- for example via SMS. In this scenario, that link would take the new user to a web-based platform where they can try a demo version of the app before being prompted to download it. This allows new users to experience the value of the app almost immediately without the immediate commitment of downloading it.

I designed out the experience that hsould happen when a Ray asset is shared with a link attached- for example via SMS. In this scenario, that link would take the new user to a web-based platform where they can try a demo version of the app before being prompted to download it. This allows new users to experience the value of the app almost immediately without the immediate commitment of downloading it.

I designed out the experience that hsould happen when a Ray asset is shared with a link attached- for example via SMS. In this scenario, that link would take the new user to a web-based platform where they can try a demo version of the app before being prompted to download it. This allows new users to experience the value of the app almost immediately without the immediate commitment of downloading it.

Those users that download the app from the web-based demo; would be linked to download the app and skip the demo in the app, taking them directly to the sign up flow (so they aren’t doing a demo twice).

Those users that download the app from the web-based demo; would be linked to download the app and skip the demo in the app, taking them directly to the sign up flow (so they aren’t doing a demo twice).

Those users that download the app from the web-based demo; would be linked to download the app and skip the demo in the app, taking them directly to the sign up flow (so they aren’t doing a demo twice).

Ideate & design

Ideate & design

Package & deliver

We delivered screens for the rest of the main journeys- as well as additional use cases for various sign-up and sign-in methods including email, social, or magic link sign-up and verification. I created reusable components for the founders to further explore future designs as needed in figma.

We delivered screens for the rest of the main journeys- as well as additional use cases for various sign-up and sign-in methods including email, social, or magic link sign-up and verification. I created reusable components for the founders to further explore future designs as needed in figma.

We delivered screens for the rest of the main journeys- as well as additional use cases for various sign-up and sign-in methods including email, social, or magic link sign-up and verification. I created reusable components for the founders to further explore future designs as needed in figma.

Affirmation Flow

Affirmation Flow

Sign-up flow

Sign-up flow

Sharing and social engagement

Sharing and social engagement

Package & deliver

Package & deliver

Wrap up

The app launched in the summer of 2024 with a majority of our designs. The ultimate goal was to provide the founders with deliverables they could use for the launch, along with repeatable frameworks for continued design and iteration—both of which we successfully achieved.

The app launched in the summer of 2024 with a majority of our designs. The ultimate goal was to provide the founders with deliverables they could use for the launch, along with repeatable frameworks for continued design and iteration—both of which we successfully achieved.

The app launched in the summer of 2024 with a majority of our designs. The ultimate goal was to provide the founders with deliverables they could use for the launch, along with repeatable frameworks for continued design and iteration—both of which we successfully achieved.

Key takeaways & final thoughts

Key takeaways & final thoughts

Key takeaways & final thoughts

It was awesome to get to come in on the ground floor of an early stage idea, and help bring it to life. I really enjoyed getting to work directly with the founders on their vision, and collaborating with a brand designer- as I learned how that early partnership can contribute to the overall experience. Additionally, designing for a new medium—audio—was a unique challenge, that I hadn’t explored before.

It was awesome to get to come in on the ground floor of an early stage idea, and help bring it to life. I really enjoyed getting to work directly with the founders on their vision, and collaborating with a brand designer- as I learned how that early partnership can contribute to the overall experience. Additionally, designing for a new medium—audio—was a unique challenge, that I hadn’t explored before.

It was awesome to get to come in on the ground floor of an early stage idea, and help bring it to life. I really enjoyed getting to work directly with the founders on their vision, and collaborating with a brand designer- as I learned how that early partnership can contribute to the overall experience. Additionally, designing for a new medium—audio—was a unique challenge, that I hadn’t explored before.

Key takeaways

Key takeaways

Key takeaways

Balancing User Needs with Stakeholder Goals: Adaptability is key, as sometimes requirements may not align with personal opinions or best practice- so developing strategies to remaining user centered, while meeting business needs is critical.

Working with partner disciplines: What works in brand marketing may not translate directly to app design. It’s important to adapt and be flexible to fit the product’s needs, ensuring both work cohesively- which we saw during this product design.

Balancing User Needs with Stakeholder Goals: Adaptability is key, as sometimes requirements may not align with personal opinions or best practice- so developing strategies to remaining user centered, while meeting business needs is critical.

Working with partner disciplines: What works in brand marketing may not translate directly to app design. It’s important to adapt and be flexible to fit the product’s needs, ensuring both work cohesively- which we saw during this product design.

Balancing User Needs with Stakeholder Goals: Adaptability is key, as sometimes requirements may not align with personal opinions or best practice- so developing strategies to remaining user centered, while meeting business needs is critical.

Working with partner disciplines: What works in brand marketing may not translate directly to app design. It’s important to adapt and be flexible to fit the product’s needs, ensuring both work cohesively- which we saw during this product design.

Future explorations

Future explorations

Future explorations

If I were to continue working on this project, the next step would be testing. I’d look at conversion rates and daily active user rates. I’d analyze usage rates of the demo experience and gather data from the sign-up flow to identify any points of friction.

Conducting contextual inquiries would also be valuable—exploring where and how people use the app, and what environmental factors impact the experience. For example:

  • Where are people most likely to use the app?

  • How does outside noise affect the experience, and should headphones be required?

  • Is the app meeting users’ needs, or could additional features enhance the experience?

  • Are static screenshots effective for social sharing, or would another format drive more engagement?

I would let user feedback guide part of the next steps. Aside from that- I would expand on other feature ideations that were not initially prioritized, like gamification strategies to encourage more engagement.

If I were to continue working on this project, the next step would be testing. I’d look at conversion rates and daily active user rates. I’d analyze usage rates of the demo experience and gather data from the sign-up flow to identify any points of friction.

Conducting contextual inquiries would also be valuable—exploring where and how people use the app, and what environmental factors impact the experience. For example:

  • Where are people most likely to use the app?

  • How does outside noise affect the experience, and should headphones be required?

  • Is the app meeting users’ needs, or could additional features enhance the experience?

  • Are static screenshots effective for social sharing, or would another format drive more engagement?

I would let user feedback guide part of the next steps. Aside from that- I would expand on other feature ideations that were not initially prioritized, like gamification strategies to encourage more engagement.

If I were to continue working on this project, the next step would be testing. I’d look at conversion rates and daily active user rates. I’d analyze usage rates of the demo experience and gather data from the sign-up flow to identify any points of friction.

Conducting contextual inquiries would also be valuable—exploring where and how people use the app, and what environmental factors impact the experience. For example:

  • Where are people most likely to use the app?

  • How does outside noise affect the experience, and should headphones be required?

  • Is the app meeting users’ needs, or could additional features enhance the experience?

  • Are static screenshots effective for social sharing, or would another format drive more engagement?

I would let user feedback guide part of the next steps. Aside from that- I would expand on other feature ideations that were not initially prioritized, like gamification strategies to encourage more engagement.

Wrap up

Wrap up

Ray

Ray

Ray

Ray