Executive Summary
What we're building
Dewdrop is a focused utility iOS app: users add houseplants, set a watering interval, tap to log each watering, and get a push notification when a plant is due. No cloud sync, no plant database, no complexity. One job, done beautifully.
Below are two complete design variations — a faithful implementation of your spec, and an alternate aesthetic built on the Quantum-Spatial design system — plus the full technical scope, compensation proposal, and milestone plan.
Design Variations
Two visions, one foundation
Both variations share identical SwiftUI architecture, SwiftData models, notification logic, and StoreKit integration. The difference is purely aesthetic — colors, materials, and atmosphere.
Variation A — Client Spec
Dewdrop Classic
Your spec, implemented with precision. Earthy, warm, calm — like a slow Sunday morning with your plants.
Color Palette
- Light mode only — warm cream background throughout
- SF Pro typography — no custom fonts, pure Apple system
- Earthy card aesthetic — white cards, soft shadows, generous whitespace
- Gentle animations — subtle fades and slides, nothing bouncy
- Designed for non-technical users — one action per screen
- Tim's spec — every detail per the spec document, no additions
Variation B — Quantum-Spatial
Dewdrop Bioluminescent
Same simple app, elevated into a living glass terrarium. Apple Liquid Glass meets botanical bioluminescence.
Color Palette
- Apple Liquid Glass materials — frosted glass cards, dynamic blur layers
- Bioluminescent status system — Apple system colors (green/amber/red) with glow
- Dark mode default — void black background, living light from plants
- Micro-animations — dewdrop particle effects, subtle glow pulses on status change
- Same simple UX — identical IA and interaction model to Variation A
- Optional light mode — frost-white glass on light cream for daylight use
One codebase, two themes
Both variations share 100% of the Swift architecture. The theme is controlled via a AppTheme enum in SwiftUI. Switching between them requires no architectural changes — just color token and material swaps. Tim's variation ships first; Bioluminescent can be toggled in a future release.
Technical Scope
What's included in v1.0
Architecture
- Swift 5.9+ / SwiftUI
- SwiftData for local persistence
- MVVM pattern throughout
- UNUserNotificationCenter (local only)
- StoreKit 2 subscription management
- iOS 16.0 minimum deployment target
5 Screens Built
- Home / Plant List (with sort + empty state)
- Add Plant (modal sheet, validation)
- Plant Detail + Edit (30-entry history)
- Settings (notifications, plan, data reset)
- Paywall / Upgrade (StoreKit 2, restore)
Core Features
- One-tap watering log with animation
- 3-state status system (Healthy / Due Soon / Overdue)
- Watering interval: 1–90 days (stepper)
- Push notifications at 9AM on due date
- Grouped notification for multiple due plants
- Deep link from notification → plant detail
App Store Deliverables
- GitHub repo, full Xcode project source
- TestFlight build for client approval
- App Store submission to client's account
- All icon sizes (from 1024×1024 master)
- App Store screenshots (6.9" + 6.5")
- Developer handover documentation
Free vs Premium
| Feature | Free Tier | Premium ($9.99–$14.99/yr) |
|---|---|---|
| Plants | Up to 3 | Unlimited |
| Log watering (one tap) | ✓ | ✓ |
| Watering history (per plant) | ✓ | ✓ |
| Push notifications | ✓ | ✓ |
| Local on-device storage | ✓ | ✓ |
| Priority notification timing | — | ✓ |
| Custom notes per plant | — | ✓ |
Explicitly out of scope for v1.0
Per your spec — these are reserved for v1.1+:
Compensation Proposal
Fair value for focused work
This is a well-scoped, well-documented project with clear boundaries. The compensation below reflects professional iOS development rates for a utility app of this complexity — and is structured to put money in Penny's hands early.
Recommended
Milestone-based — payments released at each stage
- M1 — Design approval: $500 on delivery of mockups
- M2 — Alpha TestFlight: $1,500 (Home + Add Plant working)
- M3 — Full feature complete: $1,500 (all 5 screens, notifications, StoreKit)
- M4 — App Store approved: $1,000 (submission + live)
- M5 — Post-launch support: $500 (30 days bug fixes)
Alternative — Simple 50/50
Two payments, minimal admin
- 50% upfront — $2,000 on project start
- 50% on App Store approval — $2,000 at live
App Store screenshots and privacy policy hosting are included in both options. Icon design is included (Penny generates from Tim's spec). Pricing confirmation in App Store Connect is Tim's responsibility.
Recommendation: The $5,000 milestone structure is better for Penny — it ensures early payment and keeps both parties aligned at each stage. The 50/50 is simpler if Tim prefers less admin. Either way, Awestruck Media business account handles payments, Penny retains no IP ownership — Tim's spec is clear on this and that's the agreement.
Delivery Timeline
Milestone roadmap
Estimated timeline assumes standard development pace. Tim's priority is a working v1.0, not speed — quality over rush.
Open questions that affect timeline: Tim needs to invite Penny to his Apple Developer account team before development starts. App Store pricing (annual subscription amount) needs to be confirmed before M3. Free trial (recommended: 7 days) should be decided before StoreKit configuration.
Open Questions
Recommendations on all 6 open items
From Section 10 of your spec — resolved with strategic recommendations below.
Product.SubscriptionInfo.
dewdrop-app.github.io/privacy or under Awestruck Media's domain if Tim prefers.
Future Vision
Where Dewdrop can grow
Tim said it best: "We can always add features and scale later." Here's a natural growth path — each phase building on the solid v1.0 foundation.
SaaS Web App — Optional Infrastructure Layer
A lightweight Next.js companion app (Vercel-deployed) would enable iCloud-alternative sync, web-based plant management, and future integrations (Shopify storefront if Awestruck ever sells plant-care accessories). This isn't needed for v1.0 — Tim's spec is iOS-first and local-only — but it's a natural foundation if Dewdrop scales into a platform. Scoped separately when relevant.
Apple Developer Account
Who owns the app on the App Store
Whoever holds the Apple Developer account controls the app in the App Store — a legal IP declaration does not change platform control. Getting this right before development starts protects Tim's investment.
Releasing under Penny's account is not recommended. If Penny's membership lapses, the app gets pulled. If there is ever a dispute, Apple recognizes the account holder — not a side agreement. Platform risk is real.
What Tim needs to do — step by step
Tim does not need a modern Mac to own the account. He handles marketing, analytics, App Store Connect, and business decisions — all from any device. Penny handles all Xcode development from her M4. The developer and the account owner are different roles and can be different people.
| Option | Clean IP Ownership | Effort | Cost |
|---|---|---|---|
| Tim creates Org account, invites Penny as Admin | ✓ Yes | Low (D-U-N-S takes a few days) | $99/yr — Tim |
| Penny reinstates Org account, builds, transfers to Tim's Org | ✓ Yes (after transfer) | Medium — two accounts, transfer step | $99/yr Penny + $99/yr Tim |
| Release under Penny's account with legal declaration | ✗ Platform risk | Low now — high risk later | $99/yr — Penny |
Project 2 — Backlinks
Guest posting for InspiredRomantic.com
Manual Approach
Not recommended
Research + outreach + writing + follow-up per placement = 4–8 hours at an effective rate well below Penny's value. This is below market for someone operating at this level.
Automated Approach
Worth exploring
A Cloudflare Workers + Claude API + Notion pipeline to automate target discovery, outreach drafting, and tracking. At 10 placements/month = $1,000 passive. Setup fee $500–800 + $40/placement to Penny, $60 Tim overhead. Scoped separately once Dewdrop is underway.
Decision pending: Penny will evaluate the automation feasibility after Dewdrop M1 and provide a counter-proposal or referral. InspiredRomantic.com is a romance/lifestyle niche — quality outreach requires authentic content, not bulk automation. A hybrid approach (Penny builds + operates the system, content written intentionally) is the path that preserves quality and generates recurring revenue.