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.
App Overview
iPage 2
iPage 2 is a complete rewrite of iPage in the Apple Swift 4 programming language
$2.99 · In-app purchases
PRICE
$2.99
In-app purchases
BUSINESS MODEL
Paid
No overall Grossing estimate available
RATING
★ 4.8
46 ratings · Top 5%
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.
Build your own version
Build Kit
Make this idea yours
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Add to a Remix
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
Make it yours Optional
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
What's included17 files
A product spec, phased build plan, differentiation notes, and screen references.
- START_HERE
- AGENTS
- EVIDENCE
- SPEC
- BUILD_PLAN
- DIFFERENTIATION
- skills/
- screens/
Preview a sample Build Kit No email needed
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Screen plan
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.
Differentiate and validate
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.
Free quick prompt For a smaller starting point
Quick prompt
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
// RORK SYSTEM PROMPT
Rork plan preview for iPage 2: map the core Utilities 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.
Continue in Rork >
Affiliate link: CloneChart may earn a commission at no extra cost
Opportunities
AI-GENERATED OPPORTUNITY HYPOTHESES
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
Implement a categorization feature for tools.
Assumption to check: Difficulty in organizing multiple tools effectively.
Validate with people who use this workflow before building.
Hypothesis 2
Allow users to customize backgrounds and themes.
Assumption to check: Limited customization options for pages.
Validate with people who use this workflow before building.
Hypothesis 3
Provide more detailed logs and analysis of past page uses.
Assumption to check: Inadequate history tracking.
Validate with people who use this workflow before building.
Hypothesis 4
Introduce iCloud sync for better data management.
Assumption to check: No cloud sync options.
Validate with people who use this workflow before building.
App evidence
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
App Store description
iPage 2 is a complete rewrite of iPage in the Apple Swift 4 programming language. It maintains the same purpose as the original iPage which allows a user to send a message (page) to someone's pager from their iOS mobile device such as iPhone or iPad. iPage 2 is a separate app to iPage rather than just an update. There are several features with this app including: optimization for iOS 12 and the larger screen devices, preset messages, favorites, custom SNPP servers, and importing/exporting contacts. iPage 2 does not have ads. One major difference from the original iPage is that in iPage 2 a carrier must be assigned to each individual contact. Assigning carriers can be done: 1. At the time of entering/editing a contact's information 2. At the time of sending a page 3. In bulk via 'Settings' (Settings->Carriers->Manage) 4. Via CSV file import. The User Guide (Settings -> Documentation -> UserGuide) explains these options. DISCLAIMER: iPage 2 requires an internet connection and sends information to SNPP servers that are not in its control. Therefore, the user of iPage 2 is solely responsible for verifying that the pages sent from this app are received in a timely manner. The user will not hold iPage 2 or its developers responsible for complications that arise becasue of someone not receiving a page as desired.
Written user reviews are not shown here. Check current App Store reviews >
Screenshots
< Scroll to see more >
Build scope
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Define the first version
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Set boundaries
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Check the hard parts
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
SUGGESTED BUILD STACK
React Native
Expo
Zustand
react-native-async-storage
expo-router
BUILD KIT DIFFICULTY
Intermediate
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.
