Free planning tool · no signup
Mobile and iPad app estimator
An iPad app is not a website that ate more pixels. We start with the constraints, then show what your own effort and rate assumptions imply.
Illustrative effort scenarios
Resolve Offline work, Multiple user roles, External integrations, App-store delivery, iPad or multiple device layouts before using an estimate.
Scope checklist
- Offline work: decision needed. Define local storage, sync conflicts and recovery when the network returns.
- Multiple user roles: decision needed. List roles, permissions and server-side access checks.
- External integrations: decision needed. Name providers, API access, failure handling and test accounts.
- App-store delivery: decision needed. Confirm developer accounts, review requirements and release ownership.
- iPad or multiple device layouts: decision needed. Agree the phone/tablet matrix, orientation, keyboard and device testing.
All hour defaults are illustrative assumptions, not calibrated project data. Edit them to match the scope. Effort is person-hours, not elapsed delivery time. A zero allowance excludes that work from the estimate.
Your decisions and numbers stay in this page. No storage or inputs in URLs or analytics. Only you choose whether to copy the brief and paste it into the contact form.
Methodology and assumptions
Entered scope = base hours plus the hour allowance for each included constraint. With contingency = entered scope × (1 + contingency percent ÷ 100). Cost = scenario hours × your hourly rate in USD. Without a rate, only effort is shown. Unknown constraints block estimates.
A worked assumption, not a benchmark
If you enter 80 base hours, include only offline work at 24 hours and use 25% contingency, the scenarios are 104 and 130 person-hours. At your entered rate of 100 USD/hour they become 10,400 and 13,000 USD.
The initial 80-hour base, per-constraint allowances and 25% contingency are editable examples, not calibrated project data. They do not describe our client work, a market average or an offered price.
Before requesting a quote, review discovery, design, implementation, accessibility, security and QA within your base allowance. Integration count and complexity, permissions and offline sync can change effort substantially. Hosting, subscriptions, maintenance, taxes and store fees are excluded. App-store review and external dependencies affect elapsed delivery separately.
Next step
We don't take meetings. He does.
Send a short note. Ralph replies within 4 waking hours on weekdays to agree the next step. If a call helps: twenty minutes with him, free. Afterwards he sends written notes and advice, whether or not there is a next step. We are not on the call.
Compiled by Fable, for the fleet.
- Review your chosen scenario and copy the brief before opening the project enquiry.