Product choices5 min read
Web app, PWA or mobile: which solution fits your project?
Compare web apps, PWAs, hybrid and native mobile against usage, devices and what already exists. A practical framework for defining a first version.
Read the guideDo your users need an application on their phone or tablet? CUB3 offers two mobile options: a hybrid application based on an existing product, or a native application with a scope defined for your project.
Hybrid: €10,000 excluding VAT for the recovery described below. Native: from €15,000 excluding VAT for an iOS or Android MVP, with a usable existing API.
A hybrid application shares a development codebase across several mobile platforms. A native application is built specifically for its target platform, such as iOS or Android. The choice depends on use cases, expected features and your users’ devices.
Does your application already have a design, features and reusable modules? This offer provides a first hybrid iOS and Android version based on that product, with a defined API and payment scope. Testing and submission to stores are included.
The scope assumes that the design is retained and suitable modules are reused. We therefore identify what can be retained, what needs adapting and the exchanges the mobile application depends on.
The quote specifies the first version’s features, API and payment boundaries and deliverables. An existing product does not automatically make every feature reusable: the initial review determines whether your project fits this scope.
We review the available elements and define the version to build. The adaptation is then developed and tested within the agreed scope before preparation and submission to stores.
Submission is a delivery stage. Acceptance is decided by the platforms and is not a guarantee included in the price. The development schedule and stages dependent on third-party services are specified during scoping. A completely new build or major redesign requires a separate quote.
The native offer covers an MVP developed specifically for one platform, iOS or Android, from €15,000 excluding VAT. The budget assumes a usable existing API and essential workflows defined during scoping.
The scope includes UX/UI, development, testing and submission to the selected platform’s store. We define users, their devices and the necessary workflows with you. The quote specifies the features and delivery conditions.
A new backend, a second platform and advanced features are priced separately. UX/UI is included within the native scope and can be designed for the project. Other available elements are reviewed to account for what can be reused.
For the hybrid offer, a completely new design or major redesign falls outside the €10,000 excluding VAT recovery scope. For both offers, requirements involving specific hardware or offline business workflows need a dedicated assessment. Hosting, licences, third-party usage and store fees are additional. Ongoing support can be arranged through application maintenance.
If you are starting from an idea without an existing application, first describe the users, workflows and device constraints. Our support for designing and launching a product helps prepare that discussion.
The hybrid offer costs €10,000 excluding VAT for scoped recovery of an existing product, retaining the design and reusable modules. The native offer starts at €15,000 excluding VAT for an MVP on one platform, with a usable existing API. UX/UI, development, testing and store submission are included; a new backend, second platform and advanced features require a quote.
The hybrid offer includes a first iOS and Android version within the recovery scope described. The native starting price covers one platform, iOS or Android. The second is priced separately.
That price applies only to scoped hybrid recovery of an existing product. A completely new hybrid application requires its own estimate. For a native application, budgets start at €15,000 excluding VAT and the scope is defined with you.
It depends on the requirement. A PWA is a separate offer with its own capabilities and limitations. We can compare use cases before choosing a format.
See pricing and scopes, or the web application offer if the project should first be built for the browser.