What Our Android App Development Includes
- screen design based on Material Design, with your brand colors, fonts and illustrations on top of familiar Android patterns;
- Kotlin development with Jetpack Compose, including gradual adoption of Compose in older projects;
- device features: Google Pay, background location, camera, fingerprint login, notifications and data sharing with other apps;
- work-device support: built-in barcode scanners, receipt printers, scales, offline mode and kiosk mode;
- a backend and API with an admin panel, or a connection to your existing ones, including your CRM, accounting system, payment providers and shipping carriers;
- testing on phones from different manufacturers, in dark mode, with a large system font and on narrow budget screens;
- Google Play publishing: store listing, screenshots, data safety form, content rating and gradual rollout.
Customer Apps and Employee Apps
Customer apps cover catalogs and ordering, loyalty programs, booking and customer accounts. What matters most is an easy interface, fast startup and well-handled notifications.
Work apps for couriers, warehouse staff, sales reps or field service engineers have different requirements: offline work with sync once a connection is available, scanning through the terminal's built-in scanner, kiosk mode, and central updates across all company devices. For tasks like these, native Android is often the most reliable option. These apps can be installed directly on devices without publishing to Google Play.
When Another Route Makes More Sense
We advise against native Android if:
- you need both platforms at once and the features are standard, in which case a cross-platform app with a single codebase is more cost-effective;
- your audience mostly uses Apple devices, in which case it is smarter to start with an iOS version;
- the app only needs to let customers browse a catalog and submit a request, which a well-built mobile website often handles better.
New App or Improving an Existing One
For a new app, we start by choosing the target devices and the minimum Android version, since that determines which features are available and how much testing is needed. An existing app gets an audit first: how much code is still in Java, how old the libraries are, crash reports and compliance with current Google Play requirements. Then we propose a plan of what to fix right away and what to modernize gradually between releases.
Google Play Publishing and Support
We recommend registering the Google Play developer account in your company's name, so the app, its analytics and its reviews belong to you. We roll out new versions gradually: first to a small percentage of users, and to everyone once crash reports look clean. After launch, we can take the app on for support and ongoing development: monitoring errors, keeping up with new Google Play requirements and adding features.
What We Need From You
- The list of devices the app must run on: modern phones only, or also older models, tablets and terminals.
- Documentation or access to the systems the app connects to.
- Details of external hardware, if the app works with scanners, printers or payment terminals.
- For an existing app: source code, repository access and crash reports.
What Affects the Cost
- Device list: modern smartphones only, or also older models, tablets and specialized terminals.
- Server side: we connect to your API or build the backend and admin panel from scratch.
- Background and offline work: location tracking, data queues and syncing.
- Hardware: scanners, printers, payment terminals and other external devices.
- Code condition, for existing apps: the amount of Java code, outdated libraries and test coverage.
We provide an exact estimate after reviewing your requirements and show you the stages the work breaks down into.
Frequently asked questions
Will the app work on older phones? That depends on the minimum Android version we choose together. The older the devices we support, the more limitations and testing there are.
Can the app be installed without Google Play? Yes. For internal company apps this is standard practice: they are installed directly on work devices.
Do we have to rewrite our old Java app? Not necessarily. New parts can be written in Kotlin, and the old code migrated gradually as you get to it.
Will the app work on devices without Google services, such as Huawei phones or Amazon Fire tablets? Yes, but features that depend on Google services, such as push notifications, maps and Google sign-in, need to be implemented separately for them. We discuss this at the start.
Can we add an iPhone version later? Yes. The server, user flows and design will already be in place, so an iOS version usually takes less work. Sometimes at that point we recommend considering a shared codebase for both platforms.
Why Promodex
Promodex has delivered 750+ projects since 2015. Android apps in our portfolio include Fuelio, Idram, My Viva and List. UX, design and development are handled by our full-time in-house specialists, with no outside contractors. We don't disappear after the Google Play launch: we update the app for new Android versions and keep developing it as your business grows.