Applications / PWA cross platform application
PWA and cross-platform
We choose PWA or cross-platform when you want faster launch and coherent experience on mobile and desktop.
Background
When this service makes sense
Applications that can function on multiple devices with a more manageable code base.
- Main needPWA cross platform application
- Role in the projectWeb and mobile applications, SaaS platforms and portals connected to company data and processes.
- Result pursuedWe choose PWA or cross-platform when you want faster launch and coherent experience on mobile and desktop.
Deliverables
What usually comes into the project
The exact list shall be adjusted after the audit, but these modules frequently appear in pwa and cross-platform projects.
01Platforms analysis
02PWA shell
03Partially optional offline
04Optional notifications
05Responsive testing
Connection
Service works better when it's connected to the rest of the project
Any service works better when connected to the rest of the ecosystem: content, SEO, data, operation, hosting and maintenance.
- Web applications
- Mobile applications
- SaaS platforms
- Portals and internal systems
Recommended pages
Pages related to this type of service: technologies, fields of activity, guides and complementary services.
Frequently Asked Questions
Before we begin the project
Selection, stages and support for PWA and cross-platform.
01 / Choice
What's useful to know
PWA replaces the native mobile app?
Sometimes yes, especially for simple flows. For advanced native functionalities, the native application can be better.
What information are we preparing for the first discussion?
Users' roles, main flow and an example of data used in the application. We clarify the targeted devices, authentication, payments and external systems prior to estimation.
02 / Planning
Purpose, budget and stages
What can the project include?
For PWA and cross-platform, starting points are: Platform analysis; PWA shell; Partially optional offline; Optional notifications; Responsive testing. In the offer we specify deliverables, limits and responsibilities; the list adapts to your situation.
How do we set the budget and the timetable?
The budget and timing depend on the flows, roles, integrations and platforms we launch. For a first version, we choose the functions necessary for validation and determine what can be added later.
03 / Continuity
Verification and support
How do you verify the result before handover?
We test authentication, permissions and main flows, including error cases. We check the behavior on the devices targeted and validate the scenarios with the users who will use the product.
What happens after handover?
At launch, we agree monitoring, support and responsibility for updates. App store publishing, where needed, and new features have clearly defined steps and costs in the proposal.