My Camellia: Privacy-First Fertility & Wellness App
Independent Product Development Case Study | User Experience, Privacy & Accessible Technology
The Inspiration: When Technology Creates More Frustration Than Help
My Camellia began with a conversation involving a friend whose wife was trying to become pregnant.
They had been experiencing difficulties conceiving and had sought medical advice. Despite their concerns, medical evaluations hadn’t identified an obvious problem.
Like many couples, they turned to fertility and cycle-tracking applications to help them better understand their reproductive health.
They discovered several applications that initially seemed promising. Some offered useful features and an experience that appeared to meet their needs.
But over time, frustrations emerged.
Features that had previously been available suddenly required paid subscriptions. Functionality they had become accustomed to using was moved behind paywalls. Advertising began appearing throughout the applications, interrupting what had previously been a relatively straightforward experience.
The applications were supposed to make an already challenging experience easier.
Instead, they were becoming another source of frustration.
That conversation sparked an idea.
What if I could develop an application that respected its users, protected their privacy, and remained genuinely useful without requiring a paid subscription?
That became the inspiration for My Camellia.
The Problem: Essential Features Shouldn’t Become Hostages to a Subscription
Subscription-based software isn’t inherently problematic. Developing and maintaining applications costs money, and businesses need sustainable ways to support their products.
The problem arises when users become dependent on features that are subsequently restricted or when the experience becomes increasingly intrusive.
For applications dealing with sensitive personal information, those concerns become even more significant.
Fertility and reproductive health information is deeply personal.
Someone using a fertility application shouldn’t have to worry constantly about intrusive advertising, unexpected restrictions, or whether an essential feature will suddenly require payment.
I wanted to approach the problem differently.
Rather than beginning with a monetization strategy and deciding which features users would need to purchase, I started with a more fundamental question:
What should someone reasonably expect from an application designed to help them manage such a personal aspect of their life?
My answer was straightforward: privacy, usability, consistency, and transparency.
1. Designing With Privacy as a Core Principle
Privacy was one of the guiding principles behind My Camellia from the beginning.
An application dealing with fertility and reproductive wellness requires a higher level of sensitivity than many everyday consumer applications.
Users may be recording information they would not ordinarily share with other people.
That creates an important responsibility for anyone developing the product.
I wanted privacy to influence the application’s design decisions rather than become something addressed only after development.
This meant treating the user’s personal information with care and ensuring that privacy remained a central consideration as the application evolved.
My goal was to develop a product where users could focus on their wellness rather than worry about how their information might be used.
2. Building an Application That Works Without Paying
One of the most important decisions I made was that My Camellia should be usable out of the box without requiring a paid subscription.
I didn’t want someone to begin using the application, become comfortable with its features, and then discover that those essential capabilities had been placed behind a paywall.
The core application is intended to remain accessible without payment.
This doesn’t mean every possible feature must be free.
Optional capabilities, such as PDF exports, can provide opportunities for monetization without restricting the fundamental experience.
The distinction is important.
Paying should enhance the experience, not be a requirement for using the application as intended.
This approach reflects a belief that sustainable product development and user-friendly pricing don’t have to be mutually exclusive.
3. Choosing an Advertising-Free Experience
Advertising was another concern that influenced the development of My Camellia.
In many free applications, advertising is treated as the trade-off for access.
But the presence of advertisements can be particularly intrusive when someone is using an application for personal health or wellness purposes.
I wanted My Camellia to provide an experience without advertising interruptions.
The objective was to keep the application focused on the user’s needs rather than competing for their attention.
This was a deliberate product decision.
I recognized that removing advertising would also remove a potential revenue source. However, I felt that a more focused and respectful user experience was consistent with what I wanted the application to become.
4. From a Personal Project to a Broader Product
My Camellia wasn’t originally conceived as a commercial product.
I started developing it to help someone I knew.
That gave the project a clear starting point: a real person, a real problem, and an understanding of what was frustrating about the alternatives.
As development progressed, I began considering how the application could serve a broader audience.
The underlying problems weren’t necessarily unique to my friend.
Other people could also benefit from a fertility and wellness application that prioritizes privacy, avoids advertising, and doesn’t restrict its essential functionality behind a subscription.
The project gradually evolved from a solution for one person into an application intended to be useful to others.
This required thinking beyond the original use case and considering how different users might interact with the product.
5. Balancing Product Development With Sustainable Monetization
One of the challenges in developing consumer software is deciding how to make the application financially sustainable.
I didn’t want to build a product that depended on intrusive advertisements or progressively restricting essential features.
Instead, I chose to explore a model where the core experience remains free while selected optional conveniences may be offered as paid features.
PDF exports are one example.
This creates a distinction between essential functionality and optional enhancements.
It also establishes a clearer expectation for users: the application should remain useful regardless of whether they choose to purchase additional features.
For me, that is an important part of building trust.
6. Making Product Decisions Around the User
My Camellia reinforced something I’ve encountered repeatedly throughout my career in Customer Support and Operations.
A product can have impressive technology and an extensive feature list while still delivering a frustrating customer experience.
Sometimes the problem isn’t what the product can do.
It’s how the business chooses to deliver it.
Unexpected paywalls, intrusive advertisements, and inconsistent access to functionality can undermine customer confidence.
When developing My Camellia, I wanted to avoid introducing those frustrations.
That meant thinking about product decisions from the user’s perspective:
-
Is the application useful without payment?
-
Does the experience respect the user’s privacy?
-
Are optional purchases clearly separated from core functionality?
-
Can users engage with the application without advertising interruptions?
-
Are product decisions being made with the user’s long-term experience in mind?
These considerations influenced the direction of the project.
What This Project Demonstrates
My Camellia represents several aspects of how I approach technology and product development.
Customer Empathy: Understanding the frustrations people experience with existing products and recognizing opportunities to improve their experience.
Problem Identification: Translating a real-world problem into a practical application concept.
Privacy-Conscious Product Design: Treating sensitive personal information as a central consideration in product planning.
Product Strategy: Making deliberate decisions about functionality, accessibility, and monetization.
User Experience: Prioritizing a straightforward, advertising-free experience that doesn’t depend on unnecessary interruptions.
Independent Application Development: Taking an idea that began with a personal conversation and developing it into a product intended for a broader audience.
Project Status: Under Development
My Camellia is a privacy-first fertility and wellness application currently under development through MRAB AI Labs Inc.
Inspired by the frustrations experienced by someone close to me, the application is being designed to provide an accessible, advertising-free experience without placing essential functionality behind subscription paywalls.
The core application is intended to remain free to use, with paid options limited to optional enhancements such as PDF exports.
What I Learned
My Camellia reminded me that the best application ideas don’t always begin with a market analysis or a complicated business plan.
Sometimes they begin with listening.
A friend described a frustrating experience. I recognized an opportunity to do something differently.
As I worked on the application, I found myself thinking not only about what features to include, but about what kind of relationship I wanted the product to have with its users.
Would the application respect their time?
Would it protect their privacy?
Would it remain useful without payment?
Those questions became as important as the technical development itself.
Throughout my professional career, I’ve focused on understanding customer problems and improving how organizations respond to them.
My Camellia gave me an opportunity to apply that same thinking directly to product development.
Good technology should make life easier, not create new frustrations for the people depending on it.
That’s the principle behind My Camellia.
My Camellia is an independent application development project associated with MRAB AI Labs Inc.
Website: mycamellia.app