From MVP to an app in production, with backend, integrations and an honest choice between native, React Native and PWA. For product teams.
Free first conversation · Reply within 1 business day
Consulta Já:
Android and iOS apps built with Ionic, Angular and TypeScript
Consulta Já:
Real-time scheduling and a platform with 1K+ concurrent users
Contas Casal (own product):
Offline-first PWA with ~8.8K automated tests
MPC:
Acknowledgment API consumed by the Android app; Java/Kotlin PR reviews
Consulta Já: Android and iOS apps built with Ionic, Angular and TypeScript
Consulta Já: real-time scheduling and a platform with 1K+ concurrent users
Contas Casal (own product): offline-first PWA with ~8.8K automated tests
MPC: acknowledgment API consumed by the Android app; Java/Kotlin PR reviews
The app idea is validated, but every quote recommends a different technology and nobody explains why.
The app exists, but it freezes when the connection drops and loses what the user typed.
The screens are done and the backend is not: login, notifications and the admin panel became another project.
Every iOS or Android update breaks a screen, and there are no tests to warn you before users do.
A native app (Kotlin, Swift) or a cross-platform one (React Native, Ionic), depending on performance requirements, device features and the team that will maintain it.
A documented REST API, authentication, role-based permissions and the database, built together with the app so both ends evolve at the same pace.
A web interface for your team to manage users, content and app operations, on top of the same data and rules as the API.
Local storage and a sync queue so the app works on an unstable connection, with conflict resolution defined in the spec.
Push notifications, real-time updates and delivery acknowledgment for the messages that cannot get lost along the way.
Automated builds, tests and submission to the App Store and Google Play through your company accounts, with versioning and release notes.
See also: AI agent development, custom software development, and desktop app development.
Healthcare SaaS for medical and dental practices: Android and iOS apps built with Ionic, Angular and TypeScript, a REST API and a proprietary real-time scheduling engine.
Related experience: backend that delivers promotion updates to in-store devices, with an acknowledgment API consumed by the Android app.
Facing a similar challenge? Tell us the problem and the timeline.
Free first conversation · Reply within 1 business day
Mobile app development is the building of iOS and Android apps together with the backend, the integrations and the store release. Hire it when the product needs device features such as camera, notifications and offline use, or when users expect to find it on the App Store and Google Play. Otherwise, a PWA may be enough.
We map users, main flows, integrations and device requirements. You receive the recommendation between native, cross-platform and PWA, the backend architecture, the plan and the estimate.
Specs, acceptance criteria and the flow of the main screens before the code. You approve what goes into the MVP, what waits and how each flow will be validated.
The main flow working on the device, connected to the real backend. You receive test builds to install on your phone and validate with users.
Remaining flows, integrations, notifications, admin panel and automated tests. You receive the app submitted to the stores and the backend in production. Apple and Google review on their own schedule.
Adjustments for new iOS and Android versions, fixes and new features, under a monthly retainer or handed over to your team, with documentation.
| Scope | Typical timeline | Engagement model |
|---|---|---|
| DiscoveryFlows, technology choice, backend architecture, plan and estimate | 1–2 weeks | Fixed-scope project |
| MVPThe main flow on the device, with the real backend and test builds | 2–4 weeks | Fixed-scope project |
| ProductionFull app, backend, admin panel and store submission | 6–12 weeks | Fixed scope or time & materials with a cap |
| Ongoing evolutionNew iOS and Android versions, fixes and features | Ongoing | Monthly fractional retainer |
Timelines are typical ranges. Discovery defines the scope and the estimate of each project; the contract can be in USD or BRL.
Want to know which format fits your project?
Free first conversation · Reply within 1 business day
AI goes into the app as a feature and into the engineering as a method. The rule is the same for both: nothing reaches production without a spec, tests and human review.
AI in the appAssistants, natural-language search and data extraction from photos and documents, depending on the use case.
Keys outside the appModel calls (Claude, OpenAI, Gemini) go through the backend, never through keys embedded in the app.
Cost under controlToken usage is measured per model and per feature, with limits enforced on the backend.
In the buildAI coding agents (Claude Code, Codex, Cursor, Copilot, OpenCode) implement from approved specs, and every merge goes through senior human review.
Quality gatesAutomated tests in CI and validation on real devices before each version sent to the stores.
User dataThe model receives only what it needs, and client data never trains models.
| Criterion | Native (Kotlin, Swift) | Cross-platform (React Native, Ionic) | PWA |
|---|---|---|---|
| When it makes sense | Maximum performance or heavy use of device features | The same product on iOS and Android, maintained by one team | Simple content and flows, with no dependency on the stores |
| Codebase | One per platform | One shared codebase, with native parts where needed | The same codebase as the web application |
| Device features | Full access to the APIs of each system | Access to most APIs, through libraries and native modules | Limited to what the browser exposes; varies by system |
| Distribution | App Store and Google Play | App Store and Google Play | Installed from the browser, through a link |
| Maintenance effort | Highest: two codebases and two specialties | Medium: one codebase, plus library updates | Lowest: updates like a website, with no store review |
The cost depends on five factors: the number of screens and flows, the platforms (iOS, Android or both), the backend required, the integrations and the offline and real-time requirements. We do not quote figures before knowing the scope. A 1–2 week discovery defines the estimate, and the contract can be fixed scope or time & materials with a cap, in USD or BRL.
For most business apps, cross-platform: one codebase in React Native or Ionic serves iOS and Android with a single team. Native, in Kotlin and Swift, pays off when the app depends on graphics performance, very specific device features or deep integration with the operating system. The recommendation comes out of discovery, with the criteria in writing.
Yes: we prepare the builds, the store listing, the screenshots and the submission. We recommend that the developer accounts belong to your company, so the app is published under its name. Approval depends on review by Apple and Google, which have their own rules and timelines; that is why we check the store guidelines during specification.
Yes, when the app needs them: we build the API, the database, authentication and the admin panel in the same project. If your company already has a backend, we integrate the app with it and document the API contracts. At MPC, we built the acknowledgment API consumed by the platform's Android app.
The app has to be tested, and sometimes adjusted, with each new version of the operating systems, the libraries and the store rules. We treat this as planned maintenance: automated tests point to what broke, and the fix ships in a new version. This work can continue under a monthly retainer or be taken over by your team, with the documentation we hand over.
Yes: assistants, natural-language search and data extraction from photos and documents come in through the backend, which calls the model and applies guardrails. Provider keys never live inside the app. In Contas Casal, our own product, the assistant uses several LLM providers with structured RAG, streaming and cost tracked per model.
Typical timelines are: discovery in 1–2 weeks, an MVP in test builds in 2–4 weeks and the production version in 6–12 weeks. Store review happens after submission, on a schedule set by Apple and Google. The biggest factors are the number of flows, the integrations and the offline requirements.
AI-focused IT consultancy
Senior engineering from discovery to delivery: whoever designs the architecture also writes and reviews the code.
Master Timm · Updated on
In the first conversation we look at the flows, the users and what already exists, and tell you plainly whether you need a native app, a cross-platform app, a PWA or no app at all.
Free first conversation · Reply within 1 business day