I'm planning to have a mobile app built — how does the process work, what's expected of us?

When getting quotes, go for cross-platform technologies like Flutter or React Native that let you develop both iOS and Android from a single codebase. With a 250,000 TL budget, trying to build two separate native apps for each platform will run you well out of pocket.

We had a similar booking app built for a beauty salon last year. The Apple developer account cost 99 dollars a year, and the Google account was a one-time 25 dollars. We also have an ongoing fixed cost of around 1,500 TL a month for the server and push notification services, so budget accordingly.

Iron out these four rules before sitting down with an agency: 1) Can the customer cancel the appointment directly, or is an approval step required? 2) Will payment be processed in-app or at the branch? 3) Will points expire? 4) Will staff commissions be tracked through the app?

Apple and Google store policies require you to provide an easily accessible button inside the app for users to delete their accounts. If this detail gets missed during design, your app will get rejected flat out during store review, delaying your launch.

We announced our launch date with our first app, but the Apple review took a full 12 days and we got rejected on the first submission over our privacy policy. Never announce a release date to customers before getting approved; always leave a 2-3 week buffer.

apple dev account should be opened under the company name, if u open an individual account your own first and last name will show up on invoices and as the developer in the store, doesnt look professional fyi

When signing with the agency, make sure the quote includes at least 3 months of post-launch bug fixing and OS update support. When a new OS update drops, the app can crash; ongoing support is essential.

There's a trap here let me mention it. Payment schedules should be tied to project phases not calendar dates.

When you try to change everything at once nothing settles. If I were you, I'd go this route.

You're right. Solutions that work at a small scale collapse when you grow; I learned this late.

Trying to do this alone is the most expensive way.

i've been down this road, let me tell you. the harder it is to reverse a decision the solwer you should make it.

Great work.

Noted, thanks.

i think it's hard to be that definitive about mobile app development process. mistakes made on the mobile app development process side are usually reversible but expensive.

We need to take it step by step. The biggest time-waster for us was not knowing who had the final say.

I'm also curious if anyone does it differently.

I'm a small business, let me explain from my side. Mistakes made on the mobile app development process side are usually reversible but expensive.

You're right.

I went through the same thing.

Let me speak from the other side; I'm on the supplier side. If acceptance criteria aren't written, when the work is done is open to debate.

In legacy systems the most expensive thing is unknown dependencies. This is my opinion, I'm not claiming it's absolute truth.