Is this a fit?
Create mobile apps for iOS and Android
Skills to bring or develop
- Programming
- UI/UX Design
- App Store Optimization
The starting sequence
- Learn app development
- Build portfolio apps
- Create demo projects
- Find clients
- Scale or build own apps
What the work involves
You need to be comfortable writing real code — Swift or Kotlin natively, or React Native/Flutter if you want to target both platforms from one codebase. This is not a hustle where you figure it out as you go on a client's dime. Before you pitch anyone, you need at least one working app you built yourself, even if it's simple. UI/UX intuition matters as much as the code; apps that look clunky get deleted in 30 seconds. App Store Optimization is a separate skill you'll need to learn — getting an app built is only half the job, getting it found is the other half. Expect to spend 2–4 months in skill-building before you're ready to charge anyone. If you're starting from zero programming knowledge, double that estimate.
Find your first customers
Treat this customer profile as a starting hypothesis. Talk to people in this role and find out what they already do, what it costs them, and whether they want help.
Role
Startup Founder
Problems to investigate
- Need technical co-founder
- Previous dev agencies expensive
- Dont understand tech requirements
- Worried about quality and timeline
Channels to test
- Upwork
- Referrals
- Product Hunt
First launch approach
Build 2-3 apps to showcase, then target funded startups
Ways to find your first customer
- Create portfolio of sample apps
- Offer discounted MVP builds
- Network in startup communities
- Partner with product designers
Shape the offer & delivery
These are example packages to adapt, not current market rates or promises of sales. Choose one deliverable, set a revision limit, and test the scope with a real buyer before expanding.
MVP App
$10,000-$25,000 example price
- Core features only
- Single platform
- Basic design
- 3-month timeline
Full App
$30,000-$75,000 example price
- All features
- iOS + Android
- Custom design
- Backend included
Enterprise
$100,000+ example price
- Complex functionality
- Integrations
- Ongoing support
- Team augmentation
Build and deliver the offer
Service delivery
Packages
Name
MVP Build
Deliverables
- Core-feature mobile app for iOS or Android
Timeline
6-10 weeks
Included in this example
- Up to 5 core screens/flows
- Basic backend/API
- App store submission support
Outside this example
- Both platforms simultaneously (unless using cross-platform framework)
- Advanced analytics integration
Name
Full Build
Deliverables
- Full-featured app across iOS + Android (cross-platform)
Timeline
3-5 months
Included in this example
- Full feature set per spec
- Push notifications
- Analytics integration
- App store submission for both platforms
Name
Maintenance Retainer
Deliverables
- Ongoing updates, OS-compatibility fixes, and new features
Timeline
Monthly, hours-based
Included in this example
- iOS/Android OS update compatibility
- Bug fixes
- App store review-cycle support
Client onboarding
Step
Client provides app concept, target platform(s), and any existing brand/design assets
Who handles it
client
Step
Confirm Apple Developer / Google Play developer accounts exist or get set up before build starts
Who handles it
client
Step
Agree on native vs. cross-platform (React Native/Flutter) approach based on budget and platform priorities
Who handles it
you
Step
Build a clickable prototype/wireframe for sign-off before writing production code
Who handles it
you
Kickoff conversation
- Confirm the single core user flow the MVP must nail — apps that try to do everything at launch rarely ship on time
- Walk through platform priorities: iOS-first, Android-first, or simultaneous
- Agree on backend requirements — does this need a custom backend or can it use an existing BaaS (Firebase, Supabase)?
- Set app-store submission timeline expectations — Apple review alone can take 1-2 weeks and reject for reasons outside your control
Your launch roadmap
Work through the phases at your own pace. Durations and task hours are estimates; client conversations, sales, and other outcomes depend on the response you receive. Growth and exit steps are optional later decisions.
0 of 9 tasks checked
01 · Skill Building 30 days · suggested pace
Complete course and build 3 practice apps
Tool examples: React Native, Expo
Planning allowance: 60 hours
Set up Firebase or Supabase for app backends
Tool examples: Firebase, Supabase
Planning allowance: 20 hours
02 · Portfolio Building 14 days · suggested pace
Create impressive apps for portfolio
Tool examples: React Native, Expo, Firebase
Planning allowance: 40 hours
Showcase apps with case studies
Tool examples: React, Vercel
Planning allowance: 10 hours
03 · Exit 60 days · suggested pace
Prepare your app development business for sale, acquisition, or hands-off operation
Create comprehensive standard operating procedures covering every repeatable process in your app development business — client onboarding, delivery workflows, billing, and support. A buyer needs to run this without you.
Target deliverable: Complete SOP handbook with video walkthroughs
Tool examples: Notion, Loom, Google Docs
Planning allowance: 12 hours · AI can assist; review the output
Record the questions this step raises for your business, location, and circumstances. Confirm requirements and assumptions with current official sources and a qualified professional before acting.
Target deliverable: Valuation estimate with supporting financials
Tool examples: Google Sheets, ChatGPT
Planning allowance: 6 hours · AI can assist; review the output
Organize all financial records, contracts, customer data, IP documentation, and legal documents into a virtual data room that a buyer or their advisor can review.
Target deliverable: Organized virtual data room
Tool examples: Google Drive, Google Sheets
Planning allowance: 10 hours
Identify every area where the business depends on you personally. Delegate, automate, or document each one. Test by taking 2 weeks off and measuring impact.
Target deliverable: Owner dependency scorecard (before/after)
Tool examples: Notion, Zapier, Slack
Planning allowance: 20 hours
Create a teaser document (blind profile) for your app development business and either list on marketplaces (Acquire.com, Flippa, Quiet Light) or reach out directly to 5-10 potential acquirers.
Target deliverable: Teaser document + 5-10 buyer conversations started
Tool examples: Acquire.com, Google Docs, Email
Planning allowance: 8 hours · AI can assist; review the output
Checking a task saves its checkmark in this browser. It does not run an AI agent or confirm a business result. Reset removes this guide’s checkmarks. Saved work does not sync between devices.
Tools, budget & effort
These are tools named in the original playbook, offered as examples to evaluate. Check current capabilities, pricing, licensing, and data handling with the provider before subscribing. Start with the tools you already have.
- React Native
- Flutter
- Firebase
Tools to evaluate
Item
A cross-platform framework (React Native, Flutter, or similar)
Why consider it
Building native iOS and Android separately doubles your delivery time — pick one framework and get fluent in it
Item
A backend-as-a-service (Supabase or Firebase)
Why consider it
Most client apps need auth + database + storage — do not build this from scratch per project
Item
A signed contract covering scope, app store submission responsibility, and post-launch support window
Why consider it
App store rejections and post-launch bugs are common — be explicit about who owns fixing them and for how long
Mobile App Development Framework
- Flutter
- React Native
- Swift (iOS native) / Kotlin (Android native)
Design and Prototyping
- Figma
- Sketch
- Adobe XD
Freelance Contract and Invoicing
- Bonsai
- HoneyBook
- Wave
Make the numbers your own
Include setup, subscriptions, selling, fulfillment, revisions, support, and your time. Use your actual inputs and compare a cautious case with a better case.
Open the experiment calculator →AI roles & prompt templates
Assign a clear job, provide approved inputs, and review the result. These are role and prompt ideas; this page does not run AI or connect your accounts.
Mobile Developer
Review this app permission flow and flag anything that will get rejected in App Store review
Backend Dev
Design a database schema for a user-generated content app with likes and comments
Test Engineer
Suggest a device/OS testing matrix for this app before submission
Copy a prompt, then add your context
Replace the bracketed placeholders. Use information you have permission to share, ask for sources, and check every factual or numerical claim.
Generate a client discovery questionnaire for a mobile app project
I'm a freelance mobile app developer scoping a new project. Help me write a thorough discovery questionnaire I can send to a prospective client before our first call. The app is for [iOS/Android/both]. Include questions covering: their target users and core problem being solved, must-have vs. nice-to-have features for v1, existing backend or API dependencies, their internal tech team (if any), timeline expectations, budget range, how they'll measure success at 90 days post-launch, and who owns final approval decisions. Format it as a numbered list with a brief explanation of why each question matters. Keep the tone professional but conversational — not a legal interrogation. Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
Write a project proposal and fixed-price estimate for a client
I'm a freelance mobile app developer and need to write a project proposal for a client. Here are the project details: [paste your discovery notes]. Write a professional proposal that includes: a one-paragraph summary of the problem we're solving, a phased scope broken into MVP and Phase 2, a clear list of what IS and IS NOT included (out-of-scope items), a fixed-price estimate with a payment milestone schedule (e.g., 30% upfront, 40% at design approval, 30% at launch), a realistic timeline in weeks, and a section on my process (discovery, wireframes, development, QA, launch). Flag any assumptions baked into the estimate. Keep it under 2 pages. Do not use jargon. The client is non-technical. Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
Debug a specific React Native or Flutter error and explain the fix
I'm building a mobile app using [React Native / Flutter] and I'm hitting this error: [paste the full error message and stack trace]. Here is the relevant code block: [paste code]. Explain in plain English what is causing this error, show me the corrected code with comments explaining each change, and tell me if this is a pattern I should watch for elsewhere in my codebase. If there are multiple possible causes, walk through each one. Do not just give me the fix — I need to understand why so I don't repeat it. Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
Write App Store and Google Play listing copy optimized for search
I've built a mobile app and need to write App Store (iOS) and Google Play (Android) listing copy that will rank well and convert browsers into downloads. Here's what the app does: [describe your app in 2-3 sentences]. Target user: [describe]. Top 3 problems it solves: [list them]. Competitor apps I've seen: [list 2-3]. Write: a 30-character app name with keyword (if possible), a 100-character subtitle (iOS) and short description (Google Play), a full long description (max 4,000 characters) with natural keyword integration, and 5 bullet-point feature highlights. Prioritize clarity and benefit language over feature language. Flag which keywords you embedded and why. Note any differences between the iOS and Android versions. Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.
What a working week could look like
This is an example cadence. Include time for customer conversations, review, and admin; reduce the scope to fit your available hours.
What
Chief of Staff check-in — review yesterday's build progress, name today's one hard problem
When
Daily · 15 min
What
Focused build session — feature development or bug resolution on current project
When
Mon/Wed/Fri · 3–4 hrs
What
Client communication — respond to messages, send progress update with screenshot or screen recording
When
Tue/Thu · 30 min
What
Portfolio and pipeline — update GitHub, review one ASO metric, follow up on one warm lead
When
Sat · 1 hr
Problems to plan for
Use these playbook prompts to question your plan. Pricing, channels, and delivery models should be tested with your own customers.
Underpricing because you're estimating hours, not value
Price fixed-fee per project based on value to the client and market rates, not your hourly estimate.
Skipping a written contract and starting work on a handshake
Use a template like those from Bonsai or AND.CO.
Building for both iOS and Android from day one when the client doesn't need it yet
In discovery, ask where their actual target users are. If they can't answer, recommend starting with one platform (usually iOS if targeting US consumers with disposable income). Cross-platform frameworks like Flutter can help, but they still add complexity. Launch one platform, validate, then expand.
Ignoring App Store review guidelines until submission
Read Apple's App Store Review Guidelines and Google Play's Developer Policy Center at the start of every project. Flag any gray-area features (user data, payments, content) to your client in writing before you build them. Test your app with Apple's TestFlight before final submission.
Taking on a project without a clear definition of 'done'
Define acceptance criteria in your contract: specific screens, features, and performance benchmarks that constitute a completed project. Include a revision limit (e.g., two rounds of feedback per phase). Anything beyond that is billed as a change order at your hourly rate.
Your first small test
- Choose one customer. Find five people who have the problem described in this guide.
- Show one useful sample. Ask about their current process, priorities, and objections.
- Offer a clearly scoped pilot. Agree on deliverables, a price to test, and what success means.
- Record the evidence. Track responses, costs, hours, and what the buyer actually used. Decide whether to continue, change, or pause.
Explore related ideas
Adapted from Ashley’s Waymaker side-hustle playbooks, imported October 15, 2026. This is a published snapshot, not a live connection to your Waymaker account. Source examples are planning material, not verified customer outcomes. Explore Waymaker.