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.
My Big Year is your personal radar for birds you haven’t seen — on Big Years, Big Days, and Life Lists, across the places you actually bird.
$9.99
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 My Big Year: map the core Sports 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
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
My Big Year is your personal radar for birds you haven’t seen — on Big Years, Big Days, and Life Lists, across the places you actually bird. Built by a retired software developer, it was his tool for a Maine Big Year record (2021) and later helped him and his wife reach 708 species in the Lower 48 (2024). This release opens that workflow to birders across major regions — not just one state. List where you bird United States & Canada (states, provinces, counties / equivalents) ABA & ABA Continental AOU (37 countries & territories) Europe (50 countries) South America (16 countries) Create multiple lists at once. Mark a bird seen at the smallest circle and watch it ripple to higher lists you track. Find what’s next Unseen birds for Year, Day, or Life List Map pins + sortable tables Nearest / all reports for a species Directions, eBird checklists, field-guide links Mark Seen — off the right map and table See the bird Roughly 5,400 species images so you’re not chasing names alone. In the field Near Santa Fe? See nearby unseen birds. Need a Mountain Chickadee? Review recent reports, pick one, get directions and guides, then mark it seen. Early season: opportunistic ticks along your route. Late season: map clusters of remaining targets for smarter trips. Also included eBird import & spreadsheet-friendly export Custom and nearby search Dynamic hotspot maps & checklist history ABA Species by Code Sensitive Species guide Top 100 list links Built for serious listers who want eBird’s live data as a clear answer to one question: what haven’t I seen, and where is it right now?
Written user reviews are not shown here. Check current App Store reviews >
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 user engagement features
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Lack of customization options for events
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Basic user interface
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No community features
Validate with people who use this workflow before building.
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.