Ennakko

Turns cycle patterns into planning cues without daily tracking or false certainty.

Soon on the App Store

Role:: Solo product designer and SwiftUI developer
Challenge:: Make cycle information useful without daily tasks or false certainty.

Research framed the product risks

I tested assumptions around planning value, recurring effort, privacy, trust and willingness to pay before choosing what the first version had to prove.

9-product benchmark
Mapped trackers and newer cycle-guidance products across input, paywalls, privacy and advice.
20+ interviews
Used concrete situations and abandoned habits to separate supported needs from contradictions.

The benchmark became three constraints

The first version had to make guidance contextual, show value before commitment and meet privacy expectations without a separate Ennakko account.

Ennakko — Original nine-product comparison in Ukrainian. Columns cover strengths, barriers, guidance, positioning, monetisation, reviews and implications for Ennakko.

Evidence narrowed the scope

The scope held to planning value, low recurring effort and visible model limits.

Planning already existed

When asked about the previous three months, 65.5% had often or sometimes changed a real decision because of their cycle.

Ennakko — Redrawn survey chart, 29 responses: often 8 (27.6%), sometimes 11 (37.9%), rarely 6 (20.7%), never 4 (13.8%).

Daily logging broke down

The follow-up on abandoned tracking pointed to forgetting, time and low payoff rather than one single dropout reason.

Ennakko — Redrawn survey chart, 21 responses, multiple selections: too much time 5 (23.8%), forgot 6 (28.6%), effort did not pay off 4 (19%), still using 8 (38.1%), another forgetting-related answer 1 (4.8%).

Advice needed context

Advice was the weakest signal: 58.8% called it generic, so the product needed personal patterns and clear model limits.

Ennakko — Redrawn survey chart, 17 responses: advice felt personal to 2 (11.8%), varied for 5 (29.4%) and felt generic to 10 (58.8%).

Two contexts replaced one generic user

Personas, JTBD and journey maps translated the same research into preparation and retrospective understanding.

Persona

Planner and Observer separated preparation needs from retrospective understanding.

JTBD

Help me translate cycle patterns into decisions without taking control of my schedule.

CJM

The journey map moved the product toward a quick preview, optional notes and history for appointments.

Ennakko — English customer journey map synthesis for the Planner context.

Research turned into three product decisions

Before
Required daily logging

Why
Forgetting a check-in should not interrupt planning.

After
Period history with optional notes
Before
A single predicted date

Why
An estimate needs room for variation and a way to inspect its basis.

After
Date windows with recorded inputs
Before
Separate registration screens

Why
Apple handles purchases; processing stays on device and private iCloud sync is optional.

After
No Ennakko account

A planning companion, not a diary

Ennakko gives people a useful preview from remembered dates, keeps daily input optional and makes the model’s limits visible beside calendar context.

The remaining product risk is whether people trust that distinction enough to return before real commitments and consider paying for it.

CaTarot Design + build · AI-assisted Tunto Product design · iOS · design-to-code