Picking a nearshore app development company is mostly a risk-management problem. The code part is commoditized; what you are buying is senior judgment on platform tradeoffs, a team that can ship to the App Store and Play Store without six review rejections, and a partner that is awake when you are. This guide is written for US founders, product leads, and CTOs who have already decided to build a mobile app and are now shortlisting who should build it.
Typical production app budgets land between $80,000 and $350,000 with a 12 to 26 week delivery window. US on-shore agencies will quote $200 to $300 per hour for senior mobile engineers. A credible nearshore Brazilian partner will quote $60 to $120 per hour for the same seniority, overlapping most of your working day. The math only works if the partner is actually senior. The rest of this article is how to tell.
US agency vs nearshore Brazil vs offshore: when each wins
Location is not a universal win or loss. It depends on what you are optimizing for.
| Model | Blended rate (USD/hr) | Overlap with US ET | Best when |
|---|---|---|---|
| US on-shore agency | $180 to $300 | Full day | Regulated products (HIPAA, SOC 2 pre-audit), investor optics, under-8-week commercial deadlines |
| Nearshore Brazil | $60 to $120 | 6 to 8 hours | 12 to 26 week builds, real-time collaboration, product teams that do weekly demos, cost-sensitive scale-ups |
| Nearshore Mexico or Colombia | $55 to $110 | 7 to 9 hours | Same as Brazil, smaller engineering pool for niche mobile skills |
| Offshore India or Eastern Europe | $25 to $75 | 1 to 4 hours | Long backlog, staff-aug roles, async-tolerant specs, buyers with strong internal PM |
| Freelance marketplaces | $20 to $60 | Varies | Prototypes, one-off features, never a full production app |
The framing the best buyers use: on-shore is an insurance policy, offshore is a cost lever, nearshore is a collaboration choice. For a mobile app where the founder or PM wants to sit in weekly demos, respond to design questions same-day, and ship a TestFlight build the afternoon after a standup, Brazilian nearshore is usually the cheapest honest answer.
What separates a senior mobile agency from a commodity shop
Every agency site says "30+ apps delivered." That is noise. Here are the signals that actually separate a senior mobile shop from a body shop reselling offshore hours.
Senior engineers on the kickoff call
If the only person you talk to before signing is a sales lead or account manager, you are buying on trust. Insist on a technical kickoff with the actual engineer who will write the code, not a CTO who disappears after week two. On a senior mobile team, a staff iOS or Android engineer should be able to hold an hour-long call about push notification architecture, App Store rejection patterns, and state management tradeoffs without a slide deck.
Shipped apps with live store presence
Portfolio screenshots are free. Ask for App Store and Play Store URLs for apps the team actually shipped. Download them. Read the recent reviews. Check the update history, which is visible on both stores and tells you whether the team is actually supporting what they built. An agency that only shows you Figma mockups or a landing page with logos has a portfolio problem.
Design depth, not just coding
Apps like Calm, Duolingo, and Notion's mobile client are not successful because they are built in Swift. They are successful because someone obsessed over the motion design, haptics, onboarding flow, and tab bar hierarchy. A credible mobile agency has a product designer on every build who knows iOS Human Interface Guidelines and Material 3 by heart, not a web designer who happens to open Figma mobile frames.
Platform-specific answers
Ask: "How do you handle the difference between Apple's App Store privacy labels and Google's Data Safety form?" A senior mobile team has a two-minute answer. A generalist dev shop says "we fill out whatever the stores ask." For a deeper pre-signature checklist, see our 10 questions to ask before hiring a software development company.
Engagement models: dedicated squad, fixed-scope, or staff aug
The three nearshore engagement models are not interchangeable. Picking the wrong one is how projects blow up in month three.
Fixed-scope project
Best when the spec is clear, the design is mostly locked, and the buyer wants predictability. Typical for MVP builds of $80,000 to $180,000. Downside: every scope change goes through a change order, which is fine if you over-specified upfront and brutal if you did not. For a sharper view on MVP scoping, see our guide on MVP cost and how to validate your app idea first.
Dedicated squad
A fixed team of 3 to 6 engineers plus a PM and designer, billed monthly, working only on your product. Best when you have a live product that needs continuous iteration, a growing backlog, or uncertainty about what features to build next. Monthly cost for a Brazilian nearshore squad typically runs $25,000 to $55,000 depending on team size and seniority. This is the model most scale-ups use after an MVP goes to market.
Staff augmentation
You plug one or two engineers into your existing team. Best when you already have an in-house PM and tech lead, you just need hands. Rates look similar to the squad model on a per-engineer basis, but you absorb all the coordination overhead. This is the right answer less often than it is picked.
Team composition for a production mobile app
A realistic production build has more specialists than a web project of the same size. A bare-minimum mobile squad for a 16-week engagement:
- Product manager or delivery lead: runs the backlog, chairs demos, owns the client relationship. 50 to 100 percent allocation.
- Product designer: Figma, motion design, design system, store asset generation. 50 to 100 percent through design phase, dropping to 20 percent during build.
- Two to three mobile engineers: some combination of React Native, Flutter, Swift, or Kotlin depending on strategy. For a single-codebase cross-platform app, two React Native or Flutter engineers. For separate native builds, one iOS (Swift, SwiftUI) and one Android (Kotlin, Jetpack Compose).
- One backend engineer: APIs, auth, webhooks, Firebase or a custom Node or Go service.
- QA engineer: device coverage strategy, exploratory testing, regression suite. Part-time through build, full-time during beta.
- Occasional specialists: payments engineer for RevenueCat or StoreKit 2 integration, real-time engineer for WebRTC or socket workloads, AR specialist if the app uses ARKit or ARCore, ML engineer for on-device Core ML or TFLite models.
A common cost-cutting mistake is putting one senior engineer on top of two juniors and calling that a "three-person team." On mobile, where platform quirks are unforgiving, that ratio produces app review rejections, memory leaks, and a code review backlog that eats the senior's week. Insist on at least one senior per platform.
Realistic timeline: 12 to 26 weeks for a shipped app
Most credible mobile builds land in this range. Breakdown by phase:
| Phase | Duration | What happens |
|---|---|---|
| Discovery | 2 to 3 weeks | Requirements workshop, architecture decision records, platform strategy (RN vs Flutter vs native), API contracts, compliance scoping |
| Design | 3 to 5 weeks | Low-fidelity flows, high-fidelity UI, motion spec, design system, prototype user testing, App Store and Play Store asset kit |
| Build | 8 to 16 weeks | Weekly sprints, demo every Friday, TestFlight and internal testing track builds from week 2 onward |
| Beta and hardening | 2 to 3 weeks | Closed beta with real users, crash monitoring (Sentry or Bugsnag), performance tuning, App Store and Play Store submission prep |
| Launch | 1 to 2 weeks | Store submission, review cycles (expect 1 to 3 rejections even on a clean build), staged rollout on Play Store, phased release on App Store |
For a broader look at cost drivers across these phases, see our app development cost 2026 US buyer's guide.
Process and tooling: what nearshore collaboration actually feels like
The timezone question is the one every US buyer asks first. Brazil is 1 to 3 hours ahead of US time zones depending on daylight savings. Sao Paulo at 9am is New York at 7am and San Francisco at 4am. In practice, Brazilian engineers working a standard 9-to-6 overlap most of the US business day. That matters for mobile work in particular because design review and App Store submission debugging are collaborative activities, not async.
A typical weekly cadence on a serious nearshore engagement:
- Monday: planning meeting, sprint kickoff, 30 to 45 minutes. Client product lead attends.
- Daily standups: 10 minutes, written in Slack or held on Google Meet, client optional.
- Mid-sprint checkin: 15 minutes Wednesday, live preview of in-progress screens.
- Friday demo: 30 to 60 minutes, working build pushed to TestFlight and Play Console internal track. Recorded in Loom for stakeholders who missed it.
- Monthly roadmap review: 60 minutes, looking 8 weeks ahead.
Tooling that shows up on essentially every credible mobile engagement: Linear or Jira for the backlog, Figma for design handoff, Notion for specs and ADRs, Slack Connect for the shared channel, Loom for async walkthroughs, GitHub or GitLab for code review, Fastlane or EAS Build for CI, TestFlight and Play Console internal testing for distribution, Sentry or Bugsnag for crash reporting, Amplitude or Mixpanel for product analytics.
Mobile-specific compliance: what not to learn the hard way
Mobile compliance is narrower than web compliance but more brutal when it goes wrong, because the App Store will reject your app for minor infractions and the Play Store will pull it from listings.
- Apple App Store privacy labels: you declare what data you collect, whether it is linked to identity, and whether it is used for tracking. Lying here is the fastest way to get pulled from the store.
- Google Play Data Safety form: parallel requirement on Android, with its own taxonomy. A senior team fills both out consistently.
- COPPA: if your app targets users under 13, you need parental consent flows, no third-party ad SDKs without COPPA certification, and careful attention to data retention. Applies to both stores and is the most common reason kids' apps get suspended.
- HIPAA: if the app handles Protected Health Information, you need a BAA with any vendor that touches PHI (Firebase is not HIPAA-compliant by default; you need a signed BAA with Google Cloud, and your backend needs its own controls). Most nearshore teams have shipped HIPAA apps; ask for specifics.
- CCPA and GDPR: consent banners, data deletion flows, regional data residency if you serve EU users.
- PCI-DSS: if you take card payments in-app, Apple and Google strongly prefer you use Apple Pay, Google Pay, or a tokenized provider like Stripe. Rolling your own card form on mobile is a bad idea.
Hidden costs buyers forget
Beyond the engineering invoice, these line items show up and surprise first-time app buyers:
- App Store Developer Program: $99 per year (Apple), $25 one-time (Google). Trivial, but must be in the client's name, not the agency's.
- Push notification vendors: OneSignal, Airship, or Braze. OneSignal has a generous free tier; Airship and Braze start at $10,000+ per year for commercial volumes.
- RevenueCat: for in-app subscriptions and purchases. Free up to $2,500 monthly tracked revenue, then 1 percent of tracked revenue.
- Crash reporting: Sentry starts at $26 per month, Bugsnag starts at $59 per month, scales with volume.
- Analytics: Amplitude and Mixpanel both have free tiers but typical app-scale usage runs $100 to $1,000 per month.
- Device testing: BrowserStack or Sauce Labs if you want scaled device coverage, roughly $150 to $500 per month.
- OS compliance updates: every iOS and Android major release forces SDK updates, privacy manifest updates, and occasional API migrations. Budget $5,000 to $15,000 per platform per year just to keep the app alive.
- App Store Optimization: screenshot design, keyword research, localized store listings. Either $2,000 to $10,000 up-front or an ongoing ASO retainer.
How to vet a mobile agency: a 10-point checklist
Bring this list to any shortlisted partner. A senior agency will happily go through it; a commodity shop will hedge.
- Show me App Store and Play Store URLs for three apps your team shipped in the last 18 months. Let me read the reviews.
- Who will be on my kickoff call? Show me LinkedIn profiles. Will the senior engineer on that call still be on the project in week 12?
- Walk me through a time an Apple review rejected one of your apps. How did you handle it?
- How do you decide between React Native, Flutter, and native for a given project? Give me the criteria.
- What is your approach to push notifications, deep linking, and analytics instrumentation? I want specifics, not vendor names.
- How do you handle App Store privacy labels and the Google Play Data Safety form? Show me one you filled out recently.
- What is your release cadence post-launch? Weekly? Biweekly? How do you handle phased rollout and staged release?
- Who owns the source code? Read me the IP clause in your MSA.
- What happens if the senior engineer on my project leaves your company mid-engagement?
- Give me the names of two past clients I can call. Not testimonials, actual phone numbers.
If the partner cannot answer these crisply, keep shopping.
Red flags to walk away from
- Rates below $40 per hour for senior mobile engineers. The math does not work. You are either getting juniors billed as seniors, rotated engineers you never meet, or a broker reselling offshore hours at a markup.
- Zero live App Store or Play Store apps. If everything in the portfolio is "internal tools" or "under NDA," you are the test case.
- "We can do anything" generalists. Mobile is a specialty. If the agency splits time equally between Shopify stores, WordPress sites, and mobile apps, their mobile depth is thin.
- No senior engineers on sales calls. If you only meet engineers after signing, you have no leverage to reject the team you actually get.
- Fixed-price quotes on undefined scope. A real fixed-price engagement starts with a 2 to 3 week discovery that produces the spec. Anything else is a guess dressed as a commitment.
- Reluctance to sign a source code escrow addendum. Senior shops are comfortable with escrow. If they refuse, ask why.
Contract structure: MSA, SOW, IP, and escrow
The contract pattern that works cleanly with a Brazilian nearshore partner:
- Master Services Agreement (MSA): governs the relationship, IP assignment, confidentiality, warranties, limitation of liability, governing law.
- Statement of Work (SOW): per-project, defines scope, milestones, acceptance criteria, price, and payment schedule. For a 16-week build, 3 to 5 milestones with clear acceptance tests per milestone is the norm.
- IP assignment: you own the code, design, and all derivative works on payment. This should be explicit in the MSA, not buried in boilerplate.
- Source code escrow (optional): for enterprise buyers or when the engagement is strategic. Costs $1,500 to $3,000 per year through a third-party escrow provider.
- US tax forms: the Brazilian partner should provide a W-8BEN-E so you can classify the payment correctly. They are not a 1099 vendor; they are a foreign entity, which simplifies your side.
- Currency and payment: pay in USD via wire or ACH. Most Brazilian agencies invoice in USD directly.
Why Brazil specifically, not generic LATAM
The Brazilian software market is concentrated in five ecosystems: Sao Paulo, Rio de Janeiro, Belo Horizonte, Florianopolis, and Curitiba. Collectively they produce more senior mobile engineers than the rest of Latin America combined. English fluency at senior levels is strong and improving; engineers who have worked on US-facing products for more than two years generally lead calls in English without friction.
Tax and legal structure for a US buyer is clean: the Brazilian entity invoices in USD, you pay by wire, the W-8BEN-E classifies the relationship, no 1099 is required. Brazilian labor law is friendlier to long-term dedicated-squad relationships than a lot of offshore jurisdictions, which reduces team rotation risk. Cultural alignment with US B2B norms (direct feedback, demo-driven cadence, comfort with disagreement) is higher than most buyers expect.
Where FWC fits
At FWC Tecnologia, our typical mobile engagement is a 12 to 20 week dedicated squad working on iOS, Android, or both via React Native. We have shipped 30+ apps since 2020 across fintech, logistics, agribusiness, service management, e-commerce, and AI and automation. We are based in Cuiaba, Brazil and run engagements in US business hours. Project scopes typically run 30 to 120 days for a first shipped build, with dedicated squads continuing beyond that. If you want a concrete scope and price for your app, we put together a detailed proposal in 48 hours.
Ready to scope a mobile build with a nearshore partner?
If you have read this far, you have a sharp mental model of what a credible nearshore app development company looks like: senior engineers on every call, shipped store apps you can download today, clear answers on compliance and platform tradeoffs, engagement models matched to your actual situation, and a contract that protects your IP. The rest is matching the framework to a real partner.
The fastest way to test any partner, including us, is a scoping call. Request a mobile app proposal with a one-paragraph description of what you want to build and your rough timeline. Or go straight to contact if you want to ask questions first. You can also browse our shipped apps to see the verticals we actually work in.