Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
Rose Care Companion is the pocket reference for dedicated rose growers — a private journal that knows the difference between a once-blooming rambler and a remontant floribunda, and times the right care for each.
$3.99 · In-app purchases
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for Rose Care Companion: map the core Lifestyle workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: Limited plant care information available
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Lack of user engagement features
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: No reminders for plant care tasks
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Limited customization options for journal entries
Validate with people who use this workflow before building.
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Rose Care Companion is the pocket reference for dedicated rose growers — a private journal that knows the difference between a once-blooming rambler and a remontant floribunda, and times the right care for each. WHY YOUR ROSES DESERVE BETTER Every other "smart gardening" app treats roses as one generic plant. A once-blooming rambler gets the same prune-in-late-winter calendar as a remontant floribunda. A potted David Austin gets the same water schedule as a Knock Out in the ground. Generic advice gets generic results. Rose Care Companion built rose class into its bones. WHAT YOU GET - Browse 30+ named cultivars across all 9 rose classes — hybrid tea, floribunda, climber, rambler, shrub, miniature, patio, English (Austin), heritage. Class, breeder, year, bloom pattern, mature size, disease resistance — all on your device, no internet required. - Log ANY rose, not just the catalogue. Got a species rose, a heritage find, or a brand-new release that isn't listed? Add it by name and pick its class — the class drives the full care schedule, and you can record your own breeder, bloom colour, fragrance and notes. Edit everything later; changing the class rebuilds the schedule automatically. - Per-plant journal & photos. Log blooms, prune cuts, feeding, deadheading, pest sightings — and attach a photo to any plant or journal entry, straight from your camera or library. Each plant has its own scrollable timeline, thumbnails included. - Class-aware reminders. Pruning, feeding, deadheading, and watering reminders derive from your plant's class, your climate zone, and whether it's in a pot or in the ground. - Pest & disease quick reference. Cultural → organic → conventional treatment ladders for blackspot, mildew, rust, botrytis, aphids, Japanese beetles, sawfly larvae, spider mites, and more. Log a sighting on a plant in one tap. - Climate-zone aware. USDA zones 3–10 plus Köppen Cfb for NW Europe — pruning windows shift to match your spring. PRIVATE BY DESIGN - All garden data stays on this device. SwiftData store in the app sandbox. - No accounts, no sign-in, no cloud, no server. - No analytics, no ads, no third-party tracking SDKs. - Local notifications only — no push from a server. - Export your garden as JSON anytime via the share sheet — then import it back, or wipe everything, from Settings. Your data, yours to move. CONTENT POSTURE Per-cultivar notes from Wikipedia (CC-BY-SA, with attribution); pruning and feeding schedules built into class-level rules authored once per class. ONE-TIME PURCHASE Pay once, use forever. No subscription. No "premium" tier you have to dodge. REQUIREMENTS iPhone or iPad running iOS 17 or later. iPad-optimised. Made by GFC Studio in Belgium. Questions or feedback: [email protected].
Written user reviews are not shown here. Check current App Store reviews >
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
From the Build Kit assessment.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.