App development
AC Alcateia builds React Native apps for Android and iOS: from the first version to store publishing, or taking over an app that already has users. One codebase, both platforms on the same version and technical decisions explained clearly.
What usually gets in the way
What decides whether it lasts lies underneath: data, integrations, publishing and the cost of the next feature.
Separate teams and budgets for Android and iOS, with one platform always lagging behind.
Accounts, certificates, store policies and reviews delaying the launch for weeks.
Crashes, slow screens and fear of touching the code because every change breaks something else.
What we build
Each area can be hired on its own or combined into a complete project.
From architecture to publishing: project structure, navigation, screens, integrations and developer accounts set up in your company's name.
When the idea still needs validation: the smallest app that already delivers value, live and in use, instead of months of building without feedback.
Taking over an app that already has users: new features, fixing what crashes, refactoring critical areas and tests on the flows that cannot break.
What the app needs to access to be useful: login, notifications, camera, code scanning, location, payments and company systems.
A stage that often delays projects: accounts, certificates, store policies, reviews, versioning and the updates that follow.
Who it is for
Teams that need to record, look up or check information on their phones, away from the office.
Founders and companies that want a first version in the stores and to learn from real users.
Apps in production that need evolution, stability or a technical team to carry them forward.
Benefits
Android and iOS evolve together from the same codebase, without doubling the maintenance effort.
Store accounts, code and keys stay in your company's name, with full access to everything that was built.
Organized architecture, clear conventions and tests on critical flows, with no dependence on a single person.
Builds you can install and test on your device throughout the project, not only at the end.
How we work
You tell us the problem, who will use the app and what already exists. The first conversation is free of charge.
A paid step after the first conversation: we define what goes into the first version, the integrations and the working format. Then the proposal puts scope and timeline in writing.
The app grows through short deliveries, with test builds on your device and continuous follow-up.
Store submission, review responses and ongoing evolution agreed by period or on demand.
Why us
Every technical decision is explained in plain language, including what it changes in timeline, cost and maintenance.
If the app needs an admin panel, an API or a marketing site, everything follows the same rules and the same identity.
Screens, integrations, back end, publishing and maintenance: what changes the price is stated upfront.
Technology
Mature tools, chosen for what the app needs rather than for trends.
Engagement
Frequently asked questions
Apps are quoted case by case. The price depends on the number of screens and flows, whether a back end exists, the integrations needed (payments, maps, login, internal systems) and the timeline. After the first conversation, which is free, comes the technical assessment, a paid step (R$ 250) that defines what to build and the estimate before any development proposal.
It depends on the scope, the integrations and the open decisions. That is why the timeline is defined in the assessment and written into the proposal. Deliveries happen in stages, so you follow the progress from the start.
React Native covers Android and iOS from one codebase, which usually means lower cost and both platforms always on the same version. Native development makes sense in very specific cases, such as games or heavy video editing. When React Native needs a feature that libraries do not offer, a native module can be written.
Yes. After the first conversation, the app goes through the technical assessment, a paid step: reading the code, understanding the architecture and stating clearly what can be reused and what costs more to maintain than to rebuild. Then we agree on the evolution plan.
Yes. The Apple and Google accounts are in your company's name, and the code and keys belong to you. Store fees are paid directly to Apple and Google.
Not necessarily. If an API already exists, the app uses it. If not, we assess the right path, from managed services to a custom back end, and that goes into the quote.
See also
Custom web systems, SaaS platforms, dashboards, API integrations and automation for your company’s operations. Tailored quotes from AC Alcateia.
Fast, responsive business websites and landing pages ready for Google, with SEO and lead tracking depending on the plan. Remote service across Brazil.
Strategy, content planning, editorial calendar and social media management for companies and professionals, with periodic reports and no empty promises.
Request a quote
Tell us the problem it solves and who will use it. The first conversation is free.
