PawWalk: iOS and Android app, design and build
Prepared for PawWalk
- Investment
- From $23,760
- Timeline
- 12 weeks
- Payments
- 3 stages
What you need
Today owners book walks by text and pay by bank transfer, and nobody knows where the walk is until the dog comes home. You want one app where an owner books and pays in a few taps, sees the walker live on a map during the walk, and rates it afterwards, with a simpler side of the same app for walkers.
We propose to build it for iPhone and Android together in about 12 weeks, with a test version on your phone every Friday.
How it's built, and why
- React Native (with Expo): one codebase for iPhone and Android, so both ship together and later changes cost once, not twice
- Firebase for sign-in, the database and push notifications, on an account in your name
- Stripe for payments, including Apple Pay and Google Pay
- Live location only during a walk, shared with the walker's permission and stopped when the walk ends
- Weekly test builds through TestFlight (iPhone) and Google Play internal testing, so you try every feature on a real phone before launch
What's included
Design
- Screen flows for owners and walkersS-1
- Designs for every screen, on small and large phonesS-2
- A clickable prototype you approve before the buildS-3
Owners
- Sign-up, dog profiles and saved addressesS-4
- Booking a walk with a time slot and a walkerS-5
- Paying in the app, with receiptsS-6
- Live map during the walk, and a photo when it endsS-7
- Rating the walkS-8
Walkers
- Accepting and declining walksS-9
- Starting and ending a walk (which shares and stops location)S-10
- Earnings for the weekS-11
Release
- Testing on real iPhones and Android phonesS-12
- App Store and Google Play listings, privacy forms and reviewS-13
- Crash reporting and basic analyticsS-14
Not included
- A web versionX-1
- An admin dashboard beyond a simple bookings listX-2
- MarketingX-3
- App-store screenshots designX-4
What the app stores require
- Apple and Google review every release; the first review usually takes a few days, and that wait isn't counted in the timeline
- An in-app way to delete an account, privacy labels and a clear reason for asking for location: all included above
- Developer accounts in your name: Apple charges $99 a year and Google a one-time $25, paid by you, so you own the listings
Investment
Priced by phase, with a 10% contingency for store feedback and device-specific fixes (only invoiced if used). The two extras are optional.
| Task | Hours | Rate | Amount |
|---|---|---|---|
| Design · 32 h | $3,200.00 | ||
| Screen flows, designs and prototype | 32 | $100.00 | $3,200.00 |
| Owners · 110 h | $11,000.00 | ||
| Project set-up, builds and test distribution | 10 | $100.00 | $1,000.00 |
| Sign-up, dog profiles and addresses | 18 | $100.00 | $1,800.00 |
| Booking with time slots | 28 | $100.00 | $2,800.00 |
| Payments with Stripe, Apple Pay and Google Pay | 20 | $100.00 | $2,000.00 |
| Live map during walks | 24 | $100.00 | $2,400.00 |
| Ratings and walk photos | 10 | $100.00 | $1,000.00 |
| Walkers · 36 h | $3,600.00 | ||
| Walker side: accept, start and end walks, earnings | 26 | $100.00 | $2,600.00 |
| Push notifications | 10 | $100.00 | $1,000.00 |
| Release · 38 h | $3,800.00 | ||
| Testing on real phones and fixes | 24 | $100.00 | $2,400.00 |
| Store listings, privacy forms and review | 10 | $100.00 | $1,000.00 |
| Crash reporting and analytics | 4 | $100.00 | $400.00 |
| Optional extras | |||
| Walker payouts with Stripe Connect | 24 | $100.00 | +$2,400.00 |
| In-app chat between owner and walker | 20 | $100.00 | +$2,000.00 |
| Subtotal | $21,600.00 | ||
| Contingency (10%) | $2,160.00 | ||
| Total | $23,760.00 | ||
Timeline
About 12 weeks: design in weeks 1–2, building in weeks 3–10 with a test build every Friday, testing and store submission in weeks 11–12.
Payments
- To startOn approval$7,128.0030%
- Test build with booking and paymentsWeek 6$7,128.0030%
- Live in both storesWeek 12$9,504.0040%
Assumptions and exclusions
- You vet and onboard walkers; the app records who they are, not whether they're suitable
- Running costs (Firebase, maps, Stripe fees) are billed to your accounts; at launch they're usually small and grow with use
- Not included: a web version, an admin dashboard beyond a simple bookings list, marketing and app-store screenshots design
Questions you might have
- Why one codebase instead of two native apps?
For an app like this, React Native gives the same experience on both platforms for roughly half the build and maintenance cost. If a future feature needs native code, it can be added for that feature alone.
- What if Apple or Google rejects it?
We fix what the reviewer asks for and resubmit; it's covered by the contingency. Rejections are usually about wording in the listing or a permission explanation, not the app itself.
- Who owns the app?
You do: the code (in your repository from day one), the store listings (in your developer accounts) and all the data.
Terms
Invoices are due within 14 days. Two rounds of changes are included on the designs; work outside the agreed scope is quoted in writing before it starts. Ownership of the code and designs passes to you on final payment. We fix defects against the agreed scope free for 30 days after the app is live in both stores.
Next step
Approve below and we'll send the first invoice and book a two-hour workshop to map the owner and walker journeys.