Code/App Development Graz

app development
graz

Apps for Styrian businesses, including half-finished ones. We take over projects whose original developer is gone and get them into the store.

LocationVienna, for Graz
FocusNew build & takeover
Entryfrom 5,000€
Trendsharply rising demand
Vol. 12 // No. 2026Ed. Graz

what app development
in Graz means

In Graz we run into apps that half exist more often than average. With two universities and a large tech scene, many projects here start as a thesis, with an intern or with a developer who has since moved abroad. The code then sits somewhere, may even run, but nobody dares touch it. We look at it, say honestly whether taking it over is cheaper than rebuilding, and then do one or the other.

finishing what was started

ÜBERNAHME // BESTAND

Before promising anything we read the existing code and build the project once ourselves. Only then can we say whether taking it over makes sense. With a thesis project the honest answer is often no, because different goals were in the foreground there than maintainability.

the store is the last hurdle

STORE // FREIGABE

Many half-finished apps fail not on the technology but on approval. Apple reviews every submission, and the most common rejections concern missing privacy declarations, unclear purposes for permissions and sign-in flows. We put that in order before submitting.

one codebase, two systems

HYBRID

For a new build we go hybrid in the vast majority of cases, meaning one codebase for iOS and Android. That halves the cost against two native versions, and with a normal business application nobody notices the difference.

do you really
need an app

For about half the inquiries the most honest answer is no. If nobody needs camera, location or notifications and the thing could run in a browser, a web app is cheaper, faster to finish and simpler to operate. We say so beforehand, because an app sitting in the store that nobody downloads costs more than none at all.

Web appA tool for staff or customers, no store neededIn favourChanges live immediately, no store review, one version for everyoneAgainstNo icon on the home screen, no access to every device feature
Native appCamera, location, notifications or working offlineIn favourFull device features, best performance, findable in the storeAgainstTwo versions for iOS and Android, every change through review
HybridStore presence wanted, but no budget for two versionsIn favourOne codebase for both systems, considerably cheaperAgainstNoticeably slower with very demanding interfaces

If the conversation shows a web app is enough, we take that route. What that means and what it costs is on our page about web app development.

what an app
costs in Graz

A new build starts at 5,000€ with us for a simple case, 12,000€ with user accounts and a database and 25,000€ with connections to existing systems. For a takeover we can only name a price after reading the code and building the project once ourselves. That review is manageable and always worth it, because it is what makes the decision between takeover and rebuild possible in the first place.

ENTRY

Simple

from 5,000€

One clearly defined job, one screen after another.

  • Hybrid for iOS and Android
  • Up to about five views
  • Without user accounts
  • Published in both stores
  • You get the source code

MOST COMMON

With accounts

from 12,000€

As soon as users log in and data gets stored.

  • User management and permissions
  • Own database behind it
  • Push notifications to the device
  • Usage analytics
  • Support after launch available

INDIVIDUELL

Integrated

from 25,000€

When the app has to connect to existing systems.

  • Connection to ERP or CRM
  • Working offline and syncing later
  • Several roles and locations
  • Native version where needed
  • Ongoing development
Bernhard Müllauer, founder of creatingfaces and your contact for the project
Your contact

bernhard müllauer

I write the quote, I design, I build. You do not get an account manager standing between you and the work, you talk to the same person from the first question until after launch.

If something does not make sense, I say so, even when that makes the project smaller. In the long run that is more pleasant for both sides. I drive to Graz for the first conversation, especially when several people from your company should be there.

After launch

an app is never
really finished

That is the difference to a website, and it almost never comes up in a quote. Apple and Google release new system versions every year, and the stores regularly require rebuilt versions. Anyone who knows that beforehand plans differently and is not surprised afterwards. So it stands here and not in the fine print.

What keeps running after launch
Apple Developer Programevery year99 USDWithout an active membership the app disappears from the App Store. That happens regularly by accident when a credit card expires.
Google Play Consoleone-time25 USDOne-time registration, no annual renewal. The cheaper of the two stores, but with stricter testing requirements before release.
Adapting to new OS versionstwice a yearby effortApple and Google release new major versions every year. Usually the app keeps working, but small things break, and at some point the store requires a rebuilt version.
Server and databasemonthlyby effortOnly needed when the app stores its own data or has user accounts. A pure information app does not need it. The cost depends on usage, not on the app.
Changes to content and featuresongoingby effortThe biggest item, and the only one you control yourself. Every change has to be rebuilt and go through store review again, which takes one to three days at Apple.

Fees per Apple Developer Program and Google Play Console, as of August 2026. Remaining items qualitative.

Graz in detail

plenty of tech,
little continuity

With its technical university and one of the largest universities of applied sciences in the country, Graz has more developers per head than any Austrian city except Vienna. That is an advantage for starting and a disadvantage for continuing: someone who supported a project as a student is often in Vienna, Zurich or Berlin two years later. What remains for the company is an app that runs as long as nobody wants to change anything.

we also say when rebuilding is cheaper

Taking over somebody else code is sometimes more expensive than starting from scratch, especially when it was written without documentation and without tests. We have recommended both. What we do not do: promise a takeover before seeing the code and then ask for more during the project.

we sit in vienna, not in graz

For an app project that is no disadvantage, because coordination happens on the code and on screen designs anyway. For the first conversation we drive to Graz if you want, especially when several people from your company should be there. After that it runs over video.

why us
and not cheaper

Because we look at somebody else code before writing a quote, and because afterwards we say honestly what it is worth. That is less convenient than selling every project as a rebuild, and in about half the cases it saves you money. On top of that you get the source code and the store accounts, so the same thing does not happen to you twice.

tell us what
you have in mind

Describe briefly what the app should do and whether code already exists. If it does, we look at it before writing a quote.

[ More Services ]All Services →

questions & answers

[ FAQ ]

An app starts at 5,000€ with us for a simple case without user accounts, 12,000€ with sign-in and a database and 25,000€ with connections to existing systems. Demanding applications reach 50,000€. For taking over a half-finished project we can only name a price after reading the code and building the project once ourselves. That review is manageable and is what makes the decision between takeover and rebuild possible in the first place.

Yes, and in Graz that comes up more often than elsewhere. We read the existing code and build the project once ourselves before promising anything. Only then can we say whether a takeover is cheaper than a rebuild. We have recommended both.

Because with the technical university and a large university of applied sciences, many projects here start as a thesis, with an intern or with a developer who works somewhere else two years later. The code may still run, but nobody dares touch it.

Then we say so and recommend a rebuild. Taking over somebody else code is sometimes more expensive than starting from scratch, especially when it was written without documentation and without tests. What we do not do: promise a takeover before seeing the code and then ask for more during the project.

Yes, because coordination on an app project happens on the code and on screen designs anyway. For the first conversation we drive to Graz, especially when several people from your company should be there. After that it runs over video.