B2C · Mobile · Freelance

Parentapp

Turning a child psychology expert's knowledge into a viable mobile product — from zero to a clear value proposition, business model, and end-to-end design.

My role
Solo product designer
Context
Freelance · Istanbul
Period
May 2018 – Mar 2019
Platform
iOS mobile app
Intro Research Design Success

A popular expert, no product

The project owner was a well-known child psychologist with a large social media following and published books. He had a vision for a mobile app for parents, but no clear product direction, business model, or MVP scope to act on it.

I joined to help shape the idea into something buildable — and then to design it end to end.

Key challenges

  • The team had limited knowledge of modern product development and lean methodology
  • No existing business model or defined target audience
  • This was my first time designing a business model from scratch
  • Tight coupling between research, strategy, and design — all happening in parallel

Understanding parents before designing for them

We ran a three-stage discovery process to understand who we were building for, what they struggled with, and what the competitive landscape looked like.

01

Stakeholder interviews

Mapped the team's expertise, expectations, and what they knew about parents' problems. Aligned the team before talking to users.

02

Online surveys

Two rounds via the expert's Instagram account. First to identify demographics; second to uncover jobs, pains and expectations. Audience: 25–44 year olds with 1–2 children aged 3–5.

03

User interviews

8 interviews with parents, in-person and by phone. Synthesized into a customer profile to create a shared understanding of who we were building for.

04

Competitor review analysis

Analyzed 3 competing apps via 1-star and 5-star reviews to learn what parents love and what to avoid.

Three patterns stood out. Parents valued timely, expert-backed information they could access whenever a problem arose. They wanted to feel less alone. And they strongly appreciated hearing why a particular approach worked — not just what to do.


Every decision tied back to research

Before designing screens, we ran a business model workshop using the research outputs. We explored multiple value propositions, ran a SWOT analysis on different business models, and aligned as a team on a direction: free articles to attract, premium online courses to monetize.

Articles screen — the app's entry point

9:41▶▶ ▐▐
Articles
New article of the week · Added a day ago
Articles
Courses
Notifications

Each design decision was grounded in a specific research finding or business model requirement. Three examples:

User gain

Parents want to read research and case studies for the problems they're trying to solve — not just opinions.

Design decision

Articles are tagged with R (research) and C (case study) icons. The same color system carries through into article detail pages.

Jobs to be done

Parents are occupied with childcare, cooking, and housework all day — they can't always stop to read.

Design decision

All articles are made listenable. A bookmark feature lets parents pick up exactly where they left off.

Pain point

Parents feel like a failure when standard advice doesn't work with their specific child.

Design decision

Articles include an "If your child is..." component with personalized tips for different child types — hyperactive, distracted, and more.

Revenue model

"Articles act as top-of-funnel for course upsell. A free course lets parents experience quality before purchasing. A 30-day money-back guarantee reduces friction. Shareable course certificates drive viral growth."


From idea to buildable product

The project owner had an audience but no product. By the end of the engagement, he had a validated business model, a defined MVP scope, a clear target audience, and production-ready designs to hand to a development team.

1
Business model defined from scratch — value proposition, revenue streams, and go-to-market strategy
3
Research methods combined: stakeholder interviews, surveys with the expert's Instagram audience, and 1:1 user interviews
E2E
Full end-to-end design delivered — from information architecture to final UI, including all edge cases

Clearly communicating the scope of deliverables at the start is as important as the work itself — misaligned expectations create friction even when the output is strong.

The team's limited familiarity with lean product methodology was a constraint. Bringing everyone to the same mental model — with examples — was a prerequisite for good decisions.

Regular communication with the project owner isn't just courtesy — it's a design tool. Gaps in communication compounded ambiguity in already undefined territory.