What isn't in myCocoon on launch day

It is launch day, and the more useful post is the one about what is not in the app

myCocoon v1.0 is in the App Store today. The launch-day note about what shipped is the App Store page, with the screenshots and the bulleted feature list and the seven-day free trial. This is the other post. The more useful one. The list of features that did not ship in v1.0, written by the person who held them back, with the reason next to each.

There is a thing software companies do on the day they launch. They tell you everything the product can do. They show you the screens. The blog reads like a press release. Fine. It is also slightly dishonest by omission, because every one-zero release is also a list of decisions about what to leave out, and that list is more interesting than the one in the marketing copy.

What follows is that list. Five things this app does not do, on purpose. The reason next to each.

There is no community feed

The community feed is the most common feature in pregnancy apps and the one users most often ask for, and v1.0 does not ship one. Most major pregnancy apps lean on it for retention, and it works as retention. It also does the harm.

A community feed is the surface where rumours about symptoms become reassurance, where comparison loops happen, and where a 28-week-pregnant user reads a thread about somebody else’s loss at midnight and cannot stop scrolling. The Mozilla Foundation’s Privacy Not Included audit of The Bump flagged the app for broad data collection, the use of data resellers, targeted advertising, and possible sale of personal information. (Mozilla, “Privacy Not Included”) The 2021 FTC settlement with Flo over sharing fertility-tracker data with Facebook and Google is the same shape of problem on the other side of the same product. (FTC, 2021)

myCocoon ships instead with the private invited circle covered in a separate post on this blog. A small group, named by you, who can see what you choose to share. No public feed. No strangers. No moderation surface a team this size can staff safely. If the right shape of social does emerge, it will be quieter than a feed, with a clear answer to who is in the room.

There is no Apple Watch app, no Android, no iPad-native layout

myCocoon is iPhone-only on launch day, and that is a design decision, not a roadmap gap.

The cross-signal reads described in the post on reading HealthKit cleverly are deeply iPhone-architecture-bound. They depend on:

• Apple’s HealthKit background-delivery API, which has no Android equivalent
• A dual on-device data store that keeps raw health data out of iCloud, per Apple’s own HealthKit privacy rules
• Apple Intelligence’s on-device language model, used when cloud AI is off
• App Check + device attestation, which are platform-specific surfaces

Building the same product on Android is not a port. It is a different app, with different rules, written against a different SDK and a different privacy architecture. Android deserves to be built properly, when it is built. The dishonest move is to ship a thinner version on launch day to fill a feature box.

The Apple Watch app is the same conversation. The Watch is good at one job, logging a kick session from your wrist while the toddler is asleep on you, and it is bad at almost every other job a pregnancy app could throw at it. v1.0 does not ship a Watch app because there is not yet a clear answer to what the Watch surface should be. When there is, it will ship.

The iPad-native layout is on the list, behind the Watch.

There is no full postpartum mode in v1.0

The App Store description mentions postpartum mode rolling out across 2026. v1.0 ships with an early-access banner for profiles past their due date, and not much more.

Postpartum is harder than pregnancy. Pregnancy has a calendar, a recognised set of milestones, a finite shape. Postpartum has a recovering body, a newborn whose patterns reshape every two weeks, a mother whose mental-health risk window does not close at six weeks (ACOG defines the postpartum period as extending up to 12 weeks for most clinical purposes, with mental-health risk persisting longer). (Optimizing Postpartum Care, ACOG, 2018) Most pregnancy-and-baby apps treat postpartum as baby-tracking with a banner reminder to take care of the mother. myCocoon’s postpartum mode is meant to be the other way around: a mother-first mode where the baby’s logs sit inside the mother’s day, not on top of it.

I held that back from v1.0 because the wrong version of postpartum mode would be worse than no postpartum mode at all. The shipped early-access banner is honest about that. The full mode rolls out in stages across 2026, and your subscription carries through.

The app does not call a hospital for you

The contraction timer follows the 5-1-1 rule (contractions five minutes apart, lasting one minute, for one hour) which is the standard guidance for when a low-risk first-time pregnancy should head to hospital. (How to Tell When Labor Begins, ACOG patient FAQ) The app surfaces the rule. It does not place the call.

That restraint is on purpose. There is a version of this product that ships a “Call your hospital now” button when the timer crosses the threshold. It would be more impressive in a screenshot. It would also be a healthcare-gateway feature, with a duty-of-care surface myCocoon is not licensed to be, and a single button between you and a clinical decision that depends on factors the app cannot see (your provider’s preferences, your hospital’s intake protocol, whether this is a first or fifth labour, whether your waters have broken). The right next step is a phone call, made by you, after a glance at the timer. The app’s job is to make the timing legible. The decision is yours.

The crisis-pattern local check follows the same shape. If you type a phrase that matches a defined crisis pattern, the response is a screen of regional crisis resources, surfaced locally, with no model call and no network round-trip. The app is not the helpline. It is the surface that points you at the helpline.

There is no nutrition logging, no food database, no weight-loss framing

The hardest “no” in this list, because users will explicitly ask for it. Nutrition logging is a category-defining feature in fertility and pregnancy apps. v1.0 does not ship one.

The reason is that the iPhone Health app already accepts nutrition entries from any food-log app the user already trusts (MyFitnessPal, LoseIt, Cronometer, manual entry). myCocoon reads what is already in HealthKit. It does not ask the user to log nutrition twice. It does not introduce its own food database. It does not ship a weight-loss framing on a pregnancy product, which is a quiet failure mode in this category. The IOM weight-gain bands described in the HealthKit reading post read what your scale already says. They do not coach you toward a target. (Weight Gain During Pregnancy, National Academies Press, 2009)

If you want a nutrition log, the food category in the iPhone Health app is the right place. myCocoon will read it.

What this list is, and what it is not

Five decisions not to ship on day one. None of them rules anything out forever. The Apple Watch app and the Android build are roadmap items with no committed date. The full postpartum mode rolls out across 2026 in stages. The hospital-calling button and the public community feed are values calls, not feature gaps. Nutrition logging is a hard line, not a maybe.

The post about what is in the app is the App Store description. This post is the other one. If the negative space tells you something useful about the team that built it, that was the point.

§