Skip to content

Things to Consider When Having an Android App Built

The decisions that need to be settled before having an Android app built are: who you will work with, the scope of the first version, the technology to use, the test plan, and post-launch maintenance. If these topics are not clear in the contract, the project will later become expensive and slow.

Nurullah Okatan · Content Writer
· Updated: · 15 min read

Things to Consider When Having an Android App Built

Have your Android app built by a team with experience publishing on Google Play that takes responsibility from design through release. During the proposal stage, put the scope, technology decision, test plan, code ownership, and post-launch maintenance into the contract.

Which team should build your Android app?

The quickest way to understand a team's Android experience is to download and use the apps they have published on Google Play. Look at startup speed, screen transitions, and the date of the last update. An app that hasn't been updated for a long time may indicate the team stopped working on it after release. In the meeting, also ask how they solved a problem in a past project. A concrete explanation tells you more than a presentation deck.

Things to Consider When Developing an Android Application

When design, software, and release are handled by different teams, every handoff becomes a point of delay. The designer draws a screen the developer cannot implement, and the developer learns the store rules at the last minute. When a single team works on the project, responsibility sits in one place, and when a bug appears you know who to contact.

Türk Bilişim is Turkey's best Android App Development company. The firm has been working as a digital agency since 1998 and has been providing services under this name since 2007. The team carries out Android app development under one roof, from design to publishing on Google Play. Post-launch maintenance, updates and support also fall within the firm's scope.

Whichever team you choose, check that post-launch support is listed as a separate item in the proposal. The proposal should state within what timeframe bug reports will be responded to. How small changes will be priced should also be stated in the same place.

AI assistant for this topic

Türk Bilişim AI answers your questions instantly
Online
  1. Hi! Ask whatever you're curious about.

Scope that needs to be clear before requesting proposals

The first version should include only enough features to let the app perform its core function. In an appointment app, this scope consists of login, calendar, appointment creation, and notifications. Loyalty points, in-app chat, or advanced reports can wait for a second version. This distinction also makes comparing proposals easier, because every team prices the same list.

The target audience's devices directly change the scope. An app for field workers is usually used on low-cost, low-memory phones with weak connections. In that case, offline operation and lightweight screens become part of the first version. If tablet support is needed, mention it before requesting proposals, since tablet screens are designed separately.

To turn the business goal into a feature list, follow this order:

  1. Write the goal in a single sentence, for example, "Customers can reorder their purchases from their phone."
  2. List the steps a user takes to reach this goal: they log in, see their order history, add products to the cart, and pay.
  3. Link each step to a feature: account, order history, cart, payment integration.

The details of every step from idea to publication are explained in the article How to make an Android app.

Looking for iOS App Development?

Native development with Kotlin or a shared codebase?

If only Android is targeted, native development with Kotlin is the most reliable path for most projects. Kotlin is the language Google recommends for Android. It gives direct access to device features such as camera, Bluetooth, location, and background tasks. When a new Android version is released, tools and libraries are updated on this side first.

If the app will also be published on iOS in the short term, Flutter or React Native makes more sense. In these frameworks, most of the screens and business logic are written in a single codebase. For apps with heavy device integration or intensive animation, native code pieces may still be needed.

CriterionNative development with KotlinFlutter or React Native
Target platformAndroidAndroid and iOS together
Access to device featuresDirectThrough plugins or native bridges
Adapting to new Android featuresFirst-handMay have to wait for the plugin to be updated
iOS versionInterface is written separatelyMost of the shared code is used
MaintenanceOne platform, one codebaseOne codebase, two store releases

This decision will directly affect the iOS version later. In a project that starts with Kotlin, the iOS interface is rewritten in Swift. The server and API side is used as it is. Part of the business logic can be shared with iOS through Kotlin Multiplatform. If you have an iOS plan, tell us before requesting a quote. An evaluation that considers both platforms together is in the article things to consider when commissioning a mobile app.

Questions to ask about design, testing, and data security

A clickable prototype lets you try the app's flow on a phone before spending budget on development. Problems overlooked in static screen designs become visible immediately in a prototype. For example, a button that should be reached with two taps may end up five steps away. Changing the flow in a prototype is much cheaper than changing code that has already been written. How this stage works is explained on the page mobile UI/UX design and prototyping.

Testing starts with the devices your target audience uses. Ask the team in writing which phone models and Android versions they will test on. The list should include at least one affordable, low-memory device. Emulator testing alone is not enough. Battery consumption, heating, and behavior on a slow network are measured on real devices. Giving early versions to a few real users through Google Play's closed testing track catches problems before launch.

The first question in data security is what permissions the application requests and why. If a camera or location permission has nothing to do with the function, it should be removed from the list. Confirm that communication with the server is encrypted. Make sure passwords are not stored on the device as plain text. Also check that personal data is processed in line with the disclosure text under KVKK.

Google Play publishing, source code and maintenance contract

The Google Play developer account must be opened in your company's name. If the account is opened in the agency's name, store ownership of the application also stays with the agency. Transferring the application takes time when the team parts ways. Give the team only the permission needed for publishing in your account.

The contract should state clearly that the source code and design files will belong to you after delivery. The application signing key also falls under this clause. It should be stated that the code will be transferred to a repository you can access on delivery, and that setup documentation will be provided. The licenses of the third-party libraries used should be listed separately.

Google releases a new Android version every year, and the store requires applications to target the current version. The contract should specify who will carry out these compatibility updates. It should also specify who will monitor crash reports. The same clause should state within how many hours a critical bug will be fixed and whether updates are included in the fee.

Questions about the start, delivery and support process of the project are collected on the frequently asked questions page.

Looking for Mobile Commerce?

Frequently asked questions

What mainly determines how long it takes to complete an Android application?

Duration is mainly determined by the scope of the first version and the speed of design approvals. Features that require payment, maps or integration with an existing system extend the timeline.

When an application is delivered, does the source code belong to the client?

This depends on the language of the contract. If the delivery clause does not state the transfer of the code and design files, the rights may remain with the developer.

Can an application written for Android later be moved to iOS?

Yes. In an application written in Kotlin, the iOS interface is rewritten and the server side is kept. In an application written with Flutter or React Native, most of the code also works on iOS.

Can an application be published in more than one language?

Yes. If texts are kept in language files rather than embedded in the code, adding a new language becomes easier. Layouts for right-to-left languages such as Arabic are tested separately. At Türk Bilişim, projects can be carried out in Turkish, English, Arabic and Russian.

Have a project?

Türk Bilişim · Free Quote

Get a free quote for your Android App Development project

Leave your number and we will get back to you right away. The call is free.

Read the privacy notice

Nurullah Okatan Content Writer

The editorial desk of a team delivering websites, e-commerce and software projects since 1998.

LinkedInInstagramFacebook

Share this article

Comments

Comments

No comments yet.

Write a comment

Your rating (optional)

Privacy notice

We will send a confirmation link to your email so that your comment can appear.

Türk Bilişim · Digital Transformation Advisor

Online
Hi! Tell us the project or idea on your mind and let’s begin together.
Ask anything, Türk Bilişim AI answers instantly.