Commissioning a mobile app: what sets the cost, and app or mobile site?

· 5 min read · Softio

Commissioning a mobile app: what sets the cost, and app or mobile site?

You have an app idea but no idea what it will cost. The items that set the price, whether you really need an app, and how to shrink the first version.

"I want an app built, how much will it cost?" reaches us several times a week. The honest answer: it depends on the idea, and it is usually different from the first guess, because an app is more than the screens you see on the phone. This article explains the items that make up the cost, how to tell whether you really need an app, and how to protect the budget.

First: do you really need an app?

  • Users will use you often: orders, bookings or tracking several times a week.
  • You need to send push notifications.
  • Phone features such as camera, location or offline use are part of the job.
  • Your field team works from phones and you need it recorded.
  • The app itself is the product you sell.

If customers use you a few times a year, downloading an app is a barrier for them. A well-built mobile-friendly website or an ordering site is cheaper and more effective. There is a middle option too: web apps that can be added to the home screen and send notifications, giving an app feel without the store process.

What sets the cost

1. Number of screens and flows

Login, registration, home, list, detail, basket, payment, profile, settings. Every screen is designed and coded, so the longer the user's path, the higher the cost. Our first job is always to put the screens on paper.

2. Modules

Login methods, push notifications, online payment, maps and location, camera, chat, multiple languages. Each is a separate development item; payment and chat look small but are among the most demanding.

3. Admin panel and back end

The most overlooked item. Every piece of data in the app comes from somewhere and is managed somewhere: products, users, orders, notifications. That needs server-side services and an admin panel, which in most projects take as much work as the app itself. Always ask "is the panel included?"

4. Platform: iOS, Android or both

Shipping to both platforms from a single codebase is common and economical. Separate native development roughly doubles the cost and is needed only for very specific hardware needs.

5. Integrations

Your existing website, accounting software, shipping, SMS, payment provider. Having the app and the website share one database is far cheaper than synchronising two systems later, which is why building both with one team makes sense.

6. Design

A plain interface from ready components, or screens drawn for your brand? Custom looks better but takes longer.

7. Store publishing

Developer accounts are opened for the App Store and Google Play; Apple charges annually and Google once, paid directly to them. Store visuals, descriptions and a privacy policy are prepared. Both stores review the app and sometimes ask for changes, which adds to the timeline.

8. Testing and maintenance

Testing across phones and OS versions, and after launch, yearly iOS and Android updates mean the app must be updated too. Plan an annual maintenance budget from the start.

Protecting the budget: a small first version

The most expensive mistake in app projects is putting every feature into version one. The right approach is to ship the smallest version that does the user's core job and learn from real use. This is called an MVP, and we apply the same approach to custom software projects. In practice we split the feature list into "must have", "version two" and "maybe", and version one contains only the first column. Budget and time can halve, and no money goes to features nobody will use.

Checklist when getting quotes

  • Are the screen list and wireframes part of the quote?
  • Are the admin panel and back end included?
  • Single codebase or separate development?
  • Will store accounts be opened in my name?
  • Will the source code be handed to me?
  • Is post-launch maintenance listed separately?
  • When will I see a test build on my own phone?
  • Is there a staged payment plan?

A realistic timeline

A lean first version can be installed on your phone as a test build within weeks of wireframe approval; store review adds some time before launch. Projects with many modules, payment and chat take months. We give a firm timeline in writing once the scope is clear.

Let's assess your idea together

At every meeting we first ask whether an app is really needed; sometimes the answer is "no, a mobile site is enough" and we say so. If it is needed, we sketch the screens together, shrink the first version and quote item by item. The panel and services behind the app are built by our custom software team. See the mobile app page or call +90 534 974 66 80.

Would you like a roadmap tailored to your business?

+90 534 974 66 80 Message on WhatsApp
WhatsApp Call Get a Quote