Your app idea deserves to succeed.

Usually, most projects fall into three brackets. Scoped work — a bug fix, a new feature, a codebase audit — starts from a few hundred euros. An MVP (Minimum Viable Product, a working product that validates your idea) usually sits between €3,000 and €12,000. Large, complex projects can reach figures between €20,000 and €40,000+. What moves the number: how many screens, whether a backend has to be built or your APIs already exist, third-party integrations like payments, video or maps, and whether the design is ready. After a short call I can give you a ballpark range for the type of project proposed, which can then be finalised and narrowed down in the following steps.

A focused MVP usually takes 4-8 weeks from kickoff to store submission, though depending on complexity it can run to 3-6 months. Smaller work — a feature, a fix, a performance pass — takes from a few days to a couple of weeks. Add a few days at the end for App Store and Play Store review. At every stage of development you can see a preview of the app, so you can test the product with your own hands while it is being built.

An agency can be the better choice for particularly complex projects, where design, backend, QA and project management all need to be staffed at once. A freelancer is the better choice when you prefer the person you talk to to be the same person writing the code. No markup for an account manager or a team of developers, no junior developer quietly assigned to the project, no rotating team: you get 8+ years of mobile experience directly, and for most apps this is both faster and cheaper.

It depends on the type of app. The most efficient choice is often a cross-platform framework, since a single codebase produces the app for both iOS and Android. There are particular cases — for example an app that needs heavy communication with operating system services, or low-level operations such as machine learning performed on the device — where it is better to build directly on the native framework. In any case, for 90% of projects a cross-platform solution is the recommended choice.

Yes — it is an important part of my work. I start with a short audit of the code, architecture and dependencies to understand what can safely be changed, then we decide the priorities together. Inherited code with no documentation and no original developer available is a normal starting point, not an obstacle. On an e-learning app whose development I took over, monthly active users grew by 117% and the store rating went from 3.5 to 4.5 in six months.

Ownership of the code belongs solely to the client, not to the developer. Once the project is complete and the final balance is paid, the source code is transferred, which allows the client to work with other developers, make changes independently, and more.

The first introductory call is usually about the project, the expectations and the requirements, and there I can already give a ballpark estimate of timing and cost. After that there will be further calls to define the requirements list — the list of features the app must have, described in depth. I then provide a detailed quote which, once accepted, marks the start of our collaboration.

Not directly — I work with several skilled, professional designers, and if the design of the application also needs doing, I have them carry out that work. As with every other phase of the project, there is continuous discussion to meet the client's expectations 100%. If the design has already been done, I am happy to build the application based on it.