How the mobile app development process works in Istanbul
A mobile app is built through sequential steps from clarifying the goal to store approval. The most expensive mistakes are made in goal and technology decisions, not in coding.
Türk Bilişim · Content Writer
· Updated: · 7 min read

A mobile app for a business in Istanbul goes from clarifying the goal through design, prototyping, development and testing until it reaches the store page. A wholesaler, a café chain, an industrial manufacturer or a plaza company follows the same order; what differs is who the app serves, which technology is chosen and how the app is updated after launch.
How does a mobile app project run step by step with a team based in Kartal, Istanbul?
A mobile app project with a team in Kartal moves from idea to store page through sequential stages. The idea first becomes a requirements list, then a design, and then working software. The final stop is the page in the app store.

| Stage | What is done | Output of the stage |
|---|---|---|
| Goal and needs analysis | Defining whose which work the app will solve | Requirements list |
| Market and competitor research | Similar apps and user reviews are examined | Feature priority |
| Flow and experience design | Transitions between screens are drawn | Screen map |
| Technology decision | Choosing native or a single codebase | Technical architecture |
| Prototype | Clickable screens are tested with real users | Approved design |
| Development | Code is written, the app is connected to services | Working build |
| Testing and submission to the store | Bugs are fixed, the build is sent for review | Store page |
This sequence does not work as a rigid waterfall. If a screen is missing in the prototype, the flow design is revisited. If unexpected load appears during testing, the architecture is reconsidered. Still, keeping the order reduces code that has to be rewritten later.
Türk Bilişim, which is considered one of the best Android app development firms in Turkey, has operated as a digital agency since 1998. The firm has run projects under this name since 2007. Design, software, store publishing and post-launch maintenance are brought together in the same team. The scope of the service is described in detail on the mobile app service page.
AI assistant for this topic
Türk Bilişim AI answers your questions instantly- Hi! Ask whatever you're curious about.
Target and technology decision for the wholesaler in Bakırköy and Bahçelievler
For a wholesaler and distributor in the Bakırköy and Bahçelievler area, the goal of the application is usually dealer ordering. The goal becomes clear when stated in one sentence: the dealer will see stock, place orders, and track their account balance. The criterion is also set from the start. For example, orders that arrive by phone and message are expected to move into the application.
For a wholesaler with buyers abroad, language support is part of the goal. If a Russian or Arabic interface will be needed, that decision is made before design. Arabic is read right to left and changes the screen layout.
A single codebase with Flutter or React Native is the right choice when the business logic is the same on both platforms. A dealer app with catalog, cart, order history and notifications fits this description. One team publishes the same version to both stores. If the app will make heavy use of device hardware, for example talking over Bluetooth to a special barcode scanner, native development is reconsidered.
Technology choice directly determines scalability and ease of maintenance. As the number of dealers grows, the server side grows while the app code stays the same. The most expensive mistakes are made not when code is written but when the goal and technology decisions are made. These mistakes are often noticed only after launch. Other examples of this decision are found in the mobile app development articles.
Looking for iOS App Development?Why does the prototype for the café chain in Beşiktaş test before code is written?
For a café chain with several branches in Beşiktaş, a prototype is the cheapest way to try the idea before writing any code. Clickable screens can be prepared in a few days. At this stage, a flow that was set up wrongly can be corrected with a single drawing.
The order flow is tested in the prototype with a realistic scenario. The customer selects a branch, customizes a drink, moves to the payment screen and sees the pickup time. In the loyalty flow it is tested where the points appear and how the reward is used. The test is done with the cashier and with regular customers. Where the user gets stuck is noted, and then the screen is redrawn.
A common finding in café chains is that during the morning rush customers always want the same drink. If the prototype test shows this, a one-tap reorder button is added to the home screen.
After the design is approved, development begins. Approval means the flows and screens will not change; from this point the developer writes code according to the drawings. The scope of this stage is described in the mobile UI/UX design and prototype service.
Test and store approval for the manufacturer in Başakşehir and Arnavutköy
A manufacturer working in the industrial areas of Başakşehir and Arnavutköy often has the application made for its field team and warehouse staff. A version that has not been tested is not released. Testing is the stage where errors are found and fixed, and it is carried out with real users in the field.

On iOS, TestFlight distributes the build outside the store to invited users and collects feedback. On Android, Google Play's Internal testing and closed testing tracks do the same job. A service technician installs the build on their own phone and tries it in the factory and at customer sites. Whether data is lost in areas with weak signal is seen at this stage.
Common reasons for rejection during store review are:
- Missing privacy policy or a privacy policy link that does not open
- Not giving the reviewer a working test account
- Mismatch between the store description and the app's content
- The app crashing during review
Manufacturer apps often require a company account to log in, so the test account is frequently forgotten here. The privacy policy and the KVKK text should be ready before publication. A documents page on a website can serve as an example of how these documents are published.
App stores review the app before publishing it, and the store and the period determine how long this takes. For that reason the release date is planned flexibly. If the app is going to be introduced at a fair or a dealer meeting, submission is made a few weeks in advance.
How does the corporate company in Ataşehir update the app after release?
Companies in Ataşehir in finance, insurance or holding sectors update the app after release in two ways. The type of change determines which way is used.
If the app is written with React Native and Expo, over-the-air updates can be used. Changes on the JavaScript side reach the user without passing through the store. A text correction, the layout of a campaign screen or a form rule goes live in a few hours this way.
A native change, however, requires a new store version. A new device permission, a camera or biometric login module, and a third-party SDK update belong to this group. That code runs in the layer compiled on the device. The version goes into review again and reaches users after approval.
The maintenance plan is written before the release day. Every new iOS and Android version requires compatibility testing. The libraries used are updated at regular intervals. Crash reports are monitored. The company provides maintenance, updates and support after release. Questions about how it works are answered on the frequently asked questions page.
Looking for Mobile Commerce?Frequently asked questions
Can an iOS and Android app be released at the same time from a single codebase?
Code written in Flutter or React Native is compiled separately for each platform and can be submitted to both stores on the same day. The two stores' reviews run independently, so being released on the same day is not guaranteed.
Is a privacy policy required for store review?
Yes. The link must be opened both from the store page and from inside the app. A broken link is also treated as a rejection reason, just like a missing policy.
Can the app be prepared in languages other than Turkish?
Türk Bilişim can run projects in Turkish, English, Arabic and Russian. The store description and screenshots are also prepared separately for each language.
Why is it necessary to give the reviewer a test account?
If an app that requires login cannot be entered by the reviewer, they cannot evaluate the app and will reject the version. A working username and password are written in the review notes on the submission form.
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.
Your request is saved on this device
We can't reach our server right now. Your request will be sent automatically once the connection is back. To talk right away:

Share this article
Comments
Comments
No comments yet.
















