Zumaquero DevAn Android app that behaves like a bank's, not like a half-finished MVP
10+ years building production Android software for banking, retail and telecoms, now working for companies that need an app of their own.
Want the technical detail of the stack (Kotlin, Jetpack Compose, Clean Architecture) and the criteria for native versus cross-platform? It's on the page for native Android development.
El problema
An app that closes on its own, is slow to open or drains the battery for no reason loses users in the first session, and they don't come back. Many companies commission their first app from whoever offers the cheapest development and end up with code that has no architecture, no tests and nobody who can maintain it a year later without rewriting it from scratch. The result is an app that works in the demo but fails in production, with real users and real edge cases.
Cómo lo resuelvo
I build Android apps (and, when the project calls for it, iOS) with the same discipline I applied in production banking: clean architecture, tested code and technical decisions that are justified, not copied from a tutorial. I use Kotlin and Jetpack Compose as the main stack, on a Clean Architecture foundation that lets the app be maintained and extended without a rewrite every time requirements change.
Qué incluye
- Native Android development with Kotlin and Jetpack Compose
- Clean Architecture designed to scale without rewrites
- Automated tests on the app's critical logic
- Integration with your existing systems or APIs (your own backend or third-party)
- Publication on Google Play (and the App Store if the project includes iOS)
- Error and performance monitoring in production after launch
Entregables
- App published on Google Play (and the App Store where applicable)
- Documented source code and version control handed over
- Report on the architecture and technical decisions taken
- Panel or configuration for production error monitoring
Plazos y precio
Plazo
8 to 14 weeks, depending on functional scope and number of platforms
Precio
Desde 3.000 €
Preguntas frecuentes
Do you also develop for iOS or only Android?
My specialism is Android, with more than 10 years of production experience. For iOS I can develop with cross-platform technology when the project allows, or coordinate with a specialist if the scope demands it. I lay it out transparently for your case; I won't promise the same for both platforms if it isn't true.
Why not just use Flutter or React Native?
It depends on the project. For apps with complex logic, deep system integrations or demanding performance requirements, native Android gives more control and fewer long-term surprises. For simple MVPs or apps with simple logic on both platforms, a cross-platform solution can be the right choice. I decide this with you in the review, not before knowing the requirements.
What if the app fails in production once it's published?
I include error and performance monitoring from launch, to catch problems before users report them. Ongoing support after publication is handled through the maintenance service, separate from the initial development.
Do I need to already have a backend or an API to start?
Not necessarily. If you already have a backend, the app integrates with it. If you don't, we assess it in the review: it may require an additional phase or a backend specialist, depending on the project's complexity.
Who owns the code when the project ends?
You do. When the project finishes you receive the full source code, documented and with version control, with no dependency on me to keep running the app if you decide not to continue with maintenance.
¿Hablamos de tu proyecto de mobile apps?
Pide un diagnóstico gratuito y sin compromiso.