ARFID & Picky Eaters: Pitaya / Case Study
Introduction
Problem
Solution
Persona
Name: Emily
Has ARFID - has very limited food preferences, because of that she has a hard time eating in social situations and is often anxious about food
Is self diagnosed (~56%)
Pronouns: She/Her (Most popular)
Location: USA (~65%)
Mobile OS: iOS (~55%)
Has made a list of food preferences at some point (~78%)
Would be willing to pay for an ARFID related app (~66%)
Data based on the ARFIDSupport Discord roles (n=1000+) and my own survey in this channel (n=37)
Context
My Role
I was single-handedly responsible for the initial conceptualization, research, design, development, and user outreach.
This deep involvement not only allowed me to thoroughly understand and address the needs of our target users, but also provided a comprehensive experience in transforming a digital concept into a completed product.
Technologically, I used Swift and SwiftUI to achieve a native iOS appearance and feel, prioritizing a seamless and intuitive user interface. For database creation and management, I utilized the GPT-4 API and Google App Scripts.
Business Model
The current version is fully free to use, it is meant to work as an MVP to validate the market. If there will be enough interest, I plan to add paid features such as a recommendation system.
User acquisition strategy
My user acquisition strategy was to reach out to the r/ARFID subreddit and ARFIDSupport Discord channel as well as other ARFID related communities.
During the beta phase I managed to get 53 contacts, out of which 33 were iOS users. 20 people installed my app, out of which I received 11 actionable feedbacks.
In this process I learned the importance of momentum - the moment I lost the most contacts was when I waited too long to invite them to try out the app.
MVP Mockup
For this project I iterated a lot on the actual prototype, but I also created a mockup to set a general scope for the features I plan to include.
Improvements from User Feedback
One invaluable approach I adopted during the testing period was inviting users for a discussion over a call instead of relying solely on written communication. This direct conversation provided me with a deeper insight into their requirements and challenges.
After one such discussion, I introduced an option that allows users to set a goal to try an item more than once, recognizing the significance of repetition in the food tasting journey. However, I was cautious not to push users too aggressively. Thus, I chose a stamp card approach—encouraging repetition without making it obligatory.
I also made it easier for users to add items to the database right away using GPT-4. I found that if they have to wait for an item to be added, they lose interest.
Results in the first week after MVP launch
400+
Downloads
350+
Created lists
100+
Lists with over 50 items
150+
Android users on the waitlist
Testimonials
u/laurenj2210
u/samante81
u/weirdsituati0n
u/NationalNecessary120
u/kush_faerie
u/SuperNarwhal36-5
What I Learned
- Momentum is crucial. People lose interest if you don’t keep them engadged.
- When working alone, it’s much easier to procrastinate and delay tasks. Having clear deadlines, a defined scope, and someone to hold you accountable is very valuable.
- Direct calls with users are more valuable than just written communication. It is crucial for early validation.
- When creating a product, it’s important to think about outreach channels and the core value you’re offering from the start.
- The most important thing is to keep moving forward, regardless of the speed and setbacks.