I found an existing app with the same name. Here's how a PM handles this — and why this makes my portfolio even stronger.
This happens all the time in a real PM role. I was deep into building something and discovered a competitor I'd missed in my initial research. I knew the worst thing I could do was ignore it, so I did exactly what I'm doing now: analyse it, learn from it, and pivot intelligently.
I did a hands-on review of the existing BabyDress iOS app (which prompted my name change to Snug Tonight), and here's what I found it does:
| Feature | Details | My Assessment |
|---|---|---|
| Digital Wardrobe | Parents add the actual clothes their baby owns (bodysuits, sleepsuits, sleep bags by TOG, swaddles, tops, bottoms, outerwear) | Clever Recommends from what you have, not generic items |
| Garment Catalogue | Beautiful illustrations for each clothing type with warmth labels (Light, Medium, Warm) and TOG ratings on sleep bags | Polished Very clear visual language |
| Age Stages | 3 stages: Newborn (0–3 mo), Infant (3–12 mo), Toddler (1–2 yr) | Good But stops at 2 years |
| Temperature Slider | Manual room temp input with color-coded slider (green → red), 10°C to 35°C range | Well-designed Intuitive interaction |
| Safety Notes | Expandable "Important Notes" and "Safety Information" sections referencing NHS guidelines | Responsible Builds trust |
| Dark Mode | Full dark mode with Light/Dark/System toggle in settings | Essential Same conclusion I reached |
| °C / °F Toggle | Onboarding step + settings toggle | Standard As expected |
| Gap | What's Missing | Why This Matters |
|---|---|---|
| ❌ No overnight forecast | Only considers current room temperature. No weather API, no overnight low prediction. Manual temp input only. | Critical gap This is the CORE problem. It's 22°C at 19:00 but 14°C at 03:00. Their app dresses for NOW, not the whole night. |
| ❌ No weather integration | Location is requested but only used for... unclear purpose. No visible forecast data on the main screen. | Missed They ask for location but don't surface overnight weather data to the parent. |
| ❌ iOS only | Native Apple App Store app. No Android. No web version. | Exclusionary Shuts out Android users (80%+ of South African market). Snug Tonight is cross-platform (iOS + Android) via React Native. |
| ❌ NHS-centric | Safety notes reference NHS (UK) guidelines specifically. Not localised for other markets. | Narrow South African, Australian, American parents need locally relevant guidance. |
| ❌ Onboarding friction | 6-step onboarding wizard including wardrobe setup BEFORE you can get any recommendation. | Friction A tired parent at 18:45 doesn't want to set up a digital wardrobe. They want an answer NOW. |
| ❌ Stops at 2 years | Toddler stage is 1–2 years only. | Incomplete Many parents of 2–3 year olds still need guidance, especially around blanket safety. |
| ⚠️ Questionable logic | At 20°C (ideal range), recommended a 0.2 TOG sleep bag — which is for hot weather (24°C+). Warning triangle shown on the sleep bag suggesting it knows this is wrong. | Accuracy Recommending from wardrobe is clever but can suggest wrong items if the parent's wardrobe is limited. |
| Feature | Existing BabyDress (iOS) | My Product |
|---|---|---|
| Overnight forecast | ❌ No | ✅ Core feature — dresses for overnight low (12AM–6AM window) |
| Weather API | ❌ Not visible in UX | ✅ Shows current temp + tonight's low + location (e.g., "Sandton") |
| Platform | iOS only (native app) | ✅ React Native mobile app — works on iOS & Android |
| Digital wardrobe | ✅ Add your actual clothes | ✅ V1: 5 categories, laundry tracking, substitute suggestions |
| Garment illustrations | ✅ Beautiful product images | ✅ SVG outfit illustrations (not emoji) |
| Onboarding | 6 steps before first use | ✅ 5 steps: Welcome, Location, Temp Unit, Baby Stage, Wardrobe (optional) |
| Morning log / Insights | ❌ None | ✅ Log sleep quality (stars), outfit feedback, wake-ups, notes; see patterns like "runs warm" |
| 4-tab navigation | Unclear structure | ✅ Tonight, Morning, Wardrobe, Settings |
| Dark mode | ✅ Yes | ✅ Yes, auto after 18:00 |
| Safety guidelines | ✅ NHS references | ✅ AAP + local (SA) guidelines |
| Time to first recommendation | ~3–5 minutes (setup required) | ✅ ~10 seconds (quick flow) |
| Age range in engine | 0–2 years (3 stages) | ✅ 0–3 years (3 age bands); onboarding: 3 stages (Newborn, Infant, Toddler) |
| Market focus | UK / NHS-centric | ✅ South Africa first, globally accessible |
| Pricing | Unclear | ✅ Free (1 child), Premium subscription (up to 10 child profiles) |
| "Dress for 3am" logic | ❌ Dresses for current temp only | ✅ Core differentiator — forecasts coldest point |
Finding a competitor with the same name meant I had to make two decisions: (1) should I change my product name? and (2) should I change my product direction? Let me address both.
I must rename. Having the same name as an existing App Store app creates confusion and legal risk. Here are options:
Simple, descriptive, memorable. "What should baby nightwear tonight?" Captures the overnight focus that differentiates us.
"Keep baby snug tonight." Warm, parental, action-oriented. Emphasises the nightly use case.
Play on "TOG" (the thermal rating) + "together" (parent & baby). Clever but might confuse non-TOG-aware parents.
Reverse of the competitor name. Direct, clear, but perhaps too similar.
Did I need to change what I was building? I decided to evaluate this:
My core insight — dress for 03:00, not 19:00 — is NOT addressed by the existing app at all. Their app is essentially a digital TOG chart that recommends from your wardrobe. Mine is an overnight weather-aware recommendation engine. These are meaningfully different products solving different layers of the same problem.
Their "digital wardrobe" concept is clever — recommend from what the parent actually owns. I’ve adopted this in V1 with 5 categories (Bodysuits, Sleepsuits, Sleep Bags & Suits, Swaddles & Layers, Sleep Layers), laundry tracking, and substitute suggestions.
| Aspect | Before (Original Plan) | After (Snug Tonight) |
|---|---|---|
| Name | BabyDress | Snug Tonight |
| Platform | Web tool concept | React Native mobile app (iOS + Android) |
| Positioning | Baby sleep clothing guide | Overnight baby sleep clothing guide — "dress for 03:00" + morning logging + insights |
| Key differentiator | Age-aware + temperature + forecast | Age-aware + temperature + overnight forecast + morning feedback + pattern detection |
| Wardrobe | Generic recommendations | ✅ V1: Digital wardrobe with 5 categories, laundry tracking, substitute suggestions |
| Morning features | Not planned | ✅ V1: Sleep log (stars + outfit + wake-ups + notes), insights, pattern detection |
| 4-tab navigation | Simple flow | ✅ V1: Tonight (recommendation) + Morning (log) + Wardrobe (manage) + Settings |
| Competitive framing | "Unlike static TOG charts and hardware" | "Unlike existing apps that only dress for the current temperature, Snug Tonight forecasts overnight lows, logs your results, and learns your baby's patterns" |
Everything else I'd built remained valid: my user persona, research findings, PRD logic, design wireframes, metrics framework, and roadmap. The overnight forecast was already my core differentiator — this pivot just let me lean into it harder.
| Lesson | Application |
|---|---|
| Always do an App Store / Play Store search | In my initial research, I checked websites and blogs but missed the App Store. Now I know to search every distribution channel — it's essential in any PM role. |
| Competition validates the market | Someone else built this because the problem is real. That was actually GOOD — it proved demand was there. The question isn't "is there competition?" — it's "is there differentiation?" and I had found mine. |
| Features ≠ differentiation | The existing app has a wardrobe system. I built a wardrobe too — plus overnight forecast, morning feedback, and insights. A focused insight combined with a complete feature set beats a feature list alone. |
| Platform choice IS strategy | They chose iOS native. I chose React Native for both iOS and iPadOS. In South Africa (80%+ Android), I knew my platform choice had to be strategic, not just technical. |
| Naming matters early | Always trademark-search and App Store-search your product name before you build. I caught this at Stage 4 — and I was grateful it wasn't at launch. |