- Make sure you understand the key points before making a decision.
- Take a step-by-step approach and check each step as you go.
- Choose information that is reliable, useful and relevant to your situation.
- Measure the results and plan for long-term monitoring.
Having a mobile app developed involves an investment in design, development, testing and maintenance. An agency can help you turn an idea into a usable product, but not all proposals cover the same scope. Before comparing prices, clarify the problem to be solved and the expected outcomes.
Start by defining the requirement
Describe the target users, the situations in which they will use the application, and the actions they need to be able to carry out. A booking application, an internal business tool and a community platform do not have the same constraints. Also identify the features that are essential for launch and those that can wait.
Criteria for choosing a mobile agency
- Business understanding: The team asks questions about your users, your processes and your constraints, rather than immediately proposing a list of features.
- UX/UI design: She explains how the routes will be designed, tested and validated before full-scale development.
- Technical skills: It justifies the choice between native and cross-platform development depending on requirements, expected performance and budget.
- Verifiable references: She outlines comparable projects and explains her actual role in their implementation.
- Project methodology: It sets out the stages, deliverables, validation procedures and how to handle changes.
- Quality and testing: It involves testing across a range of devices, versions and network conditions.
- Publication: It specifies who manages the developer accounts and the processes involved in publishing content online.
- Maintenance: It explains how bugs, updates and enhancements will be handled after delivery.
The stages of a well-structured project
1. Scope and specifications
Scoping transforms the idea into a defined scope: user profiles, functionalities, business rules, data, constraints and priorities. It must result in deliverables that are clear and verifiable.
2. Models and prototypes
Screens and user flows are designed before development begins. A prototype enables us to test the navigation logic and identify any areas of confusion before investing in the code.
3. Development
The team develops the necessary features, interfaces and connections. Ask for regular demonstrations and access to project tracking.
4. Testing and acceptance
Tests must cover the main workflows, errors, access rights, notifications, performance and target devices. The acceptance test formalises any anomalies and their corrections prior to delivery.
5. Publication and follow-up
Publishing on app stores requires developer accounts, legal information, visuals, a privacy policy and compliance with the applicable rules. The work doesn’t stop once the app is first published online: you need to monitor feedback and rectify any issues.
An agency, a freelancer or a no-code solution?
An agency can bring together a range of skills and manage a project from start to finish, but this may come at a higher cost. A freelancer may be suitable for a specific scope of work, provided you check their availability and that they have the necessary complementary skills. A no-code solution can speed up the development of a prototype or a simple application, but you need to consider its limitations, data ownership, recurring costs and scalability.
10 questions to ask before signing
- Who will be responsible for the scope and design?
- What features are included in the quote?
- What technology is on offer, and why?
- What deliverables will be provided at each stage?
- How will changes to the scope be quantified?
- Who owns the source code and the rights to the creations?
- Will the App Store and Google Play accounts be in my name?
- What tests are planned before publication?
- What maintenance is included after delivery?
- How can I retrieve my data and switch providers if necessary?
How much does a mobile app cost?
The budget depends on the number of features, the complexity of the user flows, the level of design, integrations, platforms, security and maintenance requirements. A simple app with few screens does not cost the same as a platform with payment processing, geolocation, messaging and multiple user roles. Request a quote that sets out the scope of work, assumptions, exclusions and recurring costs.
Why start with an MVP?
An MVP is an initial version limited to the features needed to test a key hypothesis with real users. The aim is not to deliver a slapdash product, but to narrow down the initial scope in order to learn before investing in all the options under consideration. Define the criteria that will help you decide how to proceed.
The contract and ownership of the project
The contract must specify the scope, the timetable, the payment terms, the acceptance criteria, change management, maintenance and the responsibilities of each party. Ensure that the handover of source code, documentation, mock-ups, access rights and developer accounts is clearly specified. Also check the transfer conditions in the event that you change service provider.
Pitfalls to avoid
- Choosing only the cheapest quote without comparing the deliverables.
- Accepting a promised deadline without validated specifications.
- Do not set aside a budget for maintenance and upgrades.
- Leaving developer accounts in the service provider’s name without a clear agreement.
- Developing too many features before testing user requirements.
Talking about your project
Before requesting a quote, please prepare a description of your users, the key features and any constraints. Elvis Web can analyse your digital requirements and advise you on a suitable scope of work. Please use our form to tailored quote to present your project.
FAQ
Should you develop for iOS and Android at the same time?
Not necessarily. The choice depends on your audience, your budget and technical constraints. A multi-platform approach may be appropriate, but it must be assessed in light of the required functionality.
Who owns the source code?
It depends on the contract and the rights being transferred. Ensure that the contract specifies ownership or the licence to use, the handover of deposits, documentation and the terms of transfer.
Is publication on the online shops guaranteed?
No. The platforms assess applications in accordance with their own rules and may request amendments. The service provider can prepare the application and assist with the submission, but cannot guarantee approval.
Assess the working method before signing
A reputable agency should be able to explain how it turns an idea into a testable product. Ask what stages are planned: scoping, workshops, user journeys, mock-ups, prototyping, development, testing, launch and maintenance. Check the deliverables associated with each stage and the points at which your approval is required. A proposal that jumps straight into development without clarifying the requirements exposes the project to costly changes.
Ask how new requests are handled. Adding a new feature may affect the architecture, budget and schedule. It must be assessed before being implemented, with an explanation of its implications. A shared tracking tool and regular reports help to provide clarity on progress and the decisions taken.
Defining an MVP and avoiding an uncontrolled scope
The minimum viable product should enable a value proposition to be tested using a limited set of essential functions. The aim is not to deliver an unfinished application, but to focus resources on the essential user journeys. Classify features into three categories: those necessary for launch, those useful after validation, and those that are optional. This hierarchy helps to keep within budget without compromising on security or quality.
For each function, describe a user scenario and a success criterion. For example, a user must be able to create an account, find a service, make a booking and receive a confirmation. Also specify error scenarios: time slot unavailable, connection lost, payment declined or password forgotten. These scenarios directly influence the design and testing.
Check technical skills and references
Ask for examples of applications that are comparable in terms of complexity, sector or integrations. Seek to understand the agency’s exact role, the technologies used and the constraints encountered. A visually appealing interface does not guarantee the quality of the code, the stability of the system or the ability to maintain the product. If possible, ask for a demonstration of real-world user flows and discuss technical choices without requiring the disclosure of other clients’ confidential information.
Identify the people responsible for architecture, development, testing and monitoring. Ask who is responsible for responding to incidents and how responsibilities are organised should a team member leave the project. Business continuity must not depend on a single person who holds all the technical knowledge.
Protecting data and access
An app may process personal data, contact details, payment details or sensitive information. Ask what data is collected, why, where it is stored, who can access it and how long it is retained. Any permissions requested on the phone must be justified by a specific function. The project must incorporate data protection by design, rather than treating it as a last-minute formality.
Publishing accounts, cloud services, analytics tools and developer accounts must be organised in such a way that the organisation retains control. Define roles and permissions, enable the available security measures and document access rights. Have a qualified professional check the applicable legal obligations where the project involves several countries or specific types of data.
Planning for testing, publication and updates
Tests must cover the devices and system versions used by the target audience. Check screens, connections, notifications, payments, permissions, network errors and offline scenarios, if the app supports them. Ask how issues are categorised, resolved and validated. A demonstration on a single phone is not sufficient to validate all use cases.
Publishing on app stores requires product descriptions, screenshots, privacy information and compliance with the platforms’ rules. The agency can prepare the necessary materials and assist with the submission, but the final decision rests with the platforms. Once launched, you should plan for bug fixes, compatibility updates, support and a maintenance budget. An app is a living product that evolves alongside systems and users’ needs.
Check the contract and the reversibility clause
The contract must specify the rights relating to the specific code, mock-ups, content and graphic elements, as well as the licences for third-party components. Request the handover of the source code, deployment instructions, API documentation and the necessary access rights. Ensure that you have the option to change service provider without losing the ability to maintain the application.
Request a detailed quotation that breaks down the costs for scoping, design, development, testing, launch and maintenance. The timelines must include validation stages and any necessary liaising with the platforms. A transparent proposal should also set out any exclusions, recurring costs and the process for handling additional requests.