Tried building a mobile app with free tools—when is it time to budget for an agency?

The biggest bottleneck with DIY no-code builders is native hardware access. Setting up background location tracking, secure payment gateway APIs, and push notification servers will quickly run into hard server-side limits. Plus, app store review teams instantly flag and reject template apps that are essentially just mirrored websites.

We fell into the exact same trap last year and wasted a month on a free tool. Removing their branding cost $39 a month, push alerts were another $19. It ballooned to almost $700 a year and the stores still rejected our submission. We ended up having a simple mobile-optimized web ordering form built, and that solved everything.

Getting customers to download an app for a dry cleaner with two branches is practically impossible. People barely have enough storage for banking, messaging, and food delivery apps. Why would a customer who drops off a coat twice a year download an app? Test the waters with a WhatsApp Business line and a mobile website before handing 75.000 TL over to an agency.

Before giving 75.000 TL to an agency, ask about a browser-based PWA option. The user opens it in their browser taps "add to home screen," and it launches just like an app. You won't have to deal with app store approvals or annual developer account fees. It'll wrap up costing around 20.000 TL too.

Ive been down this exact road, mate. Free tools are just bait; everything looks free at first, then the second you want to integrate a payment gateway it hits you with an "upgrade to pro" paywall. If the agencys quote feels too steep, you could hire a freelance dev to set up a ready-made open-source ordering template.

The scenarios where paying an agency is actually warranted are clear-cut: 1) When you need real-time map tracking for couriers, 2) When you require instant inventory sync with your existing barcode and POS software, 3) When secure storage of credit card details and legal liability are at stake. You definitely don't need an agency just for a basic appointment form.

the free mobile app thing is a total myth. they either shove their own ads into it or lock you into a 50 dollar monthly subscription. app store accounts are a whole other headache too. a clean mobile website makes way more sense every time.

edit: typed from phone, sorry for typos.

In mobile store processes, personal data protection and the legal compliance of privacy policies are of critical importance. Pre-built templates generally fail to achieve full compliance with local regulations. Concerning integrations and the retention of customer data, working with an agency backed by a formal contract is legally far safer.

I felt relieved reading this answer, so it's not just me. Processes without records never improve, because you don't know what to fix.

Of course, it varies if your situation is different.

Let me summarize what's been said so far. Start with a small trial; don't commit to everything at once.

I'm also curious if anyone does it differently.

There's also a measurement aspect to this. Start with a small trial; don't commit to everything at once.

When we decide without measuring, we always end up in the same place. This is my opinion, I'm not claiming it's absolute truth.

We got stuck at the same point for a while. anyway every "well look at it later" in a meeting means unbilled work.

Correct me if I'm wrong.

My question might sound amateurish, sorry about that. Mistakes made on the free app builder side are usually reversible but expensive.

I disagree with you on this point. If scope grows either time or budget must grow. There is no third option.

The harder it is to reverse a decision the slower you should make it... Of course, it varies if your situation is different.

There's also a measurement aspect to this. If scope grows, either time or budget must grow. There is no third option.

The system lives on after delivery; maintenance is a separate line item. If you have questions, write them; I'll answer as best I can.

This is exactly what we experienced. In legacy systems, the most expensive thing is unknown dependencies.

Correct me if I'm wrong.

Let me share my experience. Processes without records never improve, because you don't know what to fix.

Hope this helps.

I completely agree. Implementing a change request process doesn't slow things down, it speeds them up.

People defend habits, not processes. Resistance comes from there. This is my opinion, I'm not claiming it's absolute truth.